- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-17-2024 10:57 PM - edited 06-17-2024 10:59 PM
I have a non-production environment which I want to upgrade and I'm having some issues with it.
When upgrading, the change request auto-closes with the message: “This change was not completed because a ServiceNow maintenance automation task was running on the instance during the change window.”
When cloning over to this instance: "Target instance is not valid or not operational."
When restoring a backup: "Closing this change as incomplete, the restore has encountered an error. Please contact the ServiceNow Technical Support team for further details."
So I'm not sure what is going on, but I've raised a Now Support case to get some more information around this. The instance is fully operational and the stats page shows the same.
Has anybody else experienced this before and/or know any solutions?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-17-2024 11:02 PM
It is weird that you were able to schedule an upgrade during an existing maintenance change. Normally that is blocked. I am also not sure on why you first upgrade and then clone. Shouldn't that be the other way around?
When did you get the 'valid' message? While requesting a clone, or when it ran? If the instance was under maintenance, you can't clone over it. Check your clone settings to see if the connection is correct.
Regarding the backup, that could be anything, but ServiceNow is the only party that can tell you that. Since you aren't sharing a timeline (I assume this did not all happen within an hour), the best thing is to await the answer from ServiceNow.
Then, if everything is in order, clone over your non production instance to be sure nothing 'bad' is left from this failing upgrade/clone and perform the upgrade.
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
06-17-2024 11:01 PM
Hi @HP8
Only solution is to wait from Now Support , as it look like on SN side few actions has been planned which causing the issue.
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
06-17-2024 11:02 PM
It is weird that you were able to schedule an upgrade during an existing maintenance change. Normally that is blocked. I am also not sure on why you first upgrade and then clone. Shouldn't that be the other way around?
When did you get the 'valid' message? While requesting a clone, or when it ran? If the instance was under maintenance, you can't clone over it. Check your clone settings to see if the connection is correct.
Regarding the backup, that could be anything, but ServiceNow is the only party that can tell you that. Since you aren't sharing a timeline (I assume this did not all happen within an hour), the best thing is to await the answer from ServiceNow.
Then, if everything is in order, clone over your non production instance to be sure nothing 'bad' is left from this failing upgrade/clone and perform the upgrade.
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
06-17-2024 11:08 PM
Hi Mark. I'm wanting to clone first and then do the upgrade, not the other way around. I got the not valid message when i tried to re-clone the instance the second time around. The instance was not under any maintenance and there weren't any active change requests which overlap.
Timeline of events:
14th June - Clone Production over non-production instance
18th June - Scheduled upgrade to Washington DC failed
18th June - Tried to re-clone to see if it would resolve the issue, but this failed as too
18th June - Tried to restore this instance from a backup, which also failed
