cancel
Showing results for 
Search instead for 
Did you mean: 

Configuration aborted due to non-existing MCD..?

Former Member
0 Kudos

Hi folks,

Do anybody have an idea what does this means (the configuration seems OK and the MCD of DB2E is existant and seems OK, I checked it via MI_MCD as well):

[20071029 15:30:08:664] E [MI/Deployment ] ERROR_MESSAGES: Installation file does not exist. Upload the file.

[20071029 15:30:10:910] E [MI/Deployment ] com.sap.ip.me.core.InstallationException: Installation of MAM_CONF_PT1 is aborted because it contains dependency to non-existing Mobile Component Descriptor DB2E

com.sap.ip.me.core.InstallationException: Installation of MAM_CONF_PT1 is aborted because it contains dependency to non-existing Mobile Component Descriptor DB2E

at com.sap.ip.me.apps.InstallationScenario.initializeInstallationOrder()

at com.sap.ip.me.apps.InstallationScenario.initialize()

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.apps.jsp.Home$SyncRunnable.run()

at java.lang.Thread.run()

Nested exception:

java.lang.NullPointerException

at com.sap.ip.me.apps.InstallationScenario.initializeInstallationOrder()

at com.sap.ip.me.apps.InstallationScenario.initialize()

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.apps.jsp.Home$SyncRunnable.run()

at java.lang.Thread.run()

Thanks & regards,

Lalo

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Lalo

This problem has already been resolved. Can you please let me know which version of MI you are using, the SP level and also the patch so that i can recommend the patch that has this solution.

Best Reagards

Sivakumar

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Sivakumar,

Actually we are using the SAP MI 7.00 SP13 PL 0 and the latest MAM3.0 SR4, PL6..

I think it is one of the latest MI client installations available as well, right ..? Is it fixed later..

Thanks for your willingness to help,

Lalo

rajan_venkatachalam
Participant
0 Kudos

Hi Lalo,

Have you by any chance tried to download the DB2E directly from webserver url ,if not follow the below steps

1- open table MEMSD_CUST

2-provide the name of the MCD against the name field and version if you know,in your case it might be DB2E

3- execute.

4- Change the width from 0250 ->1250.

5-Concatnate the value of WEBSERVER+WEBPATH

Open a browser with the above url,you would be getting the file.If not re upload the DB2E again through Admin UI or webconsole.

you can also get the URL(WEBSERVER+WEBPATH) in Admin UI by providing the name of the MCD in Mobile Component page.

Thanks and Regards,

Rajan