cancel
Showing results for 
Search instead for 
Did you mean: 

problem in "Diagnostic configuration" in Solution Manager 7 ehp1

Former Member
0 Kudos

Hi All

I try to execute "Diagnostic configuration" step in my solution manager 7.0 ehp1.

I have executed all the basic configuration in my SM.

I executed transaction solman_setup -> select step "Automatic

Configuration" -> "Diagnostic configuration" and appear this error

message:

Service cannot be reached

What has happened?

URL

http://<hostname>:8000/webdynpro/dispatcher/sap.com/tcsmdnavigation/StandaloneApp call was terminated because the corresponding

service is not available.

Must I activate any service from transaction sicf? if yes, which service must I activate?

Thanks in advance for collaboration.

best regards

giovanni

Accepted Solutions (0)

Answers (5)

Answers (5)

Former Member
0 Kudos

ok

Former Member
0 Kudos

Have you run through Initial and Basic configuration in solman_setup?

This should set the required SICF services for you. Otherwise there is an IMG step to do it as well.

Edited by: Craig Farrington on Aug 12, 2009 4:22 PM

Former Member
0 Kudos

Hi

I have resolved the problem using port 5<sn>00 instead 80<sn> but it's only a workaround.

giovanni

Former Member
0 Kudos

Hi : I am getting this problem now which I get around by changing 80xx to 5xx00. did u figure a permant way out? if so , i would be ever so greatful if you can share it with us.

thanks

viji

Former Member
0 Kudos

Hi!

We are facing the same problem.

http://xxxxxxxxxxxxx::8000/webdynpro/dispatcher/sap.com/tcsmdnavigation/StandaloneApp?APP_ID=ADMIN_INTROSCOPE_AGENT

500 Internal Server Error

SAP NetWeaver Application Server 7.00/Java AS 7.00

Failed to process request. Please contact your system administrator.

Did you find any solution to the issue? The note 1276263 is not availible.

/Anton Renberg

Former Member
0 Kudos

make sure you apply #1244225 & #1172948 before using SOLMAN_SETUP

Former Member
0 Kudos

I think the cause of your problem is authorization issue.

Therefore please check the note #1276263 and the attached documentation.