SAPHostagent (SAPCCMSR) non-SAP Systems

[Former Member]

Hello,

I have the following problem with the new SAPHOSTAGENTS 7.20 (SAPCCMSR via web service) for non-SAP systems (host).

The agents start over again (about every hour). The status in RZ21(CEN) is then commit failed or shutdown.

If the agents run, I have access to everything (agents directory, etc.)

The other Agents (SAPCCM4X) works fine.

In the ST11 following error messages for the NON-SAP Server exist:

XRFC> SY_SID     : SOM

XRFC> SY_MANDT   : 000

XRFC> SYS_NR     : 77

XRFC> APPLSERVER : sapxxx_SOM_77

XRFC> ISPRESCHED : X

XRFC> DURATION   : 17

XRFC> NETHDRTIME : 17

XRFC> CALL_STATE : 2

XRFC> ERRORTYPE  : SYSFAIL

XRFC> ERRORAREA  : COREMSG

XRFC> CTXDP_TYPE : SOAP_RUNTIME

XRFC> SYNC_ASYNC : S

XRFC> LOCATION   : C

XRFC> DIRECTION  : O

XRFC> REQ_ID     : E2xxxxxxxxxxE36005056AE021E

XRFC> RESP_ID    : 00000000000000000000000000000000

XRFC> MSG_STATE  : 117

XRFC> IF_NAME_I  : CO_WSSAPCCMS

XRFC> IF_NS_E    : urn:SAPCCMS

XRFC> IF_NAME_E  : SAPCCMS

XRFC> ISSHORTCUT :

XRFC> TRC_PATT   : WSTEST

XRFC> TRC_SSID   : SOM_77

XRFC> TRC_USER   : SAPSYS

XRFC> TRC_TS     : 20130417134900

XRFC> TRC_COUNT  : 63

XRFC> TRC_EXT    :

XRFC> COMPLETE   : OK

XRFC> CALLEDPROG : CO_WSSAPCCMS

XRFC> SOAP_APPLI :

XRFC> CONF_ID    : E295428ED81xxxxxxxxxxGFDE8JS2

XRFC> BIND_ID    : E295xxxxxxxxxxxxEHG2U

XRFC> OP_NAME    : MtCustomizeWrite

XRFC> COMM_PATRN : Method:MtCustomizeWrite

XRFC> OP_NS      : urn:SAPCCMS

XRFC> REMADDRESS :

XRFC> LP_NAME    : SAPCCMSR.SAPOTxxx.99

XRFC> DT_OBJ     : CO_WSSAPCCMS

XRFC> MEMCONSUMP : 60

XRFC> WSHOST     : SAPOTxxx

XRFC> WSPORT     : 1128

XRFC> WSPROT     : http

XRFC> WSCLIENT   :

XRFC> WSPATH     : /SAPCCMS.CGI

XRFC> PXYHOST    :

XRFC> PXYPORT    :

XRFC> USEDRFCDES : E2954295B2E3FHT6AE36005056AE021E

XRFC> BONAME     :

XRFC> PROCCOMP   :

XRFC> DEPLOYUNIT :

XRFC>

XRFC>

XRFC> TRACE SOAP RUNTIME - trace records

XRFC>

XRFC>

XRFC> E CONTEXT 20130417134901.9180000 : CL_SOAP_CONTEXT ->SET_FAULT

XRFC> SOAP Runtime Fehlerbehandlung beim SOAP Fault

XRFC>

XRFC>

XRFC> E SOAP_RUNTIME 20130417134901.9180000 : CL_SOAP_RUNTIME_CLIENT

XRFC> ->EXEC_PROCESSING Ausnahmebehandlung innerhalb der SOAP Laufzeit

XRFC>

XRFC>

XRFC> E HTTP_TRANSPORT_BINDING 20130417134901.9180000 : CL_SOAP_HTTP

XRFC> _TPBND_ROOT ->HANDLE_STATUS_CODE Received return code 401 (

XRFC> Unauthorized )

XRFC>

XRFC>

XRFC> E CONTEXT 20130417134901.9180000 : CL_SOAP_CONTEXT ->SET_FAULT set

XRFC> fault loop detected

XRFC>

XRFC>

XRFC> E SOAP_RUNTIME 20130417134901.9180000 : CL_SOAP_RUNTIME_CLIENT

XRFC> ->EXEC_PROCESSING SOAP Fault Exception caught: : HTTP Error:

XRFC> 'Unauthorized'

XRFC>

Thanks

Holger

[Former Member]

Hello,

Accordoing to the SOAP message:

XRFC> E SOAP_RUNTIME 20130417134901.9180000 : CL_SOAP_RUNTIME_CLIENT

XRFC> ->EXEC_PROCESSING SOAP Fault Exception caught: : HTTP Error:

XRFC> 'Unauthorized'

I would like to sugges the SAP note:

# 1569955 - gSOAP Web Service pop-up while configuring CCMS agent

When the SAPSTARTSRV SAPCCMSR agent is not correctly started the registration can never be done correctly.

Can you please check if the user CSMREG in client 000 in the <SID> system is not blocked and if the password which is used during the registration is still valid

Monitoring Hosts with SAPHostControl and saphostexec:

http://help.sap.com/saphelp_nwpi71/helpdata/EN/44/86b14bcc8812d2e10000000a422035/frameset.htm

Installing/Registering the CCMS Agents for Experts

http://help.sap.com/saphelp_nw70/helpdata/en/8b/f64352e1bfbd4eb43e432860504a1c/frameset.htm

BR

Tamas

[Former Member]

Hi Holger,

Did you disable the ccms function of the host agent regarding to Note 1491115 - OS monitors ST06n, OS07n do not display data in CEN system ?

Laszlo

[Former Member]

Hi Laszlo,

I think this Note is not relevant.

I had installed on an NON-SAP Windows 2008 R2 Server, the saphostagent 7.20 package and register with the Transaction RZ21 in CEN. Without errors. It works fine, but always the Agent go in status "offline" for a few minutes(see in TA RZ20).

Thanks Laszlo for your help.

[isaias_freitas]

Hello Holger,

Can you post the contents of the logs at the SAP Host Agent folder? I believe that they would have the information regarding the actual cause of the problem.

Regards,

Isaías

[Former Member]

Hello Isaias,

sapstartsrv-log:

---------------------------------------------------
trc file: "sapstartsrv.log", trc level: 1, release: "720"
---------------------------------------------------
pid        2292

[Thr 4016] Mon Mar 25 15:04:50 2013
[Thr 4016] MtxInit: -2 0 0
[Thr 4016] *** ERROR => DlLoadLib()==DLENOACCESS - LoadLibrary("sapNThalib.dll")
  Error 126 = "The specified module could not be found." [dlnt.c       255]
DlLoadLib('sapNThalib.dll') failed: -2 => HA support disabled
CCMS agent initialization for instance type HOST: return code 0.
[Thr 4016] CCMS: Initialized monitoring segment of size 40000000.
[Thr 4016] CCMS: Initialized CCMS Headers in the shared monitoring segment.
[Thr 4016] CCMS: Checking Downtime Configuration of Monitoring Segment.
[Thr 4016] CCMS: AlMsUpload called by wp 1998.
[Thr 4016] CCMS: AlMsUpload successful for C:\Program Files\SAP\hostctrl\work\ALMTTREE.DAT (148 MTEs).
CCMS agent start: return code 0.
Initializing SAPHostControl Webservice
[Thr 4016] =================================================
[Thr 4016] = SSL Initialization    platform tag=(NTAMD64)
[Thr 4016] =   (720_REL,Mar  3 2013,mt,ascii,SAP_UC/size_t/void* = 8/64/64)
[Thr 4016] =   found SAPCRYPTOLIB  5.5.5C pl34  (Mar  1 2012) MT,AESNI,NB
[Thr 4016] =   current UserID: Dxxx\sapxxx
[Thr 4016] *** ERROR => sapcr_set_secudir("C:\Program Files\SAP\hostctrl\exe\sec") failed !! [ssslsecu.c   1375]
[Thr 4016] =   SECUDIR location determined through "<Default>" --
[Thr 4016] =   using SECUDIR=C:\sec
[Thr 4016] *** ERROR =>   secudessl_Create_SSL_CTX():  PSE "C:\Program Files\SAP\hostctrl\exe\sec\SAPSSLS.pse": File not found! [ssslsecu.c   1848]
[Thr 4016] secudessl_Create_SSL_CTX: SSL_CTX_set_default_pse_by_name() failed --
[Thr 4016]   secude_error 4129 (0x00001021) = "The PSE does not exist"
[Thr 4016] >> ---------- Begin of Secude-SSL Errorstack ---------- >>
[Thr 4016] ERROR in SSL_CTX_set_default_pse_by_name: (4129/0x1021) The PSE does not exist : "C:\Program Files\SAP\hostctrl\exe\sec\SAPSSLS.pse"[Thr 4016] ERROR in ssl_set_pse: (4129/0x1021) The PSE does not exist : "C:\Program Files\SAP\hostctrl\exe\sec\SAPSSLS.pse"[Thr 4016] ERROR in af_open: (4129/0x1021) The PSE does not exist : "C:\Program Files\SAP\hostctrl\exe\sec\SAPSSLS.pse"[Thr 4016] ERROR in secsw_open: (4129/0x1021) The PSE does not exist : "C:\Program Files\SAP\hostctrl\exe\sec\SAPSSLS.pse"[Thr 4016] ERROR in secsw_open_pse_or_extension: (4129/0x1021) The PSE does not exist : "C:\Program Files\SAP\hostctrl\exe\sec\SAPSSLS.pse"[Thr 4016] ERROR in sec_get_PSEtype: (4129/0x1021) The PSE does not exist : "C:\Program Files\SAP\hostctrl\exe\sec\SAPSSLS.pse"[Thr 4016] << ---------- End of Secude-SSL Errorstack ----------
[Thr 4016] *** ERROR => SapISSLAddCredential(): Error SSSLERR_PSE_ERROR trying to create SERVER Credential
        for "C:\Program Files\SAP\hostctrl\exe\sec\SAPSSLS.pse" [ssslxxi.c    2417]
[Thr 3788] CCMS: Initialized monitoring segment of size 40000000.
[Thr 3788] CCMS: Initialized CCMS Headers in the shared monitoring segment.
[Thr 3788] CCMS: Checking Downtime Configuration of Monitoring Segment.
[Thr 3788] CCMS: AlMsUpload called by wp 1998.
[Thr 3788] CCMS: AlMsUpload successful for C:\Program Files\SAP\hostctrl\work\ALMTTREE.DAT (148 MTEs).
[Thr 4016] *** ERROR => Initialization of SSL library failed -- NO SSL available!
[Thr 4016] =================================================
[Thr 4016]
[Thr 4016] <<- ERROR: SapSSLInit(read_profile=1)==SSSLERR_PSE_ERROR
SapSSLInit failed => https support disabled
Starting WebService Named Pipe thread
Starting WebService thread
Webservice named pipe thread started, listening on port \\.\pipe\sapcontrol_99
[Thr 2396] ***LOG Q0I=> NiPGetServByName: 'saphostctrl' not found: getaddrinfo (10109: WSATYPE_NOT_FOUND: The specified class was not found.) [ninti.c 939]
Webservice thread started, listening on port 1128

sapstartsrv_ccms-log:

[Thr 4016]
Mon Mar 25 15:04:50 2013
      Initialize CCMS agent sapccmsr
INFO:
      CCMS version  20060508, 64 bit, multithreaded, Non-Unicode 7200
      compiled at   Mar  3 2013
      systemid      562 (PC with Windows NT)
      running on    SAPOTxxx Windows NT 6.1 7601 Service Pack 1 2x AMD64 Level 6 (Mod 44 Step 2)
      patch text    patch collection 2012/1, OSS note 1453112, PL 418
      profile       C:\Program Files\SAP\hostctrl\exe\host_profile

INFO: Central Monitoring System is [SOM]. (found in config file)

INFO: CCMS agent will connect to the following central CCMS systems:
INFO: **********************************************************
INFO: *********************      SOM      **********************
INFO: **********************************************************

INFO: CCMS agent initialization finished.

INFO: Starting CCMS agent threads...
INFO: Checking lock file ...
INFO: Checking lock file returned 0
INFO: Checking CCMS monitoring segment ...
INFO: Attached to a monitoring segment type HOST (2), running in shared memory.
INFO: Agent status in the attached monitoring segment is NOT_ACTIVE (10).
INFO: Checking CCMS monitoring segment finished.
INFO: Creating lock file returned 0.

INFO: Starting CCMS agent threads finished.

[Thr 3788]
INFO: Entering Main loop.
INFO:
      CCMS version  20060508, 64 bit, multithreaded, Non-Unicode
      compiled at   Mar  3 2013
      systemid      562 (PC with Windows NT)
      relno         7200
      patch text    patch collection 2012/1, OSS note 1453112, PL 418

INFO Runtime:
      running on    SAPOTxxx Windows NT 6.1 7601 Service Pack 1 2x AMD64 Level 6 (Mod 44 Step 2)
      running with profile   C:\Program Files\SAP\hostctrl\exe\host_profile

INFO profile parameters:
      alert/MONI_SEGM_SIZE = 40000000
      alert/TRACE          = 1
      SAPSYSTEM            = 99
      SAPSYSTEMNAME        = SAP
      SAPLOCALHOST         = SAPOTxxx
      DIR_CCMS             = C:\saploc\CCMS
      DIR_LOGGING          = C:\Program Files\SAP\hostctrl\exe\log
      DIR_HOME             = C:\Program Files\SAP\hostctrl\work
      DIR_PERF             = C:\saploc\PRFCLOG

INFO:
      pid           2292

INFO: Created shared memory key 1008 (size 40000000)

INFO: Connected to Monitoring Segment [CCMS Monitoring Segment for SAPOTxxx, created with version CCMS version 20060508, 64 bit multithreaded, compiled at Mar  3 2013,  kernel 7200_20020600_418,  platform 562 (PC with Windows NT)]
        segment status     WARM_UP
        segment started at Mon Mar 25 15:04:50 2013
        segment version    20060508

INFO: Setting runtime information of sapccmsr in monitoring segment.
INFO: Loading static lib rfcoslib with trace level 0.
RFCOSLIB: INFO: current trace level is 1
RFCOSLIB: INFO: Semaphore Handling initialization successful.
RFCOSLIB: searching for Process Monitoring configuration in \\SAPOTxxx\saploc\PRFCLOG\dev_proc
RFCOSLIB: searching for Process Monitoring Templates in \\SAPOTxxx\saploc\PRFCLOG\procmon\
RFCOSLIB: INFO: Trying to Register Objects
RFCOSLIB: WARNING: OS Monitoring: Can not attach Shared Memory. Saposcol not running ?
ALEVTLOGLIB: INFO: EventLog Monitoring Reading evtsave.bin
ALEVTLOGLIB: INFO: EventLog Monitoring Reading C:\Program Files\SAP\hostctrl\work\sapccmsr\sapccmsr.ini

ALEVTLOGLIB: INFO: Running with EventLogMonFactor 1 (SYSLOGBUFSIZE=10240) .
ALEVTLOGLIB: INFO: EventLog Monitoring not configured
RFCOSLIB: INFO: OS monitoring: Operating System Tree created
INFO: Loading static lib alloglib with trace level 0.

ALLOGLIB: INFO: Reading logsave.bin
ALLOGLIB: INFO: Reading C:\Program Files\SAP\hostctrl\work\sapccmsr\sapccmsr.ini
ALLOGLIB: INFO: ok, no configuration for Logfile Monitoring. No entry  LogFile <file_name>  in configuration file C:\Program Files\SAP\hostctrl\work\sapccmsr\sapccmsr.ini found
ALLOGLIB: INFO: using template directory C:\saploc\PRFCLOG\logmon for log file monitoring.

INFO: Working directory is C:\Program Files\SAP\hostctrl\work\sapccmsr
INFO: Configuration file C:\Program Files\SAP\hostctrl\work\sapccmsr\sapccmsr.ini opened.
INFO: PlugIn manager initialized successfully.

[Thr 1044]
INFO: Threads of CCMS Web Service Agent: method dispatcher SAP_CCMS_AGNT_LOCAL_TD started

[Thr 3788]
INFO: Main loop: Method dispatchers initialized.
INFO: CCMS agent is running.

[Thr 3524]
INFO: Threads of CCMS Agent: method dispatcher SAP_CCMS_AGNT_LONGRUN_TD started

[Thr 1044]
Mon Mar 25 15:05:00 2013
RFCOSLIB: INFO: Operating System Version:  Windows NT 6.1.7601 SP 1 SAPOTxxx 2x AMD64 Level 6
INFO: set ccms/cache_context_refresh = 600

INFO: [SOM:000:CSMxxx] connected to SOM, host sapsoxxx, System Nr. 70, traceflag [ ]
INFO: SOM release is 701 , (kernel release 720 ), CCMS version 20060508
INFO: Central ICT-based monitoring cache not configured in SOM on server sapsom01.
INFO: Pushing data into ICT-Cache disabled.
INFO: Switch on ICT-Cache in SOM with profile parameter alert/cache/size_MB.

Thanks!!!

Regards,

Holger

[isaias_freitas]

Hello Holger,

Thanks for sharing the traces. They don't show any error.

Are the SAP HostAgent processes still running?

Regards,

Isaías

[Former Member]

Hello,

yes, they are still running. The current Status is shutdown, but in 5 minutes the Status is online and the CCMS_Self_Monitoring says, that the Agent is restarted (aktive since ...).

The other old SAPCCMSR-Agents works fine and have a "aktive since" status with an old Timestamp(from the last shutdown of the Server).

Any Idea (the error message in ST11)?

Regards

Holger

[isaias_freitas]

Hello Holger,

Do you mean that you still have the old CCMS agents running at the same host you've installed the SAP Host Agent?

If yes, that's why the SAP Host Agent isn't working. You cannot have two CCMS agents (e.g., to sapccmsr agents) running at the same server, at the same time.

You should stop the old agents, and restart the SAP Host Agent. Once the SAP Host Agent is stable, you can then uninstall the old agents.

Regards,

Isaías

[Former Member]

Hello Isaias,

no. I mean that we have other NON-SAP Server with the old Agents, and this Agents work fine.

Only the new Server we installed with the new SAPHOSTAGENTS.

Thanks,

Holger