Troubleshoot ServiceNow CMDB
The connection test does not pass
Work down this table. The first two causes account for most failures.
| Cause | How to tell | Fix |
|---|---|---|
| The instance URL is not accepted | The form rejects it before any call is made | Use https://<your-instance>.service-now.com with no path, no query string and no credentials in the URL |
| The instance is provisioned for the other OAuth grant | An OAuth method is refused although the client is active. oauth2 client credentials may report that the integration user is not configured for OAuth | Try the other OAuth method. An application registered against a named account needs oauth2 password |
| The credential is wrong or expired | The test reaches ServiceNow and is refused | Re-enter it. For OAuth, confirm the client is still active in ServiceNow |
| Credentials filled in for more than one method | Mesh rejects the configuration | Clear every field except the method you selected |
| The account cannot read the tables | The test fails, or passes while collection returns little or nothing. ServiceNow returns an empty result rather than an error for some access denials | Give the account read access to the tables listed in Choose data |
| ServiceNow is unreachable from Mesh | The test times out | Check whether your instance restricts access by IP address |
For either OAuth mode, the most common cause is a client that was deactivated or had its secret rotated in ServiceNow. Confirm the client is active before re-entering anything in Mesh.
The Authenticate step has its own Test connection, so you can prove the credential works before spending time on the rest of the sequence. The test on Review then re-checks it against everything you selected.
No data arrives after setup
| Check | What it means |
|---|---|
| Has the first collection finished? | The first run reads your whole CMDB and can take hours |
| Is the table group selected? | Anything cleared in Choose data is not read at all. Vulnerabilities, Containers and Software catalog are not selected by default |
| Can the account read that table? | Read access is per table in ServiceNow. Missing access on one table affects only that data |
Open Settings → Data source syncs to see each run, what it collected and whether it failed. See Data source synchronizations.
Some records are missing detail
Records are read once and then only when they change. A record that has not changed since Mesh first read it keeps the detail it had at that time.
If a group of records is missing a field that newer records have, contact Axiad — a one-off refresh may be needed.
Software or machines look incomplete
| Symptom | Likely reason |
|---|---|
| A machine has no manufacturer or location | Those fields are empty in ServiceNow for that record |
| Software shows no publisher or version | The software model in ServiceNow does not carry them |
| A certificate has no owner | No owner is set on the ServiceNow record |
Mesh reports what your CMDB holds. Where ServiceNow has no value, Mesh shows none rather than guessing.
A relationship will not save
A relationship can only read from a table group selected in Choose data. Two of the suggested ones — Software catalog → installed products and Software catalog → owner — read from Software catalog, which is not selected by default. Select it in Step 3, then add the relationship.
Select Check relationship setup on the Connect related step to see every problem at once rather than one at a time.
Changing the instance URL
You can change it, but a stored credential is only ever reused with the instance it was saved for, so you have to enter every credential again.
Bear in mind that everything already collected is attributed to the instance it came from. Unless you are correcting a typo, add a new connector rather than pointing this one somewhere else.
Contact Axiad
If a collection keeps failing after you have worked through this page, raise it with Axiad — through your account team or the support contact in your agreement. See Contacting Axiad.
Include:
| Include | Where to find it |
|---|---|
| The connector name | Settings → Connectors |
| The time of a failed run, in UTC | Settings → Data source syncs |
| The status and reason shown | The expanded row in Settings → Data source syncs |
| Which authentication method you used | Your connector configuration |