'Access denied. Script returned status 3 using account local MID server service credential.' in Flow

[Admin7267]

I have used Create AD Object action in the flow designer for creating admin user in AD. This issue we are only facing on the TEST instance, on the DEV instance the workflow works as expected after the Zurich upgrade as well. Last week we upgraded our Test instance to Zurich after that this issue is coming up.

Credentials were updated in Midserver and in sys_user table for the mid user, still facing same issue.

If anyone has an idea related to the ‘Access denied. Script returned status 3 using account local MID server service credential.’ error please let me know. Any guidance or tips would be greatly appreciated! Thank you!!

[Bhuvan]

@Admin7267 

Follow below knowledge article to resolve the issue

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0811747

If this helped to answer your query, please mark it helpful & accept the solution.

Thanks,

Bhuvan

[kaushal_snow]

@Admin7267 ,

When you see the error Access denied. Script returned status 3 using account local MID server service credential. in a flow using the Active Directory Spoke or Active Directory orchestration activity, it means the MID Server attempted to execute a PowerShell (or remote AD) action but failed because the credential it used was invalid or lacked sufficient permissions, and according to the documentation the code 3 indicates that the MID server service account was used but could not carry out the action.....

To fix it, go into System Credentials → Credentials, ensure the credential record the flow uses has Applies to = All MID Servers (or includes your specific MID server) and not a mis configured specific MID selection, and make sure the underlying Windows/AD account the credential maps to has the necessary rights to create or manage users/groups in AD.

Also double check the MID server logs and credential test under MID Server → Credentials to ensure you don’t see authentication errors, and remember that an upgrade (like Zürich) sometimes resets or restricts credential/mid server permission settings so compare with your DEV instance where it still works.....

If you found my response helpful, please mark it as ‘Accept as Solution’ and ‘Helpful’. This helps other community members find the right answer more easily and supports the community.