cancel
Showing results for 
Search instead for 
Did you mean: 

SyncBo Processing Statistics can not start plug-in

Former Member
0 Kudos

Hi Everybody,

We are facing the below issues on MAM3.0 (Middleware)-Netweaver2004s-.

Please provide some solutions to resolve this issue.

1)SyncBo Processing Statistics can not start plug-in

2)Error message displays :-SLD is not accessible .using ABAP port 8004 & 50400

3)Connection to Server failed Server logon failed; internal error. when synchronized between Mobile Infrastructure client and MAM.

*Task Performed:-*

1 file is created according http://help.sap.com/saphelp_nw04/helpdata/en/92/0d603d13b5c72ee10000000a114084/content.htm

2 Usergroup MESYNC "User Group for Synchronization" is created in solution manager and assigned to users via CUA.

3 Table BWAFMAPP has identical entries in the RFC back-end system to table BWAFMAPP of the server.

4 ABAP program MEREP_DISTRIBUTOR has been executed on CGM 100.

5 LcrAdministrator action is assigned to role SAP_JAVA_NWMOBILE_ADMIN_SUPER and SLD activated on http://demosap6:8004/sld, but still identical message.

6 Perfomred this link help http://help.sap.com/saphelp_nw04s/helpdata/en/44/2813dae11b73cae10000000a114a6b/frameset.htm

7 SICF is correctly configured and test provides positive result.

8 all syncbo's are deployed

9 MobileEngine.config analyzed and manually tested.

_Synchronization Log:-_

• Synchronization started

• Connection set up (without proxy) to: http://demosap6:8004/sap/bc/MJC/mi_host?~sysid=CGM&;

• Connection to server failed.

• Problems during synchronization: Server logon failed; internal error. Contact your system administrator.

Trace

[20080213 15:38:36:642] I [MI/API/Logging ] ***** LOG / TRACE SWITCHED ON

[20080213 15:38:36:642] I [MI/API/Logging ] ***** Mobile Infrastructure version: MI 70 SP 12 Patch 2 Build 200708221757

[20080213 15:38:36:642] I [MI/API/Logging ] ***** Current timezone: Europe/Berlin[20080213 15:38:36:642] I [MI/API/Logging ] ***** Current Trace Level: 1000

[20080213 15:38:36:652] I [MI ] Trace severity: All (1000)

[20080213 15:38:36:652] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/trace/trace.jsp'

[20080213 15:38:42:450] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'

[20080213 15:38:42:450] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called

[20080213 15:38:42:450] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''

[20080213 15:38:42:460] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp'

[20080213 15:38:44:473] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'

[20080213 15:38:44:473] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called

[20080213 15:38:44:473] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''

[20080213 15:38:44:473] P [MI/Sync ] Notify R3 called

[20080213 15:38:44:473] D [MI/Sync ] There is already a container for method WAF_REGISTRY and user J2EE_ADMIN in the outbound queue

[20080213 15:38:44:473] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp'

[20080213 15:38:44:493] I [MI/Sync ] Synchronize with backend called, Thread=Thread-29

[20080213 15:38:44:493] I [MI/Sync ] Thread=Thread-29 took lock for synchronization.

[20080213 15:38:44:493] P [MI/Sync ] Use following gateway for synchronization: http://demosap6:8004

[20080213 15:38:44:503] E [MI/Sync ] Received response code 2 from ABAP Sync Service and the corresponding localized message is Server logon failed; internal error. Contact your system administrator.

[20080213 15:38:44:503] W [MI/Sync ] Cannot connect to gateway

com.sap.ip.me.api.sync.SyncException: Server logon failed; internal error. Contact your system administrator.

at com.sap.ip.me.core.ABAPSyncServiceLogonCheck.connectToMIService(ABAPSyncServiceLogonCheck.java:139)

at com.sap.ip.me.core.ABAPSyncServiceLogonCheck.connectToMIService(ABAPSyncServiceLogonCheck.java:75)

at com.sap.ip.me.sync.SyncManagerImpl.doConnectionTest(SyncManagerImpl.java:636)

at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:422)

at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:318)

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

at com.sap.ip.me.apps.jsp.Home$SyncRunnable.run(Home.java:641)

at java.lang.Thread.run(Unknown Source)

[20080213 15:38:44:503] I [MI/Sync ] Synchronization finished, Thread=Thread-29

[20080213 15:38:54:547] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'

[20080213 15:38:54:547] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called

[20080213 15:38:54:557] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''

[20080213 15:38:54:557] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/home/synclog.jsp'

[20080213 15:39:32:362] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'

[20080213 15:39:32:362] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called

[20080213 15:39:32:362] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''

[20080213 15:39:32:362] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp'

[20080213 15:39:35:236] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'

[20080213 15:39:35:236] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called

[20080213 15:39:35:246] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''

[20080213 15:39:35:246] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/trace/trace.jsp'

[20080213 15:39:37:790] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'

[20080213 15:39:37:790] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called

[20080213 15:39:37:790] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''

Please update me ...

Thanks in Advance

Amol Ambalkar

Edited by: Amol Ambalkar on Feb 14, 2008 1:37 PM

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

please try the other screens in NWA as well - I would expect that you run into similar problems there as well.

I think you have a problem with the used user. My experience was, that using a user with MISERVICE role, it was not working due to missing authorisations. So I started using the MIADMIN role instead for users connecting to SLD, using JCO and that stuff. After I changed all system users for MI to this MIADMIN role, it was working fine.

Hope this helps in your case as well.

Regards,

Oliver

Former Member
0 Kudos

Hi Oliver,

Thanks for your update.

I have tried to assigned a SAP_MI_ADMIN role to the login user but in vain.still the same error is displaying.

Kindly update me any other solution.

Thanks & Regards,

Amol Ambalkar

Former Member
0 Kudos

Hi,

if I see your Port - is 8004 really the Port to the ICM? Look into SICF and the services - does it tell 8004 or 8000 or 8080?

The 4 at the end confuses me a little, caus ethis was always the port for the admin UIs.

????

Regards,

Oliver

Former Member
0 Kudos

Hi Oliver,

Yes..It's port 8004.

Please update me.

Regards,

Amol

Former Member
0 Kudos

Hi Amol,

sorry, I missed a line in your trace file...... :-$

20080213 15:38:44:503 E MI/Sync Received response code 2 from ABAP Sync Service and the corresponding localized message is Server logon failed; internal error. Contact your system administrator.

It seems that either your user has not the correct credentials/password or so - or the service user you used as you did the setup of the SyncService has these problems. Can you check that? Use the MI_ADMIN_ user instead of the MI_SERVICE user for that - this will cure most issues.

Regards,

Oliver