You’re offline. This is a read only version of the page.
Announcements
My team is trying to create a Flow inside the MS Pro Dev environment that executes a Kusto query then based on the output raise an incident with the IcM Connector as needed.
When we use the "Create or update an IcM incdent" action, the action always returns a 500 "Internal Server Error" like this with no information on how to debug or diagnose:
The same IcM ConnectorId is used in Geneva to raise incidents with no issues.
The "Create an IcM incident" action creates an incident but it does not meet our requirement of using an IcM routing ID and inject TSG information which is mandatory in the org.
We also tried to create a minimal incident using the "Create an IcM incident" action first, followed by a "Get incident details" action to try and update the incident with the "Create or update an IcM incident" action (using the Source IncidentId to match). This also resulted in the same error 500.
The issue is the same as what happened in this post with no resolution: https://powerusers.microsoft.com/t5/Using-Connectors/Internal-error-from-ICM-connector/td-p/1054244
Any help would be appreciated!
I have worked out the solution to my specific instance of the problem.
I needed to create a new IcM connector that uses one of the IcM Connector certificates that are floating around internally. Search for "IcM Connector FAQ" on sharepoint or contact FrontDesk. An existing connector created with our own managed cert that we use for Geneva/Jarvis did not work for this.
Furthermore, I had to specific an "OccuringLocationEnvironment" along with the other required fields before IcM decides everything is all good now.
Hope others find this useful.
Share
Report
All responses (
Answers (
538
