Recently (actually since we use our new cluster environment) we receive the this message from time to time after changing some settings with the console:
It finally turns out that restart of the EntSSO service solves the problem although teh eventlog messages lead into another direction (reinstall etc.).
Random pitfalls (and their solutions) in EAI technologies such as BizTalk
Thursday, October 21, 2010
Friday, June 18, 2010
Guest post: Misleading error message with SAP WCF custom adapter
In an IDOC receive scenario using the WCF custom adapter with SAP binding we received the following error messages:
The adapter "WCF-Custom" raised an error message. Details "Microsoft.Adapters.SAP.RFCException: Details: ErrorCode=RFC_EXCEPTION. ErrorGroup=RFC_ERROR_APPLICATION_EXCEPTION. SapErrorMessage=OBJECT_UNKNOWN. AdapterErrorMessage=Error returned by RfcCallReceiveEx while calling RFC: IDOCTYPE_READ_COMPLETE..
The solution is quite simple as it resides in the SAP setting for the RFC connection, transaction SM59. Switching the communication type to Unicode solved the problem.
(This post is brougth to you by Franziska Kirschner, our great new team member)
The adapter "WCF-Custom" raised an error message. Details "Microsoft.Adapters.SAP.RFCException: Details: ErrorCode=RFC_EXCEPTION. ErrorGroup=RFC_ERROR_APPLICATION_EXCEPTION. SapErrorMessage=OBJECT_UNKNOWN. AdapterErrorMessage=Error returned by RfcCallReceiveEx while calling RFC: IDOCTYPE_READ_COMPLETE..
The solution is quite simple as it resides in the SAP setting for the RFC connection, transaction SM59. Switching the communication type to Unicode solved the problem.
(This post is brougth to you by Franziska Kirschner, our great new team member)
Subscribe to:
Posts (Atom)