The Instanceld isn't enable.Please contact corresponding coordinator to enable it.

thaduri sai
Tera Contributor

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

4 REPLIES 4

Dr Atul G- LNG
Tera Patron
Tera Patron

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

AGLearnNGrow_0-1739948153725.pngAGLearnNGrow_1-1739948211941.png

 

@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]

****************************************************************************************************************

Viraj Hudlikar
Giga Sage

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 Manders
Mega Patron

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

sravya chipilla
Tera Contributor

 

  • 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.
  •