HTTP Post Error 500 - From a Service Link agent

[Michael Doherty]

Hi all, newbie alert here

I have setup a service in CCP using a newly created agent in Service Link calling out to CPO.

I'm getting a a 'HTTP Post Error 500' when viewing the transaction information and I am wondering where to start the troubleshooting.

Many thanks for any help?

Thanks

md

[mpavlish]

Check server logs for Request Center and Service Link, check adapter logs for obvious errors.

Check inbound/outbound XML from Service Link module.

Log SR with TAC.

It is hard to reocmmend other steps without knowing what is in the log file.

[Michael Doherty]

Thanks for the advice Maksim.

I looked through the logs and there was nothing over and above the error report in the failed tranacation message (which I will add to the end of the post.

Have have advanced a little on my troubleshooting but I have still not nailed it: -

• I think the request is hitting the CPO server as if I close CPO server down, I get a 'connection refused' error
  
• When I try to verify the above finding by changing the Host details in the Outbound Properties in the agent setting, I still get the '500' error but I guess CCP (or it host server) has cached the route?
  
• My thinking is it is hitting the CPO server then somehow not finding the process to call even though I have followed an example of a successful agent setup and I am quite confident I have done this correclty.
  
• Is there anyway of understanding if a web service request has come into CPO without finding the Process it was designed to call?
  

The 500 error code is below and it does reference 'Tidal' but I am losing the will to live trying to find my next move

com.newscale.is.core.RoutingException: Routing exception found: HTTP Post Error 500http://schemas.xmlsoap.org/soap/envelope/">s:ClientThe creator of this fault did not specify a Reason.http://schemas.datacontract.org/2004/07/Tidal.Automation.Common.Product" xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns:x="http://www.w3.org/2001/XMLSchema">Tidal.Automation.Common.Product.RhapsodyExceptionA server error has occurred. Please see the server logs for additional information.0-2146233088 caused by: HTTP Post Error 500http://schemas.xmlsoap.org/soap/envelope/">s:ClientThe creator of this fault did not specify a Reason.http://schemas.datacontract.org/2004/07/Tidal.Automation.Common.Product" xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns:x="http://www.w3.org/2001/XMLSchema">Tidal.Automation.Common.Product.RhapsodyExceptionA server error has occurred. Please see the server logs for additional information.

[david.hout]

I've run into this as well but not 100% sure of the resolution.  I would start by refreshing the web services on the CPO side and restart the server.

If it still doesn't work I'd create a super simple service on the portal without any arguments or custom transformations and see if you can get that to launch and build it back up from there.

[mpetra]

I always verify its working with SoapUI. Refreshing the webservices is a must within CPO. I find it easier just to refresh than to try and check the wsdl to verify its listed.

You can copy and paste the external servicelink message within soapui and send it. If it works, you know its the Agent configuration. Usually its either ntlm vs basic and username/pw/domain issues, or the soapaction is missing from the Request Header.

if it fails within SOAPUI, its usually just the xml format and the start/end tags need updated to match the process name.

[Gunasekaran Subramanian]

HTTP Post 500 error will occur if you do not have access to send a request to the WebService you are trying to consume. Ensure if this is a public WebService. If not, provide the appropriate credentials in the agent in Service Link module -> Outbound properties.

In some cases, though it is a public WebService, this may occur. Some settings has to be corrected from the WebService provider's end to allow you to access it.