- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-27-2023 03:13 AM
Hi Experts,
We have to integrate ServiceNow SaaS(Tokyo) with Servicenow On-Prem(fuji) for incident creation.
it is an SOAP outbound call from Tokyo to Fuji, while testing I am getting error:
<soap:faultstring>0x00d30003:No policy defined</soap:faultstring>
Have anyone faced similar error, we have gateway in between, we are checking with gateway team as well, mean time if anyone have faced similar problem it would be helpful to provide some directions.
Best regards
Suyog
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-27-2023 06:12 AM
Hello Suyog,
This error message is indicating that there is no policy defined for the SOAP outbound call from Tokyo to Fuji. A policy defines the rules and conditions for accessing a web service, and it is likely that a policy has not been set up or configured properly for this particular call. In order to resolve this issue, you will need to check the configuration of the policy in ServiceNow and ensure that it is properly set up to allow for outbound calls to the Fuji instance. Additionally, you may need to check the logs and/or consult with your ServiceNow administrator to troubleshoot any other potential issues that may be causing the error.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-27-2023 06:12 AM
Hello Suyog,
This error message is indicating that there is no policy defined for the SOAP outbound call from Tokyo to Fuji. A policy defines the rules and conditions for accessing a web service, and it is likely that a policy has not been set up or configured properly for this particular call. In order to resolve this issue, you will need to check the configuration of the policy in ServiceNow and ensure that it is properly set up to allow for outbound calls to the Fuji instance. Additionally, you may need to check the logs and/or consult with your ServiceNow administrator to troubleshoot any other potential issues that may be causing the error.