Flow/Integration Hub Error When Running Action for AD Spoke

[Stephen Skaggs]

Receiving an odd error when running the AD Spoke action. This worked before, I have not changed anything and it even works without error in a different instance.

The error I am receiving is:

The server is not operational.

HRESULT: [-2147016646]

Stack Trace: at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
at System.DirectoryServices.DirectoryEntry.Bind()
at System.DirectoryServices.DirectoryEntry.get_AdsObject()
at System.DirectoryServices.DirectorySearcher.FindAll(Boolean findMoreThanOne)
at System.DirectoryServices.DirectorySearcher.FindOne()
at CallSite.Target(Closure , CallSite , Object )

[Josh102]

Did you have any luck with this? I am getting the same error trying to run an AD query powershell script on the MID server

[Stephen Skaggs]

So after development of the AD spoke work in the dev instance, after moving the dev work into test. A few things occurred that may have caused the issue.

• ServiceNow release a patch update
• We clone our environments down from Prod to test which I don't believe caused it because the dev instance wasn't touched.
• The MID server and AD servers were patched the night before

However, after troubleshooting I was not able to figure it out and it just started working after some time. I don't believe it was on the ServiceNow side. I think it was on the MID server or AD server side. Maybe try rebooting the servers and verifying the connections are still valid. Also confirm the MID server still has the AD module activated. You most likely have this activated, but just in case here are the steps to getting it activated on the MID Server.

"Within the role and features wizard on the MID server, add the following:

Remote Administration Tools > AD DS and AD LDS Tools > Active Directory module for Windows Powershell"