cancel
Showing results for 
Search instead for 
Did you mean: 

MDSD 2.1 application starts but does not respond

Former Member
0 Kudos

Hi,

I am having a problem with the DSD application on a mobile device.

I have loaded the:

JVM

DB2e

MI

MDSD 2.1

onto the mobile device (the mobile has been restarted after each application has been loaded)- the backend has been confiereged using the configeration guide.

When I start the application in MI by selecting the MDSD button the mobile device shows a processing icon (like egg timer) but progresses no further and does not exit this state.

In addittion I cannot locate any error logs that identify why the application has appeared to stop.

Help on this would very much be apprechiated!

Thanks James

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hello James,

You said on the click of the MDSD button on the MI Home screen the app shows the wait cursor and does not move. Please set the trace level to "All" in the the MI Home menu Settings -> Trace and then click on the MDSD button. And send the trace. Based on the logs I will be able to exactly tell you what needs to be done.

Regards

Anup

http://www.indience.com

http://www.indience.com/index.php/products/mobile-direct-store-delivery.html

/people/sridhar.dilip/blog/2009/05/04/sap-mdsd-integration-with-sap-crm-survey-suite

Former Member
0 Kudos

Hi

The log reads:

[20090608 11:08:45:254] W [MI/CCMS ] File not found during Config Info collection: /Windows/Start Menu/MIServer.lnk

[20090608 11:13:47:325] W [MI/Core ] The SSL support feature is not properly configured. Https is not available.

[20090608 11:14:50:644] W [MI/Security ] Error while creating MIAUTH sync bo (no SyncBoDescriptor for MIAUTH available); contact SAP support

[20090608 11:14:50:660] W [MI/Security ] Cannot start authority query for user because SyncBoDescriptor for MIAUTH is not available

[20090608 11:19:33:672] W [MI/Core ] The SSL support feature is not properly configured. Https is not available.

[20090608 11:20:51:723] W [MI/Security ] Error while creating MIAUTH sync bo (no SyncBoDescriptor for MIAUTH available); contact SAP support

[20090608 11:20:51:743] W [MI/Security ] Cannot start authority query for user because SyncBoDescriptor for MIAUTH is not available

Thanks James

Former Member
0 Kudos

hi

The trace file;

[20090608 11:05:39:917] I [MI/API/Logging ] ***** LOG / TRACE SWITCHED ON

[20090608 11:05:39:917] I [MI/API/Logging ] ***** Mobile Infrastructure version: MI 70 SP 15 Patch 3 Build 200903191315

[20090608 11:05:39:917] I [MI/API/Logging ] ***** Current timezone: GMT[20090608 11:05:39:917] I [MI/API/Logging ] ***** Current Trace Level: 50

[20090608 11:08:45:260] E [MI/CCMS ] Config Info: /Windows/Start Menu/MIServer.lnk

[20090608 11:08:45:263] E [MI/CCMS ] java.io.FileNotFoundException: /Windows/Start Menu/MIServer.lnk

java.io.FileNotFoundException: /Windows/Start Menu/MIServer.lnk

at java.io.FileInputStream.<init>()

at java.io.FileInputStream.<init>()

at java.io.FileReader.<init>()

at com.sap.ip.me.ccms.configinfo.ConfigInfoCollector.addMobileEngineLnk()

at com.sap.ip.me.ccms.configinfo.ConfigInfoCollector.addConfigInfoToContainer()

at com.sap.ip.me.ccms.configinfo.ConfigInfoCollector.createConfigInfoContainer()

at com.sap.ip.me.ccms.configinfo.ConfigInfoCheckerInboundProcessor.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.access$000()

at com.sap.ip.me.awtapps.home.HomeFrame$SyncThread.run()

at java.lang.Thread.run()

Former Member
0 Kudos

Hello Richard,

The issue is you are not using IBM DBe2 persistence in this installation, The file IO option is enabled by default and does not work with SAP MDSD.

So you have to redo the complete MI install except the Crème installation.

Install:

1. MI cab

2. Assign and Download DB2e add-on 8.2.4 or 9.0 from the NetWeaver Admin console to the MI installation. This installs asks you to restarts the MI etc .

3. Assign and Download MDSD component to the MI install.

Regards

Anup

Former Member
0 Kudos

Hi Anup,

I will do that, please can you let me know why installing the Db2e CAB file manually does not work and how you can tell it was this component that is causing the issue?

Thanks James

Former Member
0 Kudos

Hello James,

If you talking about installing the DB2e cab provided by IBM, The MI cannot know that such thing is available and will not use it. It can only identify add-ons which are deployed via SAP MI and loads them accordingly.

These addons also come with some preoperty settigns etc which also important for the MI during runtime.

You have to get a copy of this db2e add-on from SAP again.

Regards

Anup

.

Former Member
0 Kudos

Hi Akil

MI 7.0 (Latest patch)

DB2e 9.1.2

and the maifest on the device is:

Manifest-Version: 1.0

Ant-Version: Apache Ant 1.6.4

Created-By: 1.4.2_12-b03 (Sun Microsystems Inc.)

Implementation-Version: official

Specification-Title: Mobile Direct Store Delivery

Specification-Version: 2.1

Implementation-Title: com.sap.dsd.appctrl.DSDMain

Main-Class: com.sap.dsd.appctrl.DSDMain

Implementation-Vendor-Id: sap.com

ApplicationClass: com.sap.dsd.appctrl.DSDMain

Implementation-Vendor: SAP

Description: Mobile Direct Store Delivery

Specification-Vendor: SAP AG

Build-ID: 2.1.00.112755

Thanks James

Former Member
0 Kudos

Hi ,

CrEme,

V3.29 B142

Java 3.1, OS 5.2

Thanks James

Former Member
0 Kudos

Hi James,

SAP has recommended Creme 3.27a until and unless we have specific requirements.

I am also suddenly facing this problem today.

I am using creme 3.27a

MDSD2.1 sr01

db2e914

which Core file(.cab ) u are using can u semd me the name and also the SP level u are in..

Regards,

Akhil

Former Member
0 Kudos

Hi,

We are on P15 and I downloaded and used the MI client for the same patch level:

Thanks James

Former Member
0 Kudos

Dear James,

I was facing the same problem...but its solved now.

Steps i performed.

Removed Creme and core_Core.cab file.

removed MI folder

Hard Reset the PDA

again installed creme 3.27a

core_core.cab

db2e

MDSD2.1

And now its working and initialising also.

Hope it helps,

Regards,

Akhil

Former Member
0 Kudos

Dear James,

You are on what Sp levels at both server and mobile client.

What is WM version u use.

1 creme( Which version )

2 MAP70.....core.core.cab

3 DB2e

4 MDSD2.1 application

Regards,

Akhil

Edited by: Akhil Rastogi on Jun 3, 2009 11:00 AM

Edited by: Akhil Rastogi on Jun 3, 2009 11:02 AM