on 04-25-2014 12:54 PM
Hello,
Several years we developed a Web Service from Sap to Sharepoint. The issue is that we often get an "Error at Target of Invocation" intermittently. The first thing we do of course is to make sure the SAP connection password has not expired. Also, whenever mapping is changed we use the Web Service to create a new WSDL file that is compatible. Importantly, we assume that the connection from a Sharepoint is being made, because to run one of the processes from Sharepoint, while connecting to SAP, there is no problem. However, when we run a different process that uses the same Sharepoint to SAP connection, we get the error at target of invocation message.
The .NET developer will sometimes recycle the Sharepoint process that clears the cache, and for now, we think, that may be the issue. Still we are not positive, and this message does not reveal the real issue. Is there a way to connect the Web Service to XI to capture any issues in between the two systems that would uncover what the real issue is?
Thanks, Tom M.
Hi Tom,
AFAIK We can raise alerts in PI system , if any messages fail for the interface (PI to .Net Webservice). But if any connection issue occurred , Receiver server will be having more information/log traces why exactly connection occurred. I will recommend to get the trace from receiver system (Server on which Webservice was hosted) and analyze the trace and find the root cause.
Thanks
Hari.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.