Instance not managed by the upgrade server (https://nodeupgrade.service-now.com/). No war file retri
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
For Self-hosted how do we configure the correct setting so this does not keeping popping up in upgrade logs.
I have already set 5 items that support recommended for self-hosted and this log entry remains.
In an addition to this "instance registration: unsuccessful: trying again in 5 minutes"
message.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
Hi @jeffreyluto
For the error : Do following steps.
1. Go to the scheduled Item "Register Instance"
https://<instance address>/nav_to.do?uri=sys_trigger.do?sys_id=7a1a3d630a0a0b6100be7e4f070e6cc3
2. Update Trigger Type = "On Demand".
3. Click "Update"
Note : 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
Refer this old (old but still helpful) community post:
Instance registration unsuccessful
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I found the script include but scheduled job in Sys_trigger.
I made the script inactive in Dev for now.
