ServiceNow instance ID doesn't appear to match what's configured in Exalate

General Questions
, , ,
1

Originally asked by Scott Willis on 10 December 2021 (original question)

When attempting to configure the ServiceNow side of an test integration using a PDI I am prompted to enter credentials. I attempt to use the local admin account but keep receiving an “Invalid Credentials” message. I believe this may be due to the ServiceNow Application of Exalate being configured to use the Wrong Dev instance ID.

Is there a way to update this to use the correct ID for my instance or am I wrong in my assumption?

833Ă—734 50.7 KB

2

Answer by Francis Martens (Exalate) on 10 December 2021

Hi Scott Willis

Harold responded on your request in the support portal

For other people bumping in this error.
The reason for this problem is that the original update set was pointing to one of the test nodes.
You need to make sure that the exalate url is set correctly, pointing to the node which is linked to your servicenow instance.