Troubleshooting ServiceNow Add-On Integration Error

Troubleshooting ServiceNow Add-On Integration Error

Problem: The following error pops up while trying to add a ServiceNow instance:


Solution:
Ensure that the ServiceNow instance is accessible from the AppManager server and the user account has itil, itil_admin and personalize_choices roles assigned.




                  New to ADSelfService Plus?

                    • Related Articles

                    • Real User Monitor (RUM) - Troubleshooting

                      If the monitor has not polled data for a long time, follow the steps below for troubleshooting: Step 1: Check prerequisites to be done Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer the help ...
                    • Service Now Event Integration using Webhook / Rest API Action

                      Steps to perform in Service Now 1) Login to your ServiceNow Instance(dev*****133.service-now.com) 2) Search for the Rest API Explorer and open it 3) In the Rest API Explorer page choose the Namespace and API Name with the proper API version. For ...
                    • Troubleshooting Server error responses

                      Server error responses Internal Server Error, Bad Gateway, Service Unavailable and Gateway Timeout are the most common server error messages. Seeing any one among these errors generally indicates an issue with the URL's server. Troubleshooting for ...
                    • Troubleshooting WinRM errors

                      This KB serves as a guide for troubleshooting errors when using the WinRM mode of data collection. First, ensure that all the following conditions are met: Refer to the below link and check if all the WinRM prerequisites have been completed properly ...
                    • New tickets are not logged in ServiceNow integration

                      Problem: New tickets are not logged in ServiceNow integration, even when new alerts are being created for the reported  monitor (Issue persists in Applications Manager builds lower than 14670) Solution: Ensure that Log a Ticket action is configured ...