500 Internal server error when running SOLMAN_SETUP

[Former Member]

Hi experts,

I'm configuring our solution manager with the SOLMAN_SETUP transaction. In the "initial Configuration", step "j2ee configuration", I click the "Start SLD configuration" button and appears an Internet explorer. After loggin with an administrator user/password, the following error appears:

500 Internal Server Error

SAP NetWeaver Application Server 7.00/Java AS 7.00

Failed to process request. Please contact your system administrator.

[Hide]

Error Summary

While processing the current request, an exception occured which could not be handled by the application or the framework.

If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).

Root Cause

The initial exception that caused the request to fail, was:

java.lang.NullPointerException

at com.sap.tc.lm.ctc.ccl.wd.TemplateInstallerCompController.getSelectedForSkipActions(TemplateInstallerCompController.java:741)

at com.sap.tc.lm.ctc.ccl.wd.ScenarioTemplateViewController.actionReexecuteSelectedTemplate(ScenarioTemplateViewController.java:141)

at com.sap.tc.lm.ctc.ccl.wd.ScenarioTemplateViewController.init(ScenarioTemplateViewController.java:115)

at com.sap.tc.lm.ctc.ccl.templateinstaller.ScenarioTemplateView.wdDoInit(ScenarioTemplateView.java:106)

at com.sap.tc.lm.ctc.ccl.templateinstaller.wdp.InternalScenarioTemplateView.wdDoInit(InternalScenarioTemplateView.java:475)

... 37 more

See full exception chain for details.

......

Our solution mananger release is 7.0 EHP1.

Do you have any idea of what the problem is, please?

Thanks and best regards,

Ana

[Former Member]

Hello,

Sorry for the delay but i resolved the problem last week and I didn't see your question.

I have made an update of the java stack and after that the error 500 disappeared.

I hope it helps.

Thanks to all. Regards,

Ana.

[Former Member]

Hi Ana,

Please let me know what you did to resolve this issue. I am facing the same issue when i run solman_setup.

Thanks & Regards,

Vaishali.K

[Former Member]

Hello Jagan,

I think the java stack is running, i can check the sld from http:://<host>:port/sld and in the tab adminitration the status is running.

do you think it could be related with the SAP client? The solution manager system was first half configured in client 001. then there was a client copy and someone configured it in the new client (100). Now, i'm trying to forget all and begin again in client 200. I have change the client in the java stack configtool.bat. However, I'm not sure if I'm forgetting something.

Your workaround is a good idea, but I'm so unexperienced that the guided solman_setup transaction seemed a good help.

Thanks and best regards,

Ana.

[Former Member]

Hi,

The E:\usr\sap\SOL\DVEBMGS00\j2ee\cluster\dispatcher\log\defaultTrace.0.trc last entries are:

#1.5 #000C298948DC001C0000000200000FA80004765AE7A68A56#1256032712398#com.sap.engine.core.configuration##com.sap.engine.core.configuration#######SAPEngine_System_Thread[impl:6]_27##0#0#Error#1#/System/Server#Plain###Exception in ConfigurationChangedListener:

null

=======================================================

java.lang.NullPointerException

+ at com.sap.engine.services.monitor.common.MonitorConfigurationHandler.configurationChanged(MonitorConfigurationHandler.java:1105)+

+ at com.sap.engine.core.configuration.impl.event.PathEventProcessor.sendEvents(PathEventProcessor.java:138)+

+ at com.sap.engine.core.configuration.impl.event.EventProcessor.processEventListeners(EventProcessor.java:121)+

+ at com.sap.engine.core.configuration.impl.event.QueuedEventProcessor.run(QueuedEventProcessor.java:48)+

+ at com.sap.engine.frame.core.thread.Task.run(Task.java:64)+

+ at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:80)+

+ at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:150)+

#

#1.5 #000C298948DC001F0000001D00000FA80004765B772CB455#1256035120366#com.sap.engine.core.thread.impl6.ThreadManagerImpl##com.sap.engine.core.thread.impl6.ThreadManagerImpl#######Thread[Thread-30,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_System_Thread[impl:6]_ThreadManager:

Thread[SAPEngine_System_Thread[impl:6]_37]

Task: com.sap.engine.core.thread.impl6.ActionObject - Processing Task [classname: com.sap.engine.services.log_configurator.archive.ArchivingThread | toString: com.sap.engine.services.log_configurator.archive.ArchivingThread@7a6dd8e1] with classloader [com.sap.engine.core.service630.container.ComponentClassLoader@6e82254d@service:log_configurator]#

#1.5 #000C298948DC001F0000001D000003680004765BBE6F6136#1256036315718#com.sap.engine.core.thread.impl6.ThreadManagerImpl##com.sap.engine.core.thread.impl6.ThreadManagerImpl#######Thread[Thread-1738,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_System_Thread[impl:6]_ThreadManager:

Thread[SAPEngine_System_Thread[impl:6]_12]

Task: com.sap.engine.core.thread.impl6.ActionObject - Processing Task [classname: com.sap.engine.services.log_configurator.archive.ArchivingThread | toString: com.sap.engine.services.log_configurator.archive.ArchivingThread@3f6a5bcb] with classloader [com.sap.engine.core.service630.container.ComponentClassLoader@2390d8e1@service:log_configurator]#

And the E:\usr\sap\SOL\DVEBMGS00\j2ee\cluster\server0\log\defaultTrace.8.trc entries related to the error message are:

#1.5 #000C298948DC00540000033C00000F1400047684AAF47374#1256212082608#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tc_wddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#SISTEMAS#104##crosol203_SOL_2722150#SISTEMAS#bf43cb51bf0011de8147000c298948dc#SAPEngine_Application_Thread[impl:3]_35##0#0#Error#1#/System/Server/WebRequests#Plain###application [webdynpro/dispatcher] Processing HTTP request to servlet [dispatcher] finished with error.

The error is: java.lang.NullPointerException: null

Exception id: [000C298948DC00540000033A00000F1400047684AAF47077]#

Thanks and best regards,

Ana Abad

[Former Member]

Hi Ana,

Looks like your java stack has some issues or some applications are not working.

Is your Java Stack up and running?. Check the SLD application on your java stack. http:://<host>:port/sld.

As a workaround,You can configure your SLD from the administration tab of SLD application.

Hope this helps.

Revert for any issues.

Thanks,

Jagan

[Former Member]

Hello,

Where are that dafault trace files?

Thanks and best regards,

Ana.

[sunny_pahuja2]

Hi,

Check default trace file /usr/sap/<SID>/<instance>/j2ee/cluster/<dispatcher/server0>/log ?

Check these log files against exception id that you get in 500 internal server error..

Thanks

Sunny

[sunny_pahuja2]

Hi,

Could you please check default trace log files ?

Thanks

Sunny