SAP Work Manager status STOPPED in SCC

[Former Member]

Hi All,

We have installed and deployed SAP Work Manager 6.0 on SMP 2.3. In the SCC it shows the app was registered or started successfully, however the Agentry instance server status is STOPPED. The Task Manager shows the Agentry Server is running, and can actually accessed from ATE.

The problem is we can't see anything in any of the other tabs. The tab Configurations is blank and we are not able to see or maintain any settings and/or parameters. The other tabs are also blank, for example Logs is not pulling in the data from the log files. See screenshots below.

The startup.log is also noit giving me any indications or errors. See also below.

Any suggestions as to what might be wrong? And how this can be resolved?

Kind regards,
Edwin

STARTUP.LOG

09:16:47 03/27/2014: Starting server (64-bit Windows)

09:16:48 03/27/2014: Administration client command port is 60880, status port is 60881

09:16:48 03/27/2014: Looking for initial status connection...

09:16:58 03/27/2014: Event: 0, 2, Status connection not detected.  Continuing startup

09:16:58 03/27/2014: Reading system ini file.

09:16:58 03/27/2014: ID: SAP Work Manager Server v6.0.0.0, Name: ???, Location: ???

09:16:58 03/27/2014: Starting log file.

09:16:58 03/27/2014: Loading message groups.

09:16:58 03/27/2014: Starting threads.

09:16:58 03/27/2014:    1 initial threads.  Threads will auto-scale.

09:16:58 03/27/2014: Starting Server: Agentry v6.1.3.10212

09:16:58 03/27/2014: Event: 0, 2, System Startup

09:16:58 03/27/2014: Loading 1 front ends

09:16:58 03/27/2014: Loading front end from angelvine.dll

09:16:58 03/27/2014: ANGEL Front End: reading init files.

09:16:58 03/27/2014: Event: 17, 14, ANGEL Front End v6.1.3.10212

09:16:58 03/27/2014: Event: 0, 2, Loading the Agentry Server's public/private key for password exchanges.

09:16:58 03/27/2014: Event: 0, 2, Key pair loaded successfully.

09:16:58 03/27/2014: Starting Server Agent.

09:16:58 03/27/2014: Agentry: Starting threads.

09:16:58 03/27/2014:    1 initial threads.  Threads will auto-scale.

09:16:58 03/27/2014: Agentry: Adding messages.

09:16:58 03/27/2014: Event: 1, 4, Agentry v6.1.3.10212

09:16:58 03/27/2014: Loading 1 agents

09:16:58 03/27/2014: Loading agent from ag3.dll

09:16:59 03/27/2014: Starting Server

09:16:59 03/27/2014: Server: reading ini file

09:17:00 03/27/2014: Initializing 2-HTTPXML from ag3httpxmlbe.dll

09:17:00 03/27/2014: SystemConnection-2: Reading configuration information.

09:17:00 03/27/2014: SystemConnection-2: Setting name to 'HTTP-XML Back End'.

09:17:00 03/27/2014: HTTP-XML Back End: Initialized.

09:17:00 03/27/2014: Event: 24, 4, Loaded HTTP-XML Back End (HTTPXML v6.1.3.10212) from ag3httpxmlbe.dll

09:17:00 03/27/2014: Initializing 1-Java from ag3javabe.dll

09:17:00 03/27/2014: SystemConnection-1: Reading configuration information.

09:17:00 03/27/2014: SystemConnection-1: Setting name to 'Java Back End'.

09:17:00 03/27/2014: Java Back End: Initialized.

09:17:02 03/27/2014: Java Back End: Java Virtual Machine loaded.

09:17:07 03/27/2014: Java Back End: Java Back End AJAPI version 5.0, release 6.1.3.10200

09:17:07 03/27/2014: Event: 23, 101, Java Back End: AJAPI JAR version 6.1.3.10200 does not match the version of the Agentry Server

09:17:07 03/27/2014: Java Back End: Initialized.

09:17:07 03/27/2014: Event: 23, 4, Loaded Java Back End (Java v6.1.3.10212 (JVM version 1.6.0_35, AJAPI version 5.0 build 6.1.3.10200)) from ag3javabe.dll

09:17:07 03/27/2014: Event: 20, 150, Loading Production application definitions using file "SAPWM-v1-0-0-app"

09:17:07 03/27/2014: Event: 20, 152, Loading Production application definitions for default localization

09:17:18 03/27/2014: Event: 20, 153, Finished loading Production application definitions for default localization

09:17:18 03/27/2014: Event: 20, 151, Finished loading Production application definitions using file "SAPWM-v1-0-0-app"

09:17:18 03/27/2014: HTTP-XML Back End Back End: Started

09:17:18 03/27/2014: Server: Starting threads.

09:17:18 03/27/2014:    1 initial threads.  Threads will auto-scale.

09:17:19 03/27/2014: Event: 20, 4, Server v6.1.3.10212

09:17:19 03/27/2014: Starting front ends

09:17:19 03/27/2014: ANGEL Front End: Starting threads.

09:17:19 03/27/2014:    3 initial threads.  Threads will auto-scale.

09:17:19 03/27/2014: ANGEL Front End: opening listen socket on port 7003

09:17:19 03/27/2014: Event: 17, 10, 0.0.0.0:7003 open

09:17:19 03/27/2014: Event: 17, 10, ANGEL Front End v6.1.3.10212

09:17:19 03/27/2014: Event: 0, 0, Old log files moved into E:\SAP\MobilePlatform\Servers\UnwiredServer\logs\com.sap.wm\Rolled\2014-03-27-091647

09:17:19 03/27/2014: Event: 0, 23, SAP Mobile Platform

09:17:19 03/27/2014: Event: 0, 2, Server startup is complete.

09:17:19 03/27/2014: Agentry Application startup complete

[Former Member · Accepted solution]

Is the Server's Region and language set to anything other then US English?

If so you might be running into a known issue that is resolved in SP04.

Stephen Streeter

[Former Member · Accepted solution]

Hi Stephen,

Under Region and Language the Format is set to English US and the Location is US, this is on both the Agentry Server as well as the Agentry Development Server where we access the SCC from.

The language toolbar was showing English (South Africa), changed that to English (US) as well, after rebooting the Agentry Server the node is no longer showing in SCC.

Any suggestions why this is no longer showing?

We are considering upgrading to SP04, but would like to get this fixed before going down that road.

Regards.
Edwin

[Former Member · Accepted solution]

There is a fix for the Agentry Server node not showing up in SP04

Stephen

[Former Member · Accepted solution]

SP04 is now release please download and retest.

Stephen

[Former Member · Accepted solution]

Hi Stephen,

We installed SP04, but we are still experiencing the same issue. We even went as far as deleting and re-deploying the app.

Again it shows the app registered successfully:

On the General tab it still shows status STOPPED:

The other tabs don't show anything, e.g. Configurations or Logs:

After restarting SMP the node completely disappears:

The Region & Language settings on the SMP server:

Any further suggestions are much appreciated.

Regards,
Edwin

[Former Member · Accepted solution]

So we decided to log a message with SAP. They have requested various log files of SCC and SMP. Awaiting their feedback, will update with their response.

[Former Member · Accepted solution]

Hi Edwin,

We are also facing same issue. is sap replied with resolution? If so kindly share us the solution.

Thank you.

[Former Member · Accepted solution]

Dear Edwin,

I found the work around, please follow the steps:

1. Launch the SCC and open the configuration tab just below the Localhost in the Tree.

2. open the SSl configuration

3. click on the key store button and import the self signed certificate(pfx and server-cer.cer).

4. Restart the server and your node appears in SCC.

Please mark as answered if this solves your issues.

[Former Member · Accepted solution]

Hi Rakeshkumar,

The workaround you provided solved the issue.

Thanks!

Edwin