‘Access denied. Script returned status 3 using account user null.’ error message for AD activities
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-02-2022 11:49 PM
Hello Experts,
We have used the Orchestration Active Directory activities in the workflow for the User offboarding process. For the ‘Disable AD User Account’ activity, the workflow follows the failure path with error message ‘Access denied. Script returned status 3 using account user null.’ but also for ‘Remove User from Group’ activity the workflow follows the success path with the same error message. This issue we are only facing on the PROD instance, on the TEST instance the workflow works as expected. Previously we were not facing this issue on PROD also but from last week this issue has occurred.
If anyone has an idea related to the ‘Access denied. Script returned status 3 using account user null.’ error please let me know.
Any guidance or tips would be greatly appreciated!
Thank you!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-19-2023 10:24 AM
HI,
We are also getting same error.
Any resolution on this ?
Thanks
VASAVI
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-19-2023 11:19 AM
On the Credential we are using for Orchestration, we specify the MID Server to run from. I've seen this issue before when we didn't have "Applies to" set to a Specific MID Server.
Please mark this response as correct and/or helpful if it assisted you with your question.
Steven
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-19-2023 12:36 PM
Hi Steven,
We already have sepcific midservers configured for Orchestation credentials.
Thanks
VASAVI
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2023 11:47 PM
The Mid server used invalid credentials while execution of those activities, we have selected valid credentials and in that credentials "applies to" as specific mid servers and then added mid server in mid server field. After these changes issue was resolved.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-11-2024 05:04 PM
I've been having this problem for about a year, now. Has _anybody_ resolved this? 🙏🏻