locked
500 Error while calling web service RRS feed

  • Question

  • BizTalk Version-BizTalk Server 2013R2
    Issue related to IIS
    The user is getting (500) Internal Server Error while calling the web service hosted in IIS. We tried recycling the app pools and IIS and related host instances. But still they are getting 500 Errors. What could be the root cause?
    Wednesday, May 31, 2017 6:31 AM

Answers

  • We created a dedicated app pool and that fixed issue.

    The application was using an app pool which was shared by various other applications and hence whenever there was a heavy inflow of messages we were getting 500 errors. Thank you for the suggestions!

    Wednesday, June 7, 2017 1:18 AM

All replies

  • Can you check for more details on the issue in IIS log files, event logs ??

    Pi_xel_xar

    Blog: My Blog

    BizTalkApplicationDeploymentTool: BizTalk Application Deployment Tool/

    Wednesday, May 31, 2017 6:48 AM
    Answerer
  • The application pool hosting the web service does not have the appropriate permissions as a result t may be starting up but at the first request fails and gves the 500 error. Check the Security Event Log to see if there are logon failures associated with the application pool account.

    If however this is a BizTalk Orchestration/Schema hosted as a service then the pool account should be the same service account under which the receive adapter is running and the a/c should be a member of the IUSR_IIS and BizTalk Isolated Host user group.

    Regards.

    Wednesday, May 31, 2017 7:26 AM
  • 500 Internal Server Error is a generic error message for something not working on the server-side.  It could be anything.

    Things you can do to troubleshoot:

    • Try to see if you can access the endpoint from a browser to verify that the Receive Location has the correct values in it.
    • Check the Windows Application Event Log for more detailed errors
    • Enable returning the error detail in the WCF Receive Location configuration

    These should help you narrow down what the exact cause of the error is.  If you still have issues resolving it, post the error information here.


    If this is helpful or answers your question - please mark accordingly.
    Because I get points for it which gives my life purpose (also, it helps other people find answers quickly)

    Wednesday, May 31, 2017 8:07 AM
  • We created a dedicated app pool and that fixed issue.

    The application was using an app pool which was shared by various other applications and hence whenever there was a heavy inflow of messages we were getting 500 errors. Thank you for the suggestions!

    Wednesday, June 7, 2017 1:18 AM