System Monitoring : Error message in Open Alert

[Former Member]

Dear experts,

i'm new on Solution Manager System Monitoring. I have configured a satellite system on my Solution Manager and when clicking on the button "alert overview", "open alert", when clicking on CPU 5minLoadAverage or Paging out, i have an error message:

Method start failed. Reason: Screen output without connection to user.

How could i resolve it?

All response is welcome.

Thank you very much for your help.

Best regards,

Pascal.

[Former Member]

"Screen output without connection to user" usually indicates that the calling program cannot make its output to the user due to its usertype. So try to change the usertype to Dia and retry

Nesimi

[Former Member]

Hi Pascal,

Please check the RFCs used for system monitoring.

SM_<SID>XXXX_READ,

SM_<SID>XXXX_TRUSTED.

for the system monitoring and jump/remote login to the system, These RFCs should work fine.

Please check both connection test and Authorization test for the RFCs in SM59.Both should be through and you should have valid user ID maintained with correct authorizations.

Hope this helps.

Revert if you face any issues!!!!...n GOOD LUCK!!!!

Thanks,

Jagan

[Former Member]

Hi Jagan,

those RFC Destination work fine even on Connection test and Authorization test.

The user added to those RFC destination have the right authorizations.

Any clues?

Thank you

Best regards,

Pascal.

[Former Member]

Hi Pascal,

The issue should be with credentials of the user!.Please also check the RFCs from the satellite to the solution manager. XXXXX_BACK and XXXXX_Trusted.

Please confirm the logon data maintained in RFC and it has sufficient roles.

also,SAP_S_RFCACL is associated to your user for trusted login.

Also,Are the CCMS agents installed and the state?.

Thanks,

Jagan

Edited by: jagadheeshan govindasamy on Sep 2, 2009 1:10 PM

[Former Member]

Hi,

Not sure if this problem still persist, but it is probably due to the fact that in the trusted RFC to the satelite system, the "current user" is ticked on in the log on details. Probably the "current user" is known on the sattelite system as a system or communication user.

If you change the user to a dialoge user, the problem will be resolved.

Thanks,

Menno