Flow designer AD spoke throwing intermittent error

[Faizan9]

Hi All,

I'm using Active directory spoke of the flow designer to connect to AD and have been getting this error intermittently:

The specified module 'activedirectory' was not loaded because no valid module file was found in any module directory. HRESULT: [-2147024894]

This happens no matter which mid server I select. Right now i've set it to 'All' for mid servers and the error happens on all of them.

I tried to put this in a while loop to make it work since there's no retry mechanism I see on the Flow designer and it would generally work in a couple of tries but using a while loop isn't a workable solution for me since I can't setup a retry count using any variables on Flow designer.

I've tried few work arounds for this but to no avail.

Anyone have experience with this issue.

would greatly appreciate any help.

[Peter de Bock1 · Accepted solution]

hi Faizan,

I had exactly the same issue last week. We have resolved it by granting/checking the appropriate feature in AD.

See my post for the details : https://community.servicenow.com/community?id=community_article&sys_id=b7079117db1d1c10190dfb2439961...

Please mark it helpfull in case it does 🙂

regards, Peter

[Ct111]

There can be some error at the other  end as well.

Check the below link 

https://stackoverflow.com/questions/19182497/import-module-the-specified-module-activedirectory-was-...

Mark my ANSWER as CORRECT and HELPFUL if it helps

[Peter de Bock1 · Accepted solution]

hi Faizan,

I had exactly the same issue last week. We have resolved it by granting/checking the appropriate feature in AD.

See my post for the details : https://community.servicenow.com/community?id=community_article&sys_id=b7079117db1d1c10190dfb2439961...

Please mark it helpfull in case it does 🙂

regards, Peter

[Faizan9 · Accepted solution]

Late in responding to this, we're able to rule out which mid servers were failing and throwing this error and the configuration that was not enabled on those mid servers that were throwing error.

As Peter above has also mentioned, we enabled the 'Active Directory' module on each mid server to get this to work and it's been running smoothly since.