SMD - RFC_ERROR_LOGON_FAILURE

[Former Member]

This is a CRM 2007 system and I am getting the below errror when i run the managed system setup for the wily step.

Step Wilyhost Agent Details

Created destination P31_DVEBMGS31_server0

Created destination SapStartSrv_sappc003_P31_31

Created destination P31_D31_server0

Created destination P31|sappc003_P31_31

Created action SAP GC|P31_DVEBMGS31_server0 - SAP GC|P31_DVEBMGS31_server0

Created action P31|sappc003_P31_31 - SapStartSrv_sappc003_P31_31

Created action SAP GC|P31_D31_server0 - SAP GC|P31_D31_server0

Created action P31 - P31 AbapSystem

Created action P31|sappc003_P31_31 - P31|sappc003_P31_31 AbapInstance

Created action P31|CRM - P31 CRMSystem

Created 6 action(s).

1 Wilyhost Agent(s)

from host sappc003 are connected to the EM.

90 seconds after restarting the WilyHostAgent the data of the following action is still missing in EM: P31|CRM - P31 CRMSystem

Please check SMDAgentApplication log files for warnings and errors.

Wilyhost Agent setup finished successfully with limitations. Data of at least one action is not available in Enterprise Manager(agp200.amgreetings.com:6001).

When I checked the smdagent logs I see:

Sep 15, 2009 1:04:05 PM [Thread[SapStartSrv_sappc004_P31_31,5,main]] Error com.sap.smd.wily.hostagent.sapcontrol.SapControlAction - doRun:

[EXCEPTION]

javax.xml.rpc.soap.SOAPFaultException: DpExtProcAttach failed

at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.buildFaultException(MimeHttpBinding.java:737)

at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.processDocumentFault(MimeHttpBinding.java:860)

at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1440)

at com.sap.smd.agent.wsclients.sapstartsrv.SAPControlStub.ABAPGetWPTable(SAPControlStub.java:2135)

at com.sap.smd.agent.wsclients.sapstartsrv.SAPControlStub.ABAPGetWPTable(SAPControlStub.java:2150)

at com.sap.smd.wily.hostagent.sapcontrol.SapControlAction.getABAPWPTable(SapControlAction.java:329)

at com.sap.smd.wily.hostagent.sapcontrol.SapControlAction.doRun(SapControlAction.java:850)

at com.sap.smd.wily.hostagent.action.AbstractAction.run(AbstractAction.java:53)

at com.wily.EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:728)

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

What is this error ?

Pls advise.

thank you

Edited by: Laxminarayan Sriram on Sep 15, 2009 7:17 PM

[Former Member · Accepted solution]

In my scenario; we deleted the managed system client (200) where the SMDAgent was initally pushed out. I re-ran the wizard with the new ABAP system client and restarted.

However I will see this error in the SMDAgentApplication log where it's still looking to connect w/ 200. So not sure where to change the client # manaully. I thought re-push of the SMDAgent should take care of it....

Also seeing the dev_jrfc.trc with below entries being repeated every 5 minutes.

Can anyone guide me in terms of where I can manually change the target client from 200 to 300?

SMDAgentApplication.1.log

Feb 3, 2010 11:24:42 AM [Thread[Reconnect,5,main]] Error com.sap.smd.wily.hostagent.action.ReconnectAction - doRun(): Failed to reconnect destination PE1|swape1ci_PE1_00

[EXCEPTION]

com.sap.smd.wily.hostagent.TransientException: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Client 200 is not available in this system

at com.sap.smd.wily.hostagent.destination.JCODestination.init(JCODestination.java:78)

at com.sap.smd.wily.hostagent.destination.JCODestination.open(JCODestination.java:45)

at com.sap.smd.wily.hostagent.action.ReconnectAction.doRun(ReconnectAction.java:35)

at com.sap.smd.wily.hostagent.action.AbstractAction.run(AbstractAction.java:53)

at com.wily.EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:728)

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

Caused by: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Client 200 is not available in this system

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:516)

at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1086)

at com.sap.mw.jco.JCO$Client.connect(JCO.java:3256)

at com.sap.mw.jco.JCO$Pool.initPool(JCO.java:4726)

at com.sap.mw.jco.JCO$PoolManager.getClient(JCO.java:6181)

at com.sap.mw.jco.JCO$PoolManager.getClient(JCO.java:6136)

at com.sap.mw.jco.JCO.getClient(JCO.java:8804)

at com.sap.mw.jco.JCO$Repository.getRepositoryClient(JCO.java:20463)

at com.sap.mw.jco.JCO$Repository.queryFunctionInterface(JCO.java:20543)

at com.sap.mw.jco.JCO$Repository.getFunctionInterface(JCO.java:20651)

at com.sap.mw.jco.JCO$BasicRepository.getFunctionTemplate(JCO.java:19689)

at com.sap.smd.wily.hostagent.destination.JCODestination.init(JCODestination.java:55)

dev_jrfc.trc

<RfcGetException

Error> occured >Wed Jan 27 09:32:30,173< >RfcGetException rc (7) message: Name or password is incorrect (repeat logon)

<RfcGetException

Error> occured >Wed Jan 27 09:37:30,173< >RfcGetException rc (7) message: Name or password is incorrect (repeat logon)

<RfcGetException

Error> occured >Wed Jan 27 09:42:30,183< >RfcGetException rc (7) message: Name or password is incorrect (repeat logon)

<RfcGetException

Error> occured >Wed Jan 27 09:47:30,193< >RfcGetException rc (7) message: Name or password is incorrect (repeat logon)

<RfcGetException

Error> occured >Wed Jan 27 09:52:30,204< >RfcGetException rc (7) message: Name or password is incorrect (repeat logon)

<RfcGetException

Error> occured >Wed Jan 27 09:57:30,223< >RfcGetException rc (7) message: Name or password is incorrect (repeat logon)

<RfcGetException

Error> occured >Wed Jan 27 10:02:30,233< >RfcGetException rc (7) message: Name or password is incorrect (repeat logon)

<RfcGetException

[Former Member]

One possible solution is that the invalid clients are specified in the JCO RFC Provider
<host>:<port>/nwa
[Configuration] (Not Destinations)
Infrastructure
  JCO RFC Provider

Clients, including the invalid ones causing messages in dev_jrfc.trc may be able to be found in the Repository Configuration above - removing them /changing them to be correct should remove the error message.

[neil_hoff]

I am running into the same issue. What did you do to fix it?

Thank you,

Neil

[Former Member]

We got the same error.

have you found a solution ??

[Former Member]

Hello

Here exact the same problem. We want to connect a PI 7.11-system.

Someone a solution?

Regards

Simon