Skip to Content
avatar image
Former Member

Application update exception after upload process for xMDSD2.1 SR02

Hi,

After performing the changes in the device configuration and performing the upload, the system arises this synchronization error:

Uploading tour...

---Tour:S0170000002

Tour upload completed

1/21/08 1:59 PM

-Requesting patches ...

--Exception occurred when processing methodSYSTEMNEWS : java.lang.IllegalStateException: Cannot switch context because current conversation id is empty : Cannot switch context because current conversation id is empty

--Problems during synchronization: Format of the synchronization inbound file is not supported; Check sync gateway

--Exception occurred when processing synchronization events:Cannot switch context because current conversation id is empty (java.lang.IllegalStateException)

--Exception occurred when processing synchronization events:Cannot switch context because current conversation id is empty (java.lang.IllegalStateException)

--Exception occurred when processing synchronization events:Cannot switch context because current conversation id is empty (java.lang.IllegalStateException)

--Exception occurred when processing synchronization events:Cannot switch context because current conversation id is empty (java.lang.IllegalStateException)

--Exception occurred when processing synchronization events:Cannot switch context because current conversation id is empty (java.lang.IllegalStateException)

--Exception occurred when processing synchronization events:Cannot switch context because current conversation id is empty (java.lang.IllegalStateException)

--Exception occurred when processing synchronization events:Cannot switch context because current conversation id is empty (java.lang.IllegalStateException)

--Exception occurred when processing synchronization events:Cannot switch context because current conversation id is empty (java.lang.IllegalStateException)

--Exception occurred when processing synchronization events:Cannot switch context because current conversation id is empty (java.lang.IllegalStateException)

--Exception occurred when processing synchronization events:Cannot switch context because current conversation id is empty (java.lang.IllegalStateException)

--Remove assignment to application: MDSD_21_SR02_401 000013

--Server recognized that some applications are no longer needed on your device. They are now being deinstalled.

--Deinstallation of: MDSD_21_SR02_401 000013 Mobile Direct Store Delivery

--Assignment to application: MDSD_21_SR02_501 000016

--System determined that some required applications are not located on your device. They are now being installed.

--Download of application: MDSD_21_SR02_501 000016

--Installation of: DSK_UPGRADE2 1

--Download of application: MDSD_21_SR02_501 000016: Integration build Cycle 0

--Installation of: MDSD_21_SR02_501 000016: Integration build Cycle 0

--To complete installation restart your device.

Part of trace file:

20080121 13:02:17:421 I MI/API/Logging ***** LOG / TRACE SWITCHED ON

20080121 13:02:17:421 I MI/API/Logging ***** Mobile Infrastructure version: MI 70 SP 12 Patch 8 Build 200712271211

20080121 13:02:17:421 I MI/API/Logging ***** Current timezone: Europe/Prague20080121 13:02:17:421 I MI/API/Logging ***** Current Trace Level: 60

20080121 13:02:18:203 W MI/Services/Os ScriptManager found 0 scripts. Maybe script configuration is wrong?

20080121 13:02:23:140 W MI/API/Services Cannot delete target file (moveFileToDir): C:\Program Files\SAP Mobile Infrastructure (C)\lib\MDSD_21_SR02_501.jar

20080121 13:02:23:140 W MI/API/Services Move failed from C:\Program Files\SAP Mobile Infrastructure (C)\pending\MDSD_21_SR02_501.jar to C:\Program Files\SAP Mobile Infrastructure (C)\lib\MDSD_21_SR02_501.jar

20080121 13:02:23:140 E MI/Deployment com.sap.ip.me.core.InstallationException: Problems while installing MDSD_21_SR02_501 out of InstallationScenario DSK_UPGRADE2

com.sap.ip.me.core.InstallationException: Problems while installing MDSD_21_SR02_501 out of InstallationScenario DSK_UPGRADE2

at com.sap.ip.me.apps.InstallationScenarioApplicationType.install(InstallationScenarioApplicationType.java:196)

at com.sap.ip.me.apps.InstallationScenarioApplicationType.install(InstallationScenarioApplicationType.java:131)

at com.sap.ip.me.core.ApplicationManager.installApplication(ApplicationManager.java:789)

at com.sap.ip.me.core.InstallationSequenceInstallTrigger.continueInstallation(InstallationSequenceInstallTrigger.java:55)

at com.sap.ip.me.core.InstallationSequenceInstallTrigger.userLoggedOn(InstallationSequenceInstallTrigger.java:40)

at com.sap.ip.me.core.UserManagerImpl.fireLogon(UserManagerImpl.java:2336)

at com.sap.ip.me.core.UserManagerImpl.logOnUser(UserManagerImpl.java:785)

at com.sap.ip.me.core.UserManagerImpl.logOnUser(UserManagerImpl.java:763)

at com.sap.ip.me.awtapps.home.LoginDialog.actionOk(LoginDialog.java:377)

at com.sap.ip.me.awtapps.home.LoginDialog.exitDialogOk(LoginDialog.java:361)

at com.sap.ip.me.awtapps.home.AWTDialog.handleEvent(AWTDialog.java:99)

at java.awt.Window.postEvent(Window.java:1614)

at java.awt.Component.postEvent(Component.java:3895)

at java.awt.Component.postEvent(Component.java:3895)

at java.awt.Component.postEvent(Component.java:3895)

at java.awt.Component.dispatchEventImpl(Component.java:3631)

at java.awt.Component.dispatchEvent(Component.java:3477)

at java.awt.KeyboardFocusManager.redispatchEvent(KeyboardFocusManager.java:1713)

at java.awt.DefaultKeyboardFocusManager.dispatchKeyEvent(DefaultKeyboardFocusManager.java:627)

at java.awt.DefaultKeyboardFocusManager.preDispatchKeyEvent(DefaultKeyboardFocusManager.java:831)

at java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(DefaultKeyboardFocusManager.java:741)

at java.awt.DefaultKeyboardFocusManager.dispatchEvent(DefaultKeyboardFocusManager.java:592)

at java.awt.Component.dispatchEventImpl(Component.java:3506)

at java.awt.Component.dispatchEvent(Component.java:3477)

at java.awt.EventQueue.dispatchEvent(EventQueue.java:456)

at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)

at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)

at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:141)

at java.awt.Dialog$1.run(Dialog.java:540)

at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178)

at java.awt.EventQueue.dispatchEvent(EventQueue.java:454)

at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)

at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)

at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)

at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)

at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)

Nested exception:

com.sap.ip.me.core.InstallationException: Cannot download installation file

at com.sap.ip.me.core.AwtApplicationType.downloadInstallationFile(AwtApplicationType.java:349)

at com.sap.ip.me.core.AwtApplicationType.install(AwtApplicationType.java:62)

at com.sap.ip.me.core.ApplicationManager.installApplication(ApplicationManager.java:791)

at com.sap.ip.me.apps.InstallationScenarioApplicationType.install(InstallationScenarioApplicationType.java:189)

at com.sap.ip.me.apps.InstallationScenarioApplicationType.install(InstallationScenarioApplicationType.java:131)

at com.sap.ip.me.core.ApplicationManager.installApplication(ApplicationManager.java:789)

at com.sap.ip.me.core.InstallationSequenceInstallTrigger.continueInstallation(InstallationSequenceInstallTrigger.java:55)

at com.sap.ip.me.core.InstallationSequenceInstallTrigger.userLoggedOn(InstallationSequenceInstallTrigger.java:40)

at com.sap.ip.me.core.UserManagerImpl.fireLogon(UserManagerImpl.java:2336)

at com.sap.ip.me.core.UserManagerImpl.logOnUser(UserManagerImpl.java:785)

at com.sap.ip.me.core.UserManagerImpl.logOnUser(UserManagerImpl.java:763)

at com.sap.ip.me.awtapps.home.LoginDialog.actionOk(LoginDialog.java:377)

at com.sap.ip.me.awtapps.home.LoginDialog.exitDialogOk(LoginDialog.java:361)

at com.sap.ip.me.awtapps.home.AWTDialog.handleEvent(AWTDialog.java:99)

at java.awt.Window.postEvent(Window.java:1614)

at java.awt.Component.postEvent(Component.java:3895)

at java.awt.Component.postEvent(Component.java:3895)

at java.awt.Component.postEvent(Component.java:3895)

at java.awt.Component.dispatchEventImpl(Component.java:3631)

at java.awt.Component.dispatchEvent(Component.java:3477)

at java.awt.KeyboardFocusManager.redispatchEvent(KeyboardFocusManager.java:1713)

at java.awt.DefaultKeyboardFocusManager.dispatchKeyEvent(DefaultKeyboardFocusManager.java:627)

at java.awt.DefaultKeyboardFocusManager.preDispatchKeyEvent(DefaultKeyboardFocusManager.java:831)

at java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(DefaultKeyboardFocusManager.java:741)

at java.awt.DefaultKeyboardFocusManager.dispatchEvent(DefaultKeyboardFocusManager.java:592)

at java.awt.Component.dispatchEventImpl(Component.java:3506)

at java.awt.Component.dispatchEvent(Component.java:3477)

at java.awt.EventQueue.dispatchEvent(EventQueue.java:456)

at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)

at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)

at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:141)

at java.awt.Dialog$1.run(Dialog.java:540)

at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178)

at java.awt.EventQueue.dispatchEvent(EventQueue.java:454)

at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)

at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)

at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)

at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)

at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)

20080121 13:04:22:531 W MI/Sync Container Type:R,Id:47927980AECA0BA3E10000000A126235,SId:0,Items:0,MaxI:0 does not contain a conversation id, use defaull: MI46443032435a4558 / 4792758FAECA0BA3E10000000A126235 (User: FD02CZEX, MSD: Name: / MOBILEENGINE_AWT (V. 70128), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType)

Thanks and regards,

Frank

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • avatar image
    Former Member
    Jan 22, 2008 at 11:09 AM

    Hello Frank,

    For the first part of the problem "Cannot switch context because current conversation id is empty " please perform a client data reset which should solve the problem. For the download problem "Problems while installing MDSD_21_SR02_501 out of InstallationScenario DSK_UPGRADE2", please make sure download url for MDSD_21_SR02_501 works perfectly in an Internet explorer on the client device.

    Best Regards

    Sivakumar

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jan 22, 2008 at 06:37 PM

    Hi Siva,

    For the first error about the container, is it necessary to have a clean client when performing Application update after upload? If so, I think that there is missing execution of method reset on SyncManagerImpl.java after uplaod process is performed.? Could this be?. For the second error, I saw that the download path (webserver + webpath) led me to the jar file from which I generated the SDA, using Mobile Archive Convertor (however the name did not match with the name of the SDA). I 'll fix it and try again.

    Best regards,

    Frank

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Frank,

      just as a comment:

      A client reset is not always necessary after an application update. If you just update a view or so, that is absolutely fine. But if you change the persistence (MEREPMETA.XML) then you need the client reset. This reset reads the MEREPMETA file again and generates the persistence based on these informations. So this part is not really missing in the coding, cause you do not really know if this is necessary or not. On the other side: having the ability to trigger a client reset in the INSTALL.XML file would perhaps be a great option.

      Regards,

      Oliver

  • avatar image
    Former Member
    Jan 23, 2008 at 10:02 AM

    I agree, if the application contains changes for the SyncBO definitions and new MEREPMETA.xml is generated, then a client reset will be performed. Although, if this is not the case, do you recommend to change the install.xml to perform a client reset in any case scenario? Is the change relevant also for updating the application using Role Synchronization?

    Thanks and regards,

    Frank

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Frank,

      well, I do not know if it is possible to do that change in the INSTALL.XML file. If it is and you do that change, then off course it will effect as well your role sync.

      But what is the issue with doing the reset manually? You do that update out in the filed? I thought it is a new installation.

      Regards,

      Oliver

  • avatar image
    Former Member
    Jan 23, 2008 at 02:06 PM

    Yes Oliver,

    The update will be done in the field (productive) as standard procedure decribed in the Technology Consultant guide. Is the standard procedure without user interaction, to update the application using Enable Patch Download = true in the mobileengine.config file.

    Best regards,

    Frank

    Add comment
    10|10000 characters needed characters exceeded