The Instanceld isn't enable.Please contact corresponding coordinator to enable it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2025 05:46 PM
Hi Team,
Getting this error:- The Instanceld isn't enable.Please contact corresponding coordinator to enable it. in Dev and Uat servicenow while using existing integration.
Thanks,
Saikrishna
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2025 10:53 PM - edited 02-18-2025 10:56 PM
Hi @thaduri sai
It seems like you're performing an integration, but your instance might be incorrect or not matching. You can log a case with Now Support to have this checked.
Check like this
@Mark Manders any thoughts.
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2025 10:54 PM
Hello @thaduri sai
Ensure that the instance_id field in the sys_properties table is correctly set. Search for instance_id in this table and compare value by typing "stats.do" in application menu. If different then do update.
Ensure that the integration settings are correctly configured in both Dev and UAT environments. Sometimes, discrepancies in configuration can lead to such issues.
If no success, raise a HI Support ticket for same.
If my response has helped you hit helpful button and if your concern is solved do mark my response as correct.
Thanks & Regards
Viraj Hudlikar.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2025 10:56 PM
And what did the other side tell you? The error tells you that it can't find the system you are integrating with (assuming you have this error in ServiceNow and not in your other system. Is it still up? Unfortunately, more often than not, other parties often let their dev/test instances only up for a while. Or don't tell you that they are in maintenance.
If they are up and should be available, you need to check on the settings. Is it trying to find them using the wrong parameters? Did you clone? Are accounts reset?
There is a lot of information missing here to pinpoint to the exact cause.
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2025 02:26 AM
- If you're using an existing integration (e.g., ServiceNow-Jira, ServiceNow-SAP, etc.), the Instance ID needs to be registered and enabled in the integration settings.
- Check the integration configuration and verify if the Instance ID is correctly registered and enabled.