Skip to Content
0
Former Member
Oct 15, 2013 at 07:59 PM

IntroscopeSapAgent.profile could not be read

304 Views

Good afternoon,

I've been able to get my servers to show up in the console. We found that there were some firewall settings that were blocking communication between the montoring server and bobj servers.

Today I did a landscape check and I am getting SMDAgent not reachable on my stand alone tomcat servers. I checked the logs and found this on all tomcat servers. I looked in that directory and it is completely blank. Also, I've started/restarted all of the smd agents on these servers. From what I can see they're starting ok.

#1.5 #00505699003000010000003200000D1C0004D5C416B18098#1360938077879#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[Connector,5,main]##0#0#Warning##Java###com.sap.smd.wily.hostagent.SapAgent - isConfigured(): IntroscopeSapAgent.profile could not be read!

[EXCEPTION]

{0}#1#java.io.FileNotFoundException: D:\\usr\\sap\\DAA\\SMDA98\\SMDAgent\\applications.config\\com.sap.smd.agent.application.wilyhost\\IntroscopeSapAgent.profile (The system cannot find the file specified)

at java.io.FileInputStream.open(Native Method)

at java.io.FileInputStream.<init>(FileInputStream.java:106)

at com.sap.smd.wily.hostagent.SapAgent.isConfigured(SapAgent.java:68)

at com.sap.smd.wily.hostagent.WilyHostService.startAgent(WilyHostService.java:116)

at com.sap.smd.wily.hostagent.WilyHostService.init(WilyHostService.java:68)

at com.sap.smd.core.plugin.service.ServiceEntityHandle.entityLoad(ServiceEntityHandle.java:114)

at com.sap.smd.core.runtime.broker.application.api.entity.AbstractEntityHandle.load(AbstractEntityHandle.java:234)

at com.sap.smd.core.runtime.broker.application.core.entity.PseudoEntityHandle.load(PseudoEntityHandle.java:154)

at com.sap.smd.om.impl.broker.ObjectProxyImpl.loadInternal(ObjectProxyImpl.java:308)

at com.sap.smd.om.impl.broker.ObjectReference.loadDependencies(ObjectReference.java:305)

at com.sap.smd.om.impl.broker.ObjectProxyImpl.loadInternal(ObjectProxyImpl.java:272)

at com.sap.smd.om.impl.broker.ObjectProxyImpl.load(ObjectProxyImpl.java:146)

at com.sap.smd.core.runtime.broker.ApplicationManager.loadState(ApplicationManager.java:468)

at com.sap.smd.core.runtime.broker.ApplicationManager.reachInitializationStates(ApplicationManager.java:366)

at com.sap.smd.core.runtime.Runtime.run(Runtime.java:57)

at com.sap.smd.agent.SMDAgeletsRuntimeContext.runStarterPlugin(SMDAgeletsRuntimeContext.java:116)

at com.sap.smd.agent.SMDAgeletsRuntimeContext.startApplications(SMDAgeletsRuntimeContext.java:159)

at com.sap.smd.agent.AgentContext.startApplications(AgentContext.java:709)

at com.sap.smd.agent.SMDAgeletsRuntimeContext.offlineStart(SMDAgeletsRuntimeContext.java:500)

at com.sap.smd.agent.SMDAgeletsRuntimeContext.offlineStartAppsIfNeeded(SMDAgeletsRuntimeContext.java:359)

at com.sap.smd.agent.SMDAgeletsRuntimeContext.statusChanged(SMDAgeletsRuntimeContext.java:316)

at com.sap.smd.agent.connection.SMDConnector.triggerStatusChanged(SMDConnector.java:2162)

at com.sap.smd.agent.connection.SMDConnector.setConnectionStatus(SMDConnector.java:2086)

at com.sap.smd.agent.connection.SMDConnector$SMDConnectionTask.internalAttemptConnection(SMDConnector.java:566)

at com.sap.smd.agent.connection.SMDConnector$SMDConnectionTask.attemptConnection(SMDConnector.java:95)

at com.sap.smd.agent.connection.SMDConnector$SMDConnectionTask.run(SMDConnector.java:1039)

at java.lang.Thread.run(Thread.java:722)