Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Running multiple SAP WM 6.2 applications on SMP3.0 PL5 gives bad key error

Hi

I have SMP 3.0 , SP Level - 05

I have installed below application in the SAP Management Cockpit

SAP Work Manager 6.2 with SubURL - SAPWM_PM

SAP Work Manager 6.2 with CS with SubURL - SAPWM_CS

Starting the server does not give any errors.

In the events.log, i get the following errors

01/19/2015 05:20:19, 1,         3,         9, Thr       3520, HTTPXML-2, Chickaming HTTPXML, xmlAllowXSLTScript, File: , ..\agentry\SystemLogger.cpp#794:DTLoggerHandler::badKey

01/19/2015 05:20:19, 1,         3,         9, Thr       3520, HTTPXML-2, Chickaming HTTPXML, xmlResolveExternals, File: , ..\agentry\SystemLogger.cpp#794:DTLoggerHandler::badKey

01/19/2015 05:20:19, 1,         3,         9, Thr       3520, HTTPXML-2, Chickaming HTTPXML, xmlValidateOnParse, File: , ..\agentry\SystemLogger.cpp#794:DTLoggerHandler::badKey

01/19/2015 05:20:26, 0,        24,         4, Thr       3520, Loaded HTTP-XML Back End (HTTPXML v7.8.0.11) from ag3httpxmlbe.dll

01/19/2015 05:20:26, 1,         3,         9, Thr       3520, Java-1, Chickaming Java, initialHeapSize, File: , ..\agentry\SystemLogger.cpp#794:DTLoggerHandler::badKey

01/19/2015 05:20:26, 1,         3,         9, Thr       3520, Java-1, Chickaming Java, maxHeapSize, File: , ..\agentry\SystemLogger.cpp#794:DTLoggerHandler::badKey

01/19/2015 05:20:26, 1,         3,         9, Thr       3520, Java-1, Chickaming Java, nonStandardJavaOptions, File: , ..\agentry\SystemLogger.cpp#794:DTLoggerHandler::badKey

01/19/2015 05:20:26, 1,         3,         9, Thr       3520, Java-1, Chickaming Java, reduceOSSignalUse, File: , ..\agentry\SystemLogger.cpp#794:DTLoggerHandler::badKey

01/19/2015 05:20:34, 0,        23,         4, Thr       3520, Loaded Java Back End (Java v7.8.0.11) from ag3javabe.dll

01/19/2015 05:20:34, 0,        20,       153, Thr       3520, Finished loading Production application definitions for default localization

01/19/2015 05:20:51, 1,         2,        48, Thr       4212, EADDRINUSE, Attempt to listen on an address in use, ..\Socket\win32\sockets.cpp#1438:ListeningStreamSocket::OSListeningSocket::listenOn

01/19/2015 05:20:51, 1,         2,        48, Thr       4212, EADDRINUSE, Attempt to listen on an address in use, ..\Socket\win32\sockets.cpp#1438:ListeningStreamSocket::OSListeningSocket::listenOn

01/19/2015 05:20:51, 1,         2,        48, Thr       4212, EADDRINUSE, Attempt to listen on an address in use, ..\Socket\win32\sockets.cpp#1438:ListeningStreamSocket::OSListeningSocket::listenOn

01/19/2015 05:20:51, 1,         2,        48, Thr       4212, EADDRINUSE, Attempt to listen on an address in use, ..\Socket\win32\sockets.cpp#1438:ListeningStreamSocket::OSListeningSocket::listenOn

01/19/2015 05:20:51, 1,         2,        48, Thr       4212, EADDRINUSE, Attempt to listen on an address in use, ..\Socket\win32\sockets.cpp#1438:ListeningStreamSocket::OSListeningSocket::listenOn

Could you please help me how to resolve this issue

Regards,

Ragavie

Tags:
replied

Ragavie,

First, you can ignore the DTLoggerHandler::badKey errors.  Those are indicating you have entries in your Agentry.ini that have been depreciated and should be removed.  It is not harming anything having them there other than generating the messages on startup.

The second error indicates you are trying to use the same port number for both applications and it is complaining that it is already in use.  I suspect you didn't change the HTTPXML-2 backend listenOn port for the two WM applications.  By default it listens on 8282.  You will need to change one of them to listen on a different port.

That should fix the error.

--Bill

0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question