cancel
Showing results for 
Search instead for 
Did you mean: 

PIOS connector not deployed in MI 7.0 SP 10 Patch3

Former Member
0 Kudos

Hi all

We are using PIOS connector and driver to activate the scanner in our device Symbol 9090. Though we did some manual copying of files, it was working fine when we were using MI7.0 SP10 and Patch 1. But the connector is not getting installed completely after we applied the Patch3, even if the synchronization says successful for the connector component. Do any body have faced similar problem?

Thanks

Raj

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Raj

Please implement note 995387. For further information please see my reply in thread Make sure you are using Creme 3.27A and also have increased the memory by setting the -ml parameter. Hope this helps you in solving the problem.

Best Regards

Sivakumar

Former Member
0 Kudos

Hi Sivakumar

Tried applying the note 995387. As mentioned I was not able to edit the shortcut MIServer.lnk file in \Windows\StartUp. But I was able to do -ml 60000 in CrEme Console by executing the CrEme found in \Windows\CrEme\bin and I was able to see the below

NSIcom Ltd., CrEme(tm)

CrEme J2ME(tm)

CrEme V3.27a B102.020706 02-Jul-2006

MemoryLimit=60000K

But in jspcout file the following is seen

NSIcom Ltd., CrEme(tm)

CrEme J2ME(tm)

CrEme V3.27a B102.020706 02-Jul-2006

MemoryLimit=29184Kb

I am not sure whether the memory used by CrEme is increased. Please advice.

Thanks

Raj

Former Member
0 Kudos

Hi Raj,

I do not think that the memory allocation has increased, you can copy the MIServer.lnk back to your PC and edit it using Notepad, it is simple to do. Add -ml 64000 to it.

After you edit it put it back in the same location in the device.

Let me know if this is not possible.

Best Regards,

Karthik

Former Member
0 Kudos

Karthik,

When i look up the MIserver on the PDA through the active sync,Its seen as a shortcut. When i copy it to my desktop,its still a shortcut.I am not able to edit it using a NOTEPAD.

Any other thoughts from anyone with reference to how to set the JVM memory? We are on cremE 3.27a on a symbol MC9094 device(On WM5.0 with AKU3.5) with 128Mb RAM and on MI7.0SPS10 Client patch 3. Is there a method to edit the JVM at the registry level for this?

Interestingly, we dont have this issue on MI7.0SPS10 client patch 1 on this device.The connector gets deployed properly with JVM being allocated with 28 MB RAM.

Any help would be appreciated.

Thanks

Narasimhan

Former Member
0 Kudos

Hi Narasimhan

Although the MIServet.lnk is a shortcut when copied on to the desktop, you can still edit the same. Select the file, right click and choose the option Send To ->Notepad. Now add the -ml parameter. Or just create a file with the following contents and rename the file a as MIServer.lnk <i><b>255#"\Windows\CrEme\bin\CrEme.exe" -ml 64000 -Of -cf MI\creme_listOfJars.txt com.sap.ip.me.core.Startup -home:/MI</b></i>. Copy this file to \Windows\Startup and delete the old one. This should do the trick

Best Regards

Sivakumar

Former Member
0 Kudos

Sivakumar,

Thanks for the explicit reply.It helped a lot.I was able to edit the MIServer.Ink and increase the JVM memory to 40MB,60MB and 75 MB.However we are still having the same issue.The connector isnt getting deployed properly and the status remains as "Deployment activated" in the NWADMIN.

However on the MI_CLOGMON transaction i am able to error message indicating "Exception while trying to install application CONNECTOR_WM50_XSL_CRM (root cause: Problems while loading external installer of ADDON [com.sap.ip.me.core.InstallationException])". On the trace file on the client i am also able to see "ABACO Installtion message: The following error occured during the EXECUTE process java.lang.Exception: Exception on method loadProxyLibrary. The library (piosinstall) could not be found at com.sap.ip.me.api.pios.install.AddOnImplementation.LoadProxyLibrary().

Repeated sync results in error on MI_CLGMON transaction "Problems while loading external installer of ADDON (root cause: Installation of (CONNECTOR_WM50_XSL_CRM1) cannot proceed because the same or another version already exists. To re-install the application please uninstall the current version and then proceed with the installation. [java.lang.Exception])".

Any ideas or help in resolving the same? Is there any other workaround on this?

Thanks

Narasimhan

Former Member
0 Kudos

Hi all,

Eventhough we had the increased the Creme memory to 114000Kb (-ml 114000) , the connector still isnt getting installed properly. We have the same issue on windows mobile 2003 enviroinment. Both these devices are symbol mc9090 and mc9060 devices with 128 MB RAM supported by sap on this version.

We also tried installing CreMe 3.29 version from NSI and here again with 114 MB allocated to CreMe, The connector installation wasnt succesfull.

Any thoughts or suggestions?

Regards

Narasimhan

Former Member
0 Kudos

Hi All,

I have the same problem ....

Did you find any way of fixing it ???

Regards

nana

Former Member
0 Kudos

Hi all

Upgrade to SPS10 Patch 05(the latest patch on this SP) and this will solve your problem.

Best Regards

Sivakumar

Former Member
0 Kudos

Hi,

I installed MI 70 SP 10 Patch 5 Build

But there is no difference.

Here is the log:

[20070528 07:19:27:250] I [MI/API/Logging ] ***** LOG / TRACE SWITCHED ON

[20070528 07:19:27:250] I [MI/API/Logging ] ***** Mobile Infrastructure version: MI 70 SP 10 Patch 5 Build 200705151251

[20070528 07:19:27:250] I [MI/API/Logging ] ***** Current timezone: ART[20070528 07:19:27:250] I [MI/API/Logging ] ***** Current Trace Level: 50

[20070528 07:21:54:000] E [MI/PIOS ] ABACO Installation Message: The following error ocurred during the INSTALLATION process java.lang.Exception: Installation of (CONNECTOR_WM50_XSL_CRM1) cannot proceed because the same or another version already exists. To re-install the application please uninstall the current version and then proceed with the installation.

at com.sap.ip.me.api.pios.install.AddOnDetail.install()

at com.sap.ip.me.api.pios.install.AddOn.install()

at com.sap.ip.me.api.pios.install.AddOnImplementation.install()

at com.sap.ip.me.core.AddonApplicationType.callExternalInstaller()

at com.sap.ip.me.core.AddonApplicationType.extractInstallationFile()

at com.sap.ip.me.core.AddonApplicationType.install()

at com.sap.ip.me.core.ApplicationManager.installApplication()

at com.sapmarkets.web.liTS.util.reg.RegistrySyncInboundProcessing.installApplicationFromMSD()

at com.sapmarkets.web.liTS.util.reg.RegistrySyncInboundProcessing.installMSDs()

at com.sapmarkets.web.liTS.util.reg.RegistrySyncInboundProcessing.startApplicationInstallation()

at com.sapmarkets.web.liTS.util.reg.RegistrySyncInboundProcessing.startInstallationViaMSD()

at com.sapmarkets.web.liTS.util.reg.RegistrySyncInboundProcessing.process()

at com.sap.ip.me.sync.SyncManagerImpl.processSingleContainer()

at com.sap.ip.me.sync.SyncManagerMerger.processInboundContainers()

at com.sap.ip.me.sync.SyncManagerImpl.processSyncCycle()

at com.sap.ip.me.sync.SyncManagerImpl.syncForUser()

at com.sap.ip.me.sync.SyncManagerImpl.processSynchronization()

at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend()

at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend()

at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend()

at com.sap.ip.me.awtapps.home.Home.doSync()

at com.sap.ip.me.awtapps.home.HomeFrame.doUserActionSync()

at com.sap.ip.me.awtapps.home.HomeFrame.userActionSync()

at com.sap.ip.me.awtapps.home.HomeFrame.action()

at java.awt.Component.handleEvent()

at com.sap.ip.me.awtapps.home.HomeFrame.handleEvent()

at java.awt.Window.postEvent()

at java.awt.Component.postEvent()

at java.awt.Component.postEvent()

at java.awt.Component.postEvent()

at java.awt.Component.dispatchEventImpl()

at java.awt.Component.dispatchEvent()

at java.awt.EventDispatchThread.run()

[20070528 07:21:54:011] E [MI/PIOS ] ABACO Installation Message: ROLLBACK EXECUTED SUCCESSFULY !!!

[20070528 07:21:54:034] E [AppLog/MI/Core ] Problems while loading external installer of ADDON

java.lang.Exception: Installation of (CONNECTOR_WM50_XSL_CRM1) cannot proceed because the same or another version already exists. To re-install the application please uninstall the current version and then proceed with the installation.

at com.sap.ip.me.api.pios.install.AddOnImplementation.install()

at com.sap.ip.me.core.AddonApplicationType.callExternalInstaller()

at com.sap.ip.me.core.AddonApplicationType.extractInstallationFile()

at com.sap.ip.me.core.AddonApplicationType.install()

at com.sap.ip.me.core.ApplicationManager.installApplication()

at com.sapmarkets.web.liTS.util.reg.RegistrySyncInboundProcessing.installApplicationFromMSD()

at com.sapmarkets.web.liTS.util.reg.RegistrySyncInboundProcessing.installMSDs()

at com.sapmarkets.web.liTS.util.reg.RegistrySyncInboundProcessing.startApplicationInstallation()

at com.sapmarkets.web.liTS.util.reg.RegistrySyncInboundProcessing.startInstallationViaMSD()

at com.sapmarkets.web.liTS.util.reg.RegistrySyncInboundProcessing.process()

at com.sap.ip.me.sync.SyncManagerImpl.processSingleContainer()

at com.sap.ip.me.sync.SyncManagerMerger.processInboundContainers()

at com.sap.ip.me.sync.SyncManagerImpl.processSyncCycle()

at com.sap.ip.me.sync.SyncManagerImpl.syncForUser()

at com.sap.ip.me.sync.SyncManagerImpl.processSynchronization()

at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend()

at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend()

at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend()

at com.sap.ip.me.awtapps.home.Home.doSync()

at com.sap.ip.me.awtapps.home.HomeFrame.doUserActionSync()

at com.sap.ip.me.awtapps.home.HomeFrame.userActionSync()

at com.sap.ip.me.awtapps.home.HomeFrame.action()

at java.awt.Component.handleEvent()

at com.sap.ip.me.awtapps.home.HomeFrame.handleEvent()

at java.awt.Window.postEvent()

at java.awt.Component.postEvent()

at java.awt.Component.postEvent()

at java.awt.Component.postEvent()

at java.awt.Component.dispatchEventImpl()

at java.awt.Component.dispatchEvent()

at java.awt.EventDispatchThread.run()

[20070528 07:21:54:159] E [AppLog/MI/Deployment ] Exception while trying to install application CONNECTOR_WM50_XSL_CRM

com.sap.ip.me.core.InstallationException: Problems while loading external installer of ADDON

at com.sap.ip.me.core.AddonApplicationType.extractInstallationFile()

at com.sap.ip.me.core.AddonApplicationType.install()

at com.sap.ip.me.core.ApplicationManager.installApplication()

at com.sapmarkets.web.liTS.util.reg.RegistrySyncInboundProcessing.installApplicationFromMSD()

at com.sapmarkets.web.liTS.util.reg.RegistrySyncInboundProcessing.installMSDs()

at com.sapmarkets.web.liTS.util.reg.RegistrySyncInboundProcessing.startApplicationInstallation()

at com.sapmarkets.web.liTS.util.reg.RegistrySyncInboundProcessing.startInstallationViaMSD()

at com.sapmarkets.web.liTS.util.reg.RegistrySyncInboundProcessing.process()

at com.sap.ip.me.sync.SyncManagerImpl.processSingleContainer()

at com.sap.ip.me.sync.SyncManagerMerger.processInboundContainers()

at com.sap.ip.me.sync.SyncManagerImpl.processSyncCycle()

at com.sap.ip.me.sync.SyncManagerImpl.syncForUser()

at com.sap.ip.me.sync.SyncManagerImpl.processSynchronization()

at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend()

at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend()

at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend()

at com.sap.ip.me.awtapps.home.Home.doSync()

at com.sap.ip.me.awtapps.home.HomeFrame.doUserActionSync()

at com.sap.ip.me.awtapps.home.HomeFrame.userActionSync()

at com.sap.ip.me.awtapps.home.HomeFrame.action()

at java.awt.Component.handleEvent()

at com.sap.ip.me.awtapps.home.HomeFrame.handleEvent()

at java.awt.Window.postEvent()

at java.awt.Component.postEvent()

at java.awt.Component.postEvent()

at java.awt.Component.postEvent()

at java.awt.Component.dispatchEventImpl()

at java.awt.Component.dispatchEvent()

at java.awt.EventDispatchThread.run()

null

null

Former Member
0 Kudos

Nana,

We had similar issues on Patch level 3, but installation of patch level 4 solved the proble for us. We havent tried the same out with patch level 5. Also we were using connector CONNECTOR_WM50_XSL_CRM and not CONNECTOR_WM50_XSL_CRM1. I am not sure whats the difference between them.

However, before you tried re-installing the new patch, did you completely uninstall the old patch level, delete the MI folders and re-start the device, before installing the new patch? Also whats the device that you are using? Also did you increase the memory allocation for Java as indicated above? That seems to have helped others. Also we have noticed sometimes that the deployment of the Connector and the addon together results in successfull installtion of the Addon. Our experience have shown that,Everything seems to be device and OS patch level specific, eventhough it isnt supposed to be so since we are using the same JVM across the products.

If its a Intermec or a symbol device you can totally get away from installing the connector and driver by installing other barcode reader software from the manufacturer.It seems to use the same amount of RAM(1 to 2MB RAM) . The tools can be downloaded from the respective developer zones.This also gives you the flexibility to use the barcode reader for all text fields without adding specific programming to each screen and fields. Thats the direction we are heading out using this solution.

Hope it helps.

Thanks

Narasimhan