SMDAgents reports file /usr/sap/DAA/SMDA97/exe/saposcol does not exist

[neeta_patel2]

Hi all,

After starting the SMD agent, the log file reports the following:

pg SMDAgentApplication.0.log

<!LOGHEADER[START]/>

<!HELP[Manual modification of the header may cause parsing problem!]/>

<!LOGGINGVERSION[1.5.3.7185 - 630]/>

<!NAME[SMDAgentAppLog]/>

<!PATTERN[SMDAgentApplication.log]/>

<!FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%t] %10s %m)]/>

<!ENCODING[ASCII]/>

<!FILESET[0, 10, 1000000]/>

<!PREVIOUSFILE[SMDAgentApplication.9.log]/>

<!NEXTFILE[SMDAgentApplication.1.log]/>

<!LOGHEADER[END]/>

Jul 15, 2010 2:59:45 PM [Thread[Thread-6,5,main]] Warning com.sap.smd.wily.hostagent.destination.ProcessDestination - commandExists: file /usr/sap/DAA/SMDA97/exe/saposcol does not exist, destination Process_Saposcol not available

Jul 15, 2010 2:59:45 PM [Thread[Thread-6,5,main]] Warning com.sap.smd.wily.hostagent.destination.ProcessDestination - open(): file saposcol does not exist, destination not available

The SAP Hostagent is installed and this starts the saposcol process. The managed system configuration has been odne successfully in this managed system. This managed system is a Jva stack runing the SAP Portal. Any ideas why we are seeing the above error in the SMDAgentApplication.0.log file?

There are SMD Agents installed on other systems in our landscape and we are seeing this problem in one system.

Regards, Neeta

[guilherme_balbinot]

Dear Neeta,

Please check the SAP Host Agent.

Check its status

saphostexec -status

Check its version

saphostexec -version

I can see that, in your particular case, there was an issue in the host profile (I found your OSS message).

The installation is covered by SAP Note 1031096: Installing Package SAPHOSTAGENT

This is the general recommendation to contribute to the SDN content.

Best regads,

Guilherme Balbinot