Remote Instance Creation Fails with 401 Unauthorized – “Invalid insert”
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Check saved username and password
Remote Instance Creation Fails with 401 Unauthorized – “Invalid insert”
Hi ServiceNow Community,
I am trying to create a Remote Instance connection from one ServiceNow instance to another ServiceNow instance.
While creating the Remote Instance, I am receiving the following error:
Error:
Authentication to remote instance failed
Method failed:
(https://dev405790.service-now.com/sys_properties.do?SOAP&displayvalue=all&redirectSupported=true)
HTTP/1.1 401 Unauthorized with code: 401
Check saved username and password
Error Message:
Invalid insertEnvironment
Source Instance: ServiceNow instance from which I am creating the Remote Instance
Target Instance: dev405790.service-now.com
Connection Type: Remote Instance
Target endpoint being accessed:
sys_properties.do?SOAP&displayvalue=all&redirectSupported=true
What I have checked
The target ServiceNow instance is accessible through the browser.
The credentials have been verified.
I can log in to the target instance using the credentials.
I re-entered the username and password while configuring the Remote Instance.
The target instance is active and accessible.
However, the Remote Instance creation still fails with:
HTTP/1.1 401 Unauthorizedfollowed by:
Invalid insertQuestion
What could be causing the 401 Unauthorized response when ServiceNow attempts to access the target instance's sys_properties.do?SOAP endpoint?
Are there any specific requirements for:
Remote Instance authentication
User roles/permissions on the target instance
SOAP/Web Service access
Basic Authentication
ACLs on sys_properties
System properties that need to be enabled
Integration user configuration
Authentication restrictions or MFA/SSO settings
Could someone please provide the correct configuration steps for creating a Remote Instance connection between two ServiceNow instances and explain what needs to be configured on the target instance?
Any guidance on troubleshooting the 401 Unauthorized and Invalid insert errors would be greatly appreciated.
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
Hello @VasagnanesG
Use OAuth
Remote Instance:
Table: sys_properties -- Create New System property "glide.oauth.inbound.client.credential.grant_type.enabled" with type as "true|false" and Value as "false".
Navigate to All > System OAuth > Inbound Integration > OAuth - Client credentials grant:
OAuth Application user as system administrator (this is where you can create a dummy user as well ensuring dummy user must have "snc_platform_rest_api_access" role.)
Select available Auth scope and hit save
Source Instance:
Navigate to All > System OAuth > Application Registry > New > Connect to an OAuth Provided (simplified) - Outbound:
Enter the Client ID and Client Secret from above Remote Instance
Default Grant Type as Client Credentials
Token URL as remote instance URL: https://remoteinstance.service-now.com/oauth_token.do
In Source Instance, Navigate to All > Outbound Rest Message > Create New as Follows and validate
Hope that helps!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Thank you so much for the detailed response and guidance!
It turns out the issue was that I hadn't assigned the admin role to the user. Once I assigned that, everything started working as expected.
Since I am actively working on expanding my ServiceNow knowledge, could you also share some introductory notes or key concepts regarding ITOM (IT Operations Management), CSM (Customer Service Management), and HR Service Delivery? Additionally, if you have any video resources or recordings regarding anything ITSM as well, I would really appreciate any insights or links you could provide.
Thanks again for all your help!
Best regards,
Vasa Gnanesh
