User ID has sap* rights and I get this...

[Former Member]

• Synchronization started.

• Connection set up (without proxy) to: http://ap-ccms-d01:50000/meSync/servlet/meSync?~sysid=DMI&;

• Successfully connected with server.

• Processing of inbound data began.

• Server logon failed.

Not experienced with SAP MI and I do not understand why it fails to log me on. I also have S_ME_SYNC and S_RFC authorizations. Has anyone encounter this issue? Please let me know how it can be solved.

Besides creating the roles, service users is there anyting else that needs to be done on the server side?

thanks,

.adrian

[Former Member]

thanks all

[Former Member]

The file name was in upper case and now I have change it. It did not solve the issue. I also have tried to put the IP address of the server. Also no success.

[Former Member]

Hello there.

First let me thank everyone for your sugestions.

However I still have this issue. I have created a new user with sap_all authorization, it did not work, then I give that user the othe authorizations and it still does not work.

I have found some other people that experieced this issue and they sugested to look under misync.test fiel to see that log. Over there I have this king of logs:

#1.5#0050568D20FC00480000000700001B1C0003F6FEDE10F42B#1115999437912#com.sap.ip.mi.misync.ServletWafSync#sap.com/com.sapmarkets.mesyncjco#com.sap.ip.mi.misync.ServletWafSync.doget [abertisan]#J2EE_GUEST#2####c02aed80c3c611d9c2460050568d20fc#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###'ashost' is missing#

#1.5#0050568D20FC003F0000000700001B1C0003F6FEDE3AD72D#1115999440662#com.sap.ip.mi.misync.ServletWafSync#sap.com/com.sapmarkets.mesyncjco#com.sap.ip.mi.misync.ServletWafSync.doget [abertisan]#J2EE_GUEST#2####c1ce8b60c3c611d99b560050568d20fc#SAPEngine_Application_Thread[impl:3]_37##0#0#Error##Plain###'ashost' is missing#

#1.5#0050568D20FC003A0000001500001B1C0003F6FEDE58DB86#1115999442631#com.sap.ip.mi.misync.ServletWafSync#sap.com/com.sapmarkets.mesyncjco#com.sap.ip.mi.misync.ServletWafSync.doget [abertisan]#J2EE_GUEST#2####c2fafd70c3c611d9c8c40050568d20fc#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###'ashost' is missing#

#1.5#0050568D20FC00490000000A00001B1C0003F6FEDF0CE5C4#1115999454412#com.sap.ip.mi.misync.ServletWafSync#sap.com/com.sapmarkets.mesyncjco#com.sap.ip.mi.misync.ServletWafSync.doget [abertisan]#J2EE_GUEST#2####ca00a0c0c3c611d9923d0050568d20fc#SAPEngine_Application_Thread[impl:3]_38##0#0#Error##Plain###'ashost' is missing#

I have setup the file DMI.props and those are the contents of that file:

ashost=ap-ccms-d01.corp.se.sempra.com

sysnr=01

MobileInfrastructure.Sync.ServiceUserName=MI_SERVICE

MobileInfrastructure.Sync.ServicePassword=mypassword

The only diference is that in the instructions manual it states that the file is located ...\j2ee\cluster\server0\apps\sap.com\com.sapmarkets.mesyncjco.misync\servlet_jsp\meSync\root\System_Properties

while I have it under:

...\j2ee\cluster\server0\apps\sap.com\com.sapmarkets.mesyncjco\servlet_jsp\meSync\root\System_Properties

I'm not sure if this is a instalation error or is a typo in hte manual. Can someone check where the .props file should be located?

[Former Member]

Hi

I’ve also this difference (Post May 13, 2005 12:03 PM).

You should try write:

+ashost=ap-ccms-d01.corp.se.sempra.com

sysnr=00+

in DMI.props, because in url you’ve got http://ap-ccms-d01:50000/meSync/servlet/meSync?~sysid=DMI&, so I conclude that your system number is 00.

Message was edited by: £ukasz Kryœ

Message was edited by: £ukasz Kryœ

Message was edited by: £ukasz Kryœ

[Former Member]

HI

An easy way would be to give SAP_ALL authorization object to the user.(if possible)

It,as u can sense will always work

rgds

Harsh Chauhan

[Former Member]

Hi!

With reference to

"User has not been installed on MW, it is not ready for sync :ABERTISA"

MW is Middleware which refers to your MI Server.You did mention in your first post that the user is assigned with the Role that has Auth.Objects S_ME_SYNC,S_RFC,S_TCODE right? Has anything changed with the user auth? Also, before your first post you were getting the message "Server Logon Failed?" and now after doing all the checks per the earlier posts you are getting "User has not been installed on MW, it is not ready for sync :ABERTISA", Correct?

Could you confirm that your User Id / Password is same for MI Client and MI Server and that nothing has changed with the roles after your first post.

[Former Member]

I get both messages. The Server logon failed is displayed right away on the same screen while if I look at the trace for that syncronization atempt I see the other message.

The User ID and passwords are exactly the same in server and the client.

[Former Member]

Hi Adrian!

I have my *.props file under this folder.

".....\j2ee\cluster\server0\apps\sap.com\com.sapmarkets.mesyncjco\servlet_jsp\meSync\root\System_Properties\*.props"

Where * is my system id in lower case.

Also, if you have not tried this,You can test the Synchronization without MI Client by typing the below URL

"http://netweaver02:50000/meSync/servlet/meSync?_sysid=dev&login=sganesan&_{password=123&}client=100&_language=en&acknowledge=X&~test=true&"

Watch the URL typed in,it is CASE SENSITIVE.

If it is successfull you will see the message "&WAF_SYNC&STATUS=&Execution Time= & HeaderType = MEREPLICATION &MORE_PACKAGES_WAITING = & "

Else.

Error Message.

If this test works,make sure you have the props file name is the name you have defined for sysid in the URL(Case Sensitive).

Regards,

Gisk

[Former Member]

I have done all the steps recomended in the last post. I uninstaled MI and installed again (this time I instaled the AWT version). I get the same result. Logon to server failed...

Please let me know if anyone has any other sugestions.

I still do not know what MW means. "User has not been installed on MW, it is not ready for sync :ABERTISA"

[Former Member]

Hi Adrian,

I have faced exactly same problem. It is an authorization issue only. Please ensure that your user has at least following authorizations:

1. S_ME_SYNC

2. S_RFC

3. S_TCODE

Above mentioned objects are required for MI operations. If you want to administer also, add following objects as well

4. S_MI_MGMT - for device administration and configuration

5. S_MI_CCMS - for customization of alerts and display of alerts in the Alert Monitor

6. S_MI_ALERT - for customizing of alerts

7. S_DATASET - storage of alerts on the server

With this I'm sure your problem will get solved.

Regards,

Ravi Sharma

[Former Member]

Hi,

This si the trace file:

[20050512 18:19:17:248] I [MI/API/Logging ] ***** LOG / TRACE SWITCHED ON

[20050512 18:19:17:248] I [MI/API/Logging ] ***** Mobile Engine version: MI 25 SP 09 Patch 00 Build 200409101427

[20050512 18:19:17:248] I [MI/API/Logging ] ***** Current timezone: America/Los_Angeles

[20050512 18:19:17:248] I [MI ] Trace severity: All (1000)

[20050512 18:19:17:248] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/trace/trace.jsp'

[20050512 18:19:23:248] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'

[20050512 18:19:23:248] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doPost(...) called

[20050512 18:19:23:248] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = 'tracesendToR3'

[20050512 18:19:23:248] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/trace/trace.jsp'

[20050512 18:19:33:201] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'

[20050512 18:19:33:201] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called

[20050512 18:19:33:201] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''

[20050512 18:19:33:201] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp'

[20050512 18:19:34:123] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'

[20050512 18:19:34:123] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called

[20050512 18:19:34:123] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''

[20050512 18:19:34:154] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/home/syncpassword.jsp'

[20050512 18:19:38:233] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'

[20050512 18:19:38:233] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doPost(...) called

[20050512 18:19:38:233] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''

[20050512 18:19:38:264] P [MI/Sync ] Notify R3 called

[20050512 18:19:38:264] D [MI/Sync ] There is already a container for method WAF_REGISTRY and user ABERTISA in the outbound queue

[20050512 18:19:38:264] D [MI/API/Services ] MEResourceBundle:Constructor: Create MEResourceBundle(com/sap/ip/me/awtapps/home/mobile_engine, en_US, (null))

[20050512 18:19:38:264] D [MI/API/Services ] MEResourceBundle:Constructor: Use classloader com.sap.ip.me.core.Startup@1004901

[20050512 18:19:38:264] D [MI/API/Services ] CREATED MEPropertyResourceBundle com.sap.ip.me.api.services.MEResourceBundle$MEPropertyResourceBundle@1a85d38 for bundleName: com/sap/ip/me/awtapps/home/mobile_engine with Locale: _en

[20050512 18:19:38:264] I [MI/Sync ] Synchronize with backend called, Thread=Thread-28

[20050512 18:19:38:264] I [MI/Sync ] Thread=Thread-28 took lock for synchronizeation.

[20050512 18:19:38:264] D [MI/Sync ] Synchronisation: Fire SyncEvent 0

[20050512 18:19:38:264] P [MI/Core ] Thread Thread-28 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)

[20050512 18:19:38:264] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.sync.LogSender

[20050512 18:19:38:264] P [MI/Core ] original context restored

[20050512 18:19:38:264] P [MI/Core ] Thread Thread-28 switched context to MI4142455254495341 / MI4142455254495341 (User: ABERTISA, MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)

[20050512 18:19:38:264] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.apps.jsp.SyncStatus

[20050512 18:19:38:264] P [MI/Core ] original context restored

[20050512 18:19:38:264] P [MI/Core ] Thread Thread-28 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)

[20050512 18:19:38:264] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.ccms.LastSuccessfulSyncAlert

[20050512 18:19:38:264] P [MI/Core ] original context restored

[20050512 18:19:38:264] P [MI/Core ] Thread Thread-28 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)

[20050512 18:19:38:264] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.services.os.AgentManager

[20050512 18:19:38:279] D [MI/API/Services ] CREATED parent MEPropertyResourceBundle for child bundle: com.sap.ip.me.api.services.MEResourceBundle$MEPropertyResourceBundle@1a85d38 using bundle name: com/sap/ip/me/awtapps/home/mobile_engine

[20050512 18:19:38:279] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp'

[20050512 18:19:38:279] P [MI/Sync ] Created outbound container for user (SHARED) and method AGENT_PARAMETERS

[20050512 18:19:38:279] P [MI/Core ] original context restored

[20050512 18:19:38:279] P [MI/Core ] Thread Thread-28 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)

[20050512 18:19:38:279] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.core.StatusUpdater

[20050512 18:19:38:279] P [MI/Core ] original context restored

[20050512 18:19:38:279] P [MI/Core ] Thread Thread-28 switched context to MI4142455254495341 / MI4142455254495341 (User: ABERTISA, MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)

[20050512 18:19:38:279] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.smartsync.core.SmartSyncRuntimeManager

[20050512 18:19:38:279] D [MI/Smartsync ] User has not been installed on MW, it is not ready for sync :ABERTISA

[20050512 18:19:38:279] P [MI/Core ] original context restored

[20050512 18:19:38:279] P [MI/Core ] Thread Thread-28 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)

[20050512 18:19:38:279] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.ccms.AlertManager

[20050512 18:19:38:279] P [MI/Core ] original context restored

[20050512 18:19:38:279] P [MI/Sync ] Synchronization started for user (SHARED)

[20050512 18:19:38:279] D [MI/Sync ] PackageManager: old package file C:\Program Files\SAP Mobile Infrastructure\sync\(SHARED)\out\package.out could not be deleted

[20050512 18:19:38:279] D [MI/Sync ] PackageManager: create package with maximum 2147483647 items

[20050512 18:19:38:311] D [MI/Sync ] PackageManager: filled package with 0 acknowledge received container(s)

[20050512 18:19:38:311] D [MI/Sync ] PackageManager: filled package with 0 acknowledge container(s)

[20050512 18:19:38:342] D [MI/Sync ] PackageManager: filled package with 72 container items or headers

[20050512 18:19:38:342] D [MI/Sync ] PackageManager: filled package with 1 notify container(s)

[20050512 18:19:38:342] D [MI/Sync ] Package file C:\Program Files\SAP Mobile Infrastructure\sync\(SHARED)\out\package.out exists and can be read

[20050512 18:19:38:342] P [MI/Sync ] Synchronisation started

[20050512 18:19:38:342] D [MI/Sync ] Dumping file 'C:\Program Files\SAP Mobile Infrastructure\sync\(SHARED)\out\package.out'

INH-H[1]=0103ccd845dc23221935;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[1]=0103ccd845dc23221935;TIMESTAMP;0;000000;19700101&INB-B[2]=0103ccd845dc23221935;DEVICEID;0;&INB-B[3]=0103ccd845dc23221935;USER;0;ABERTISA&INH-H[2]=0103ccdaa04bda7b4f1e;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[4]=0103ccdaa04bda7b4f1e;TIMESTAMP;0;000000;19700101&INB-B[5]=0103ccdaa04bda7b4f1e;DEVICEID;0;&INB-B[6]=0103ccdaa04bda7b4f1e;USER;0;ABERTISA&INH-H[3]=0103ccde64db45e939f9;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[7]=0103ccde64db45e939f9;TIMESTAMP;0;000000;19700101&INB-B[8]=0103ccde64db45e939f9;DEVICEID;0;&INB-B[9]=0103ccde64db45e939f9;USER;0;ABERTISA&INH-H[4]=0103ccdf0487191e79ad;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[10]=0103ccdf0487191e79ad;TIMESTAMP;0;000000;19700101&INB-B[11]=0103ccdf0487191e79ad;DEVICEID;0;&INB-B[12]=0103ccdf0487191e79ad;USER;0;ABERTISA&INH-H[5]=0103ccdfce6f7d45e0d3;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[13]=0103ccdfce6f7d45e0d3;TIMESTAMP;0;000000;19700101&INB-B[14]=0103ccdfce6f7d45e0d3;DEVICEID;0;&INB-B[15]=0103ccdfce6f7d45e0d3;USER;0;ABERTISA&INH-H[6]=0103cce33f5e86b3c61f;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[16]=0103cce33f5e86b3c61f;TIMESTAMP;0;000000;19700101&INB-B[17]=0103cce33f5e86b3c61f;DEVICEID;0;&INB-B[18]=0103cce33f5e86b3c61f;USER;0;ABERTISA&INH-H[7]=0103cce46b0db12ad014;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[19]=0103cce46b0db12ad014;TIMESTAMP;0;000000;19700101&INB-B[20]=0103cce46b0db12ad014;DEVICEID;0;&INB-B[21]=0103cce46b0db12ad014;USER;0;ABERTISA&INH-H[8]=0103cce58d75c6d58d46;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[22]=0103cce58d75c6d58d46;TIMESTAMP;0;000000;19700101&INB-B[23]=0103cce58d75c6d58d46;DEVICEID;0;&INB-B[24]=0103cce58d75c6d58d46;USER;0;ABERTISA&INH-H[9]=0103cce82371b7e5b68e;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[25]=0103cce82371b7e5b68e;TIMESTAMP;0;000000;19700101&INB-B[26]=0103cce82371b7e5b68e;DEVICEID;0;&INB-B[27]=0103cce82371b7e5b68e;USER;0;ABERTISA&INH-H[10]=0103ccea96fa4a3b9652;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[28]=0103ccea96fa4a3b9652;TIMESTAMP;0;000000;19700101&INB-B[29]=0103ccea96fa4a3b9652;DEVICEID;0;&INB-B[30]=0103ccea96fa4a3b9652;USER;0;ABERTISA&INH-H[11]=0103ccec012ca062e298;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[31]=0103ccec012ca062e298;TIMESTAMP;0;000000;19700101&INB-B[32]=0103ccec012ca062e298;DEVICEID;0;&INB-B[33]=0103ccec012ca062e298;USER;0;ABERTISA&INH-H[12]=0103ccf565d51f7bd8f7;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[34]=0103ccf565d51f7bd8f7;TIMESTAMP;0;000000;19700101&INB-B[35]=0103ccf565d51f7bd8f7;DEVICEID;0;&INB-B[36]=0103ccf565d51f7bd8f7;USER;0;ABERTISA&INH-H[13]=0103cdf4e3416d40815c;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[37]=0103cdf4e3416d40815c;TIMESTAMP;0;000000;19700101&INB-B[38]=0103cdf4e3416d40815c;DEVICEID;0;&INB-B[39]=0103cdf4e3416d40815c;USER;0;ABERTISA&INH-H[14]=0103d16e551570169713;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[40]=0103d16e551570169713;TIMESTAMP;0;000000;19700101&INB-B[41]=0103d16e551570169713;DEVICEID;0;&INB-B[42]=0103d16e551570169713;USER;0;ABERTISA&INH-H[15]=0103d192e748e435f81c;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[43]=0103d192e748e435f81c;TIMESTAMP;0;000000;19700101&INB-B[44]=0103d192e748e435f81c;DEVICEID;0;&INB-B[45]=0103d192e748e435f81c;USER;0;ABERTISA&INH-H[16]=0103d193f55fbd794439;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[46]=0103d193f55fbd794439;TIMESTAMP;0;000000;19700101&INB-B[47]=0103d193f55fbd794439;DEVICEID;0;&INB-B[48]=0103d193f55fbd794439;USER;0;ABERTISA&INH-H[17]=0103d22044f095f427f4;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[49]=0103d22044f095f427f4;TIMESTAMP;0;000000;19700101&INB-B[50]=0103d22044f095f427f4;DEVICEID;0;&INB-B[51]=0103d22044f095f427f4;USER;0;ABERTISA&INH-H[18]=0103d22213987cabb3b4;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[52]=0103d22213987cabb3b4;TIMESTAMP;0;000000;19700101&INB-B[53]=0103d22213987cabb3b4;DEVICEID;0;&INB-B[54]=0103d22213987cabb3b4;USER;0;ABERTISA&INH-H[19]=0103d22213e6f159009f;;N;;;;;;NEW_PROTOCOL;;0;;0;;&

[20050512 18:19:38:342] D [MI/Sync ] End of content of file 'C:\Program Files\SAP Mobile Infrastructure\sync\(SHARED)\out\package.out'

[20050512 18:19:38:342] P [MI/Sync ] Do not use http proxy (system properties update)

[20050512 18:19:38:342] I [MI/Sync ] GzipDataCompression: Gzip data compression is switched off

[20050512 18:19:38:342] P [MI/Sync ] Sending outbound file to server.

[20050512 18:19:38:358] P [MI/Sync ] Outbound file was sent.

[20050512 18:19:38:389] P [MI/Sync ] Receiving inbound file from server.

[20050512 18:19:38:389] P [MI/Sync ] Inbound file was received.

[20050512 18:19:38:389] P [MI/Sync ] Synchronisation successfully connected

[20050512 18:19:38:389] D [MI/Sync ] Number of pending inbound containers before inbound processing = 0

[20050512 18:19:38:389] D [MI/Sync ] SyncInboundContainer: closing reader for inbound file / stream

[20050512 18:19:38:389] D [MI/Sync ] Dumping file 'C:\Program Files\SAP Mobile Infrastructure\sync\(SHARED)\inbound.sync'

&WAF_SYNC&EXCEPTION_INFO_CODE=7&

[20050512 18:19:38:389] D [MI/Sync ] End of content of file 'C:\Program Files\SAP Mobile Infrastructure\sync\(SHARED)\inbound.sync'

[20050512 18:19:38:389] P [MI/Core ] original context restored

[20050512 18:19:38:389] D [MI/Sync ] Synchronisation: Fire SyncEvent 1

[20050512 18:19:38:389] P [MI/Core ] Thread Thread-28 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)

[20050512 18:19:38:389] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.sync.LogSender

[20050512 18:19:38:389] P [MI/Core ] original context restored

[20050512 18:19:38:389] P [MI/Core ] Thread Thread-28 switched context to MI4142455254495341 / MI4142455254495341 (User: ABERTISA, MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)

[20050512 18:19:38:389] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.apps.jsp.SyncStatus

[20050512 18:19:38:389] P [MI/Core ] original context restored

[20050512 18:19:38:389] P [MI/Core ] Thread Thread-28 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)

[20050512 18:19:38:389] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.ccms.LastSuccessfulSyncAlert

[20050512 18:19:38:389] P [MI/Core ] original context restored

[20050512 18:19:38:389] P [MI/Core ] Thread Thread-28 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)

[20050512 18:19:38:389] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.services.os.AgentManager

[20050512 18:19:38:389] P [MI/Core ] original context restored

[20050512 18:19:38:389] P [MI/Core ] Thread Thread-28 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)

[20050512 18:19:38:389] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.core.StatusUpdater

[20050512 18:19:38:389] P [MI/Core ] original context restored

[20050512 18:19:38:389] P [MI/Core ] Thread Thread-28 switched context to MI4142455254495341 / MI4142455254495341 (User: ABERTISA, MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)

[20050512 18:19:38:389] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.smartsync.core.SmartSyncRuntimeManager

[20050512 18:19:38:389] D [MI/Smartsync ] User has not been installed on MW, it is not ready for sync :ABERTISA

[20050512 18:19:38:389] P [MI/Core ] original context restored

[20050512 18:19:38:389] P [MI/Core ] Thread Thread-28 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)

[20050512 18:19:38:389] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.ccms.AlertManager

[20050512 18:19:38:389] P [MI/Core ] original context restored

[20050512 18:19:38:389] I [MI/Sync ] Synchronization finished, Thread=Thread-28

[20050512 18:19:48:326] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'

[20050512 18:19:48:326] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called

[20050512 18:19:48:326] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''

[20050512 18:19:48:326] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/home/synclog.jsp'

[20050512 18:21:04:484] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'

[20050512 18:21:04:484] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called

[20050512 18:21:04:484] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''

[20050512 18:21:04:484] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp'

[20050512 18:21:05:531] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'

[20050512 18:21:05:531] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called

[20050512 18:21:05:531] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''

[20050512 18:21:05:531] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/trace/trace.jsp'

[20050512 18:21:07:031] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'

[20050512 18:21:07:031] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called

[20050512 18:21:07:031] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''

At some point is says:

User has not been installed on MW, it is not ready for sync :ABERTISA .

What is MW?

And I think that i will need to patch the instalation since I have Mobile Engine 09 but when I look in MI through the WebConsole (http://ap-ccms-d01.corp.se.sempra.com:50000/me/WebConsole/add) I do not see version 250900 for MOBILEENGINE_JSP. I only have version 250000 and 250400.

Is this a SP issue?

thanks for your help.

[Former Member]

1). Did you change the Config File with the following options OR did you re-install your MI client?

MobileEngine.Sync.Pwdencrypted=X

MobileEngine.Security.SynchronizationPasswordHandlingOption=local

MobileEngine.Sync.Passwd=false

2) If you have set the Config File as above, Is your User Id and Password same in the MI Client & MI Server.

3)Is the Server Settings in your MI Client is correct and the MI Client User Id / Password you have matches with the MI Server User Id / Password, the system that is set in your MI Client?

[Former Member]

System log does not mention anything about this.

This is my MobileEngine.config file:

#Thu May 12 08:45:00 PDT 2005

MobileEngine.Sync.Gateway=http\://ap-ccms-d01\:50000/meSync/servlet/meSync?~sysid\=DMI&

MobileEngine.Sync.Proxyused=false

MobileEngine.Deployment.UpdateJarList=X

MobileEngine.Sync.Proxyport=

MobileEngine.Sync.ConnectionTimeout=-1

Runtime=tomcat

MobileEngine.Sync.Proxyhost=

Init.UsingTomcatDirs=true

MobileEngine.Sync.Client=200

MobileEngine.Sync.Gateway.Port=50000

MobileEngine.Sync.Gateway.System=DMI

MobileEngine.Reg.AlreadyInitialized=true

MobileEngine.Sync.Gateway.Protocol=http

MobileEngine.Sync.Gateway.Host=ap-ccms-d01

MobileEngine.Sync.Pwdencrypted=X

MobileEngine.Sync.Timezone=America/Los_Angeles

MobileEngine.Sync.Passwd=Test123

MobileEngine.Sync.Language=EN

Do u think something is missing?

[Former Member]

Hi Adrian!

Pl try this.Keep your MI Sync Password same as your MI Client password and set the following values in your config file.

MobileEngine.Sync.Pwdencrypted=X

MobileEngine.Security.SynchronizationPasswordHandlingOption=local

MobileEngine.Sync.Passwd=false

Make sure you restart the MI Client after making changes in the config file.

If this doesnot help, Uninstall and Re-install your MI Client,After that create a new user with the password same as your MI Server(SYNC Password).This may not look good though, but it doesnot take much time to do this.

Once it is working you can keep the SYNC Password different from your MI Client, if you wish.

[stefan_schwing]

Hi, no, this is not problem. The message claerly states that you user could not be logged on during synchronization. Did you use the correct client in the sync settings or are you using a language on MI that your SA PSyste mdoes not have installed ? Maybe the system log tells you more why this user could not be logged on.

Cheers, Stefan

[Former Member]

I'm able to log on with this user ID using the SAP GUI.

I do not have any applications installed for SAP MI. Could this be a reason?

thanks,

.adrian

[stefan_schwing]

Hi, try loggin on with this userid and the password you use for the synchronization at the specified system using the standard SAPLogon. Also pay special attention to uppercase / lowercase passwords.

Cheers, Stefan