Skip to Content
Author's profile photo Tamas Istenes

“SAP OS monitor has probably stopped. The OS information may be incomplete or missing.”

Netweaver administrator is not getting the information about saposcol’s availability from saposcol itself, but from CCMS agents By CCMS agent I mean sapstartsrv process,which has built-in CCMS agent. CCMS agent looks to it’s own shared memory and provides them, if they are available. Asynchronously from this, CCMS agent is regulary downloading the information from saposcol’s shared memory.

All CCMS agents can copy data from the SAPOSCOL shared memory segment to the CCMS monitoring segment and transfer it to a central monitoring system.

CCMS Agents:

Advanced Functions of the CCMS agents

Working Directory and Log Files of the CCMS Agents

NWA administrator -> sapstartsrv webservice (SAPCCMSR porttype) -> sapstartsrv shared memory (getting data – task for integrated agent) on one side, and on the other side sapstartsrv (resp. integrated agent) is regulary copying data from saposcol’s shared memory to it’s own.

Please check
2213745 – SAP OS monitor has probably stopped
#1834530 – AS Java Overview shows warning for stopped SAPOSCOL WS

Only the “Operating System” data which is reported by NWA is stored in the CCMS shared memory monitor segment.

Please always be sure the SAPOSCOL is the latest version on the highest PL:

#19227- Open newest saposcol
#548699 – FAQ: OS collector SAPOSCOL

SAPOSCOL: Clearing Shared Memory and Updating Saposcol

Key words:

“SAP OS monitor has probably stopped. The OS information may be incomplete or missing.

To resolve this, start your SAPOSCOL. To learn more about starting and stopping SAPOSCOL”

Assigned Tags

      1 Comment
      You must be Logged on to comment or reply to a post.
      Author's profile photo Laszlo Badovszky
      Laszlo Badovszky

      Thank you for the information - and for the useful links too!