Instance registration unsuccessful

[FinToy]

Hi, we're running an on-premise instance and there's no connection to internet. In the system logs I can see repeating log entry (Information type) with text: "Instance registration: unsuccessful: trying again in 5 minutes"

Is this something we should disable when running the instance on-premises?

[Chuck Tomasi]

If you DO decide to disable the script include... it could lead to other errors such as scripts that are the calling the script include. Also make a BIG documented note somewhere that you did this. Some time in the future, you will find yourself scratching your end wondering why your instance isn't registering and forget ALL about this checkbox you unchecked.

[FinToy]

Thank you gentlemen. Perhaps it's better to raise a HI ticket about this. I'll let you know how it all ended.

[FinToy]

Quite funny, the ServiceNow official response sounds somehow familiar...

2018-02-21 22:44:18 PST - Vab Singhal (NOW)

Solution proposed by Vab Singhal (NOW)

There is a script include called RegisterInstanceClient which attempts to register the instance from
https://<instance>.service-now.com/sys_script_include.do?sys_id=94c8d2d6c0a8006f00027d4fc446bf30

if you don't have an internet connection you should be able to disable this script include. That should stop the error.


Regards,
Vab Singhal
ServiceNow Technical Support Team

2018-02-21 22:46:52 PST - Vab Singhal (NOW)

On a side note, please make sure to test properly before disabling the script include.
Because it could lead to other errors such as scripts that are the calling the script include.
Also, make a BIG documented note somewhere that you did this.

Sometime in the future, you will find yourself scratching your end wondering why your instance isn't registering and forget ALL about this checkbox you unchecked.

Regards,
Vab Singhal
ServiceNow Technical Support Team

[FinToy]

Anyway, the Script include you mentioned is now disabled. Let's see if we face any problems with this. Thank you once again.

[FinToy]

...and the problems started right away. Now we get error messages:

Those seem to be caused by this:

Trying to disable the scheduled job next.