Getting an error "Access denied. Script returned status 3 using account user null".

[Seema Thakre]

Hello,

           I have a requirement related to   'Account Setup: User was a Conversion and ended with two active entries in SN User Table'. The requirement is "User is a conversion, and the existing AD account DID get updated, but the ServiceNow User did not get updated, and the AD sync added a NEW user record, so we have dup with same email address". but when I try to replicate the issue, I am getting this error 'Access denied. Script returned status 3 using account user null.' 

If anyone has an idea related to the ‘Access denied. Script returned status 3 using account user null.’ error please let me know.

Thank You!

[Brian Workman]

Have you resolve this? I am getting the same thing.

[Daisy3]

Were you able to resolve this?

I am getting the error: Access denied. Script returned status 3 using account local MID server service credential.

[Markus Kraus]

The ServiceNow checks are not fully thought through I think. There is a script which checks the credentials before running any powershell script:

"Credentials.psm1" (check agent script files) - here you can see for instance that for SCCM the "no credentials or use mid server service account"-case always fails with error 3...

The default seems to be "testCredentialsWMI": https://docs.servicenow.com/csh?topicname=mid-server-powershell-files.html&version=latest

[Brian Workman]

I had noticed that before, and sometimes I see that it uses one over the other and am not sure how or why. When I do it from one of my environments, it uses the one that doesn't require credentials.

Do you know how to force it to do that one?  I don't really know how to proceed after your comments. Could you elaborate?