XI CCMSR Agent registration setup error - SALF_CSM_AGENT_REGISTER

[Former Member]

Hi,

I am going through the "How To Monitor Exchange Infrastructure 3.0" guide. I am running into problems when i am trying to register the CCMSR Agent and get the error - "RFC Error Info for SALF_CSM_AGENT_REGISTER"

If I try using the Visual administrator to register the CCMSR agent, i get the following error:

ERROR: can't register at XID. RfcRc = 3, SYSTEM_FAILURE

RFC Error Info for SALF_CSM_AGENT_REGISTER

message: An exception that could not be caught occurred.

status:

intstat:

Wed Sep 14 16:46:00 2005

INFO: dsr: dsrlib unloaded.

...closing this logfile...

If I try from the command line, I get the following error:

ERROR: System name of monitored system must be different

from all central system names.

Exiting....

**********************************************************

• Welcome to sapccmsr

*

• Usage: sapccmsr -R [-f <config file>] |-U| -stop | -stat

• [ pf=<complete path of agent profile file> ] | -V

*

*

• sapccmsr -R [-f <config file>]

• [ pf=<complete path of agent profile file> ]

• Register CCMS agent at central system and

• NT service SAPCCMSR.<nr>

*

• sapccmsr -U [ pf=<complete path of agent profile

• Stop CCMS agent and deregister NT service

*

• sapccmsr -stop [ pf=<complete path of agent profi

• Stop CCMS agent

*

• sapccmsr -status [ pf=<complete path of agent pro

• Show CCMS agent status

*

• sapccmsr -V

• Show CCMS agent version

**********************************************************

INFO: dsr: dsrlib unloaded.

EXITING with code 1

A couple of questions I have:

1. Can we run CCMS and XI on the same machine?

2. If so then why am I not able to register the CCMSR agent through either way. I have double checked all of the input parameters.

Any help is appreciated:

Jay Malla

SAP XI Consultant

Licensed To Code

[rolfc_weber · Accepted solution]

Hi,

Try look at SAP Note 860676.

Hope this helps.

Regards

Rolf C. Weber

[Former Member · Accepted solution]

Thanks Rolf. I will test it out. But that seems to be the issue. We've had another similar issue with SP12 having different SLD properties than the previous versions. In particular "adapterType" for the adapter engine had been renamed to "AdapterType". We got the patch from Dirk to fix the issue.

Thanks,

Jay

[Former Member]

Hi Rolf,

Thanks - it worked like a charm! It looks like SP12 has quite a few errors that was introduced in terms of the SLD entries and code.

Regards,

Jay