- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-31-2015 07:21 AM
Hello All,
I have a local admin account used to move update sets between instances. We have recently moved from Eureka - > Fuji in Dev and Test instances. Right now when am trying to import update sets from the DEV instance I get the following error:
Error Info:
Authentication to remote instance failed
Check saved username and password
Pop up Box Error:
Authentication to remote instance failed. Error reported was "Method failed: (https://asknowdev.service-now.com/sys_update_set.do?SOAP&displayvalue=all&redirectSupported=true)HTT... 401 Unauthorized with code: 401". Check saved username and password
This has worked always but stopped after we moved to Fuji. We have reset the password and checked user name & pass but still getting the error. Does anyone know what could be causing this?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-29-2015 04:03 AM
Servicenow have found out that actually the Company associated to the local account has been deactivated hence causing the error described. Just need to activate company associated to the account and it should work. Hope this helps anyone going through the same and asking themselves, why it does not work if I have the right credentials! haha!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-29-2015 04:03 AM
Servicenow have found out that actually the Company associated to the local account has been deactivated hence causing the error described. Just need to activate company associated to the account and it should work. Hope this helps anyone going through the same and asking themselves, why it does not work if I have the right credentials! haha!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-26-2018 06:18 AM
Hello all,
Sorry to dig old resolved questions, but i face the same issue and in my case i have two instances that aren't in the same version. Thus this issue is happening.
Take a look at the folowing Link. It says in Procedure: "Provision a parent development instance on the same software version, such as Dublin, as the target instance, such as production".
Kind regards
FIKRI BENBRAHIM Mohamed Jawad
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-06-2024 09:05 PM
check the versions and tried to test connection from instance B first.
If your testing connection from A -B instance and your getting above error. just try to test connection from B- A. if it works , then again TEST connection from A -B instance it worked for me