Skip to main content
Solved

Assyst ETM/ipaas 500 internal server error

  • April 8, 2024
  • 1 reply
  • 70 views

Forum|alt.badge.img+9

Has anyone using ETM/IPAAS run into an unknown error with creating events or in any integration use case really where the error cause is shown as follows?

Looking to see if others are experiencing this issue or if it’s truly unique to an integration we had with a servicenow vendor and our assyst instance via AGS.


All that displays as the cause in the failure log of etm is this:

500 - <html><head><title>Error</title></head><body>Internal Server Error</body></html>

Best answer by Arnaud Le Tollec

Dear customer.

500 internal server error indicates that the server encountered an unexpected condition that prevented it from fulfilling the request.

However the error you mentioned is not precise enough to confirm the exact cause of the issue at this point. I would therefore advise you to log an incident with the IFS service desk.

I have noticed that you may have already done so, if this is the case please feel free to close this community question.

Kind regards. 

 

View original
Did this topic help you find an answer to your question?

Arnaud Le Tollec
Do Gooder (Employee)
Forum|alt.badge.img+4

Dear customer.

500 internal server error indicates that the server encountered an unexpected condition that prevented it from fulfilling the request.

However the error you mentioned is not precise enough to confirm the exact cause of the issue at this point. I would therefore advise you to log an incident with the IFS service desk.

I have noticed that you may have already done so, if this is the case please feel free to close this community question.

Kind regards. 

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings