OOB "Add User to Group" AD activity - error msg "Exception from HRESULT: 0x80005000"

TylerTeter
Kilo Guru

The out-of-box "Add User to Group" AD activity, results in failure and it's giving an error msg of "Exception from HRESULT: 0x80005000". I've done some research on that error code, and similar ones for this activity and many think it's some kind of credential error. My question is, what kind of access must be configured for this activity to work? I didn't notice the documentation mention any needed additional access.

Add User to Group AD activity

Active Directory activity pack

There was a similar question asked on - AD orchestration authentication $cred is null but they only answered for the first half, how to do it via the PowerShell Activity. I'm hoping to use the OOB activity if possible however.

I'm planning on digging into this and debugging more on my end, but any help would be appreciated!

Thanks,

Tyler

find_real_file.png

1 ACCEPTED SOLUTION

Thanks Tyler!



After a bit more digging, I found the problem record in HI. Like you, we were on Geneva Patch 7 and this issue was fixed in Patch 8. The workaround was successful for me.



ServiceNow KB: PRB654096: AddUserToADGroup.ps1 PowerShell script is missing a parameter (KB0563575)



Thanks again for the help and pointing me in the right direction!



- Justin


View solution in original post

10 REPLIES 10

Community Alums
Not applicable

Tyler,


What version of ServiceNow are you on? I believe there was an issue in this activity in Geneva.


Ben


Ben,



We're currently running Geneva Patch 7. Do you know which version fixes this issue? Is there a change log on this that goes into further detail on the fix?



Thanks,


Tyler


Tyler,



Did you ever figure this out? I'm on Geneva as well and just encountered this error.



- Justin


Justin,




I went ahead and just used my own homemade PowerShell script and put it into a Run PowerShell activity. It ended up worked better actually because I had more flexibility for various AD Checks (inactive, elevated user/group, etc).   I also needed to be able to check against users in multiple domains, which this activity doesn't support also.



In short I never got this activity to work however.



Thanks,


Tyler