Cisco Catalyst Integration – “Request Accepted for Execution” Instead of Successful Connection

[RoseF1235]

I am currently integrating ServiceNow with Cisco Catalyst Center using a MID Server. When I test the connection, instead of seeing a green success message (for example, Connection Established), the system returns the message:

“The request has been accepted for execution.”

Because of this, CI data from Cisco Catalyst is not being ingested or moved into ServiceNow.

I have confirmed:

• The MID Server is up and validated
• The MID Server user credentials are correct and can be used to log in successfully
• Required plugins and integration steps have been completed per the documentation

Has anyone encountered this behavior before?

• Does this message indicate an authentication, API, or execution issue on the Cisco side?
• Is there a known ServiceNow configuration (REST/SOAP, MFA, roles, or async execution behavior) that causes this response?

[MartinKlus]

Hello,

same problem, same error-message.

Many thanks

[robertomagg]

Hello,

The same for me, I'm investigating...

Thank you so much.

[robertomagg]

Hello,

Our environment is a self hosted instance, so we had to import, into Cisco Catalyst (Trusted Certificate menu) the CA certificate of the url (Servicenow) exposed by the load balancer. It's a mandatory step because the Servicenow and Cisco Catalyst can't be connected to internet.

After that I received the correct message "Connection Established"  instead“The request has been accepted for execution.” and the information from Cisco arrived into Servicenow.

Perhaps importing the certificate is also necessary for a cloud instance; you could try that and see if it solves the problem.

Have a good day!

Roberto

[RoseF1235 · Accepted solution]

check to see if theirs an update or upgrade needed to be done on your midserver. That resolved our issue