GP 2015 R2 Workflow error when user approve a document

(0) Share

Report

Posted on by Community Member

I am running GP 2015 R2 workflow and got a new error after upgrade that was not there before R2!

The error appears when users approve a document even though the document get approved!

The error is:

"[Microsoft][SQL Server Native Client 11.0][SQL Server]A.NET Framework error occurred during execution of user-defined routine or aggregate "GetAssignedUsers". System.ArgumentNullException: Value cannot be null.Parameter name: UsersListGuidSystem.A

Any advice to solve this issue?

*This post is locked for comments

I have the same question (0)

All responses (19)

Answers (1)

soma 24,410 on at

Like (0)

Report

Please run the below command in SQL server against system database. After that check the workflow, it will not through this error again.

exec wfDeployClrAssemblies

Hope this helps!!!

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Still same problem after running it!

Was this reply helpful? Yes No
Beat Bucher GP Gee... 28,058 Moderator on at

Like (0)

Report

Hi Mohannad,

Have you checked and made sure every GP user that's defined in some ways in the FW approval tree has a valid associated AD userID ?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Yes, they do!

Was this reply helpful? Yes No
Bill Campbell 12 on at

Like (0)

Report

Beat, side question - do all users in the Approval Tree for the WF have to be defined as GP Users as well? I have a situation where the managers and Directors will not be accessing GP (application) directly and so we have not set them up as GP users. They are in the WF as Approval Agents, but I am using their AD User ID.

Just wondering if I am reading to much into this comment.

Was this reply helpful? Yes No
Beat Bucher GP Gee... 28,058 Moderator on at

Like (0)

Report

Bill,

Yes they have to... however you can check them as 'Web Client User Only' so SQL will not create any account for those users and they will only 'virtually' exist in GP and linked to their AD user-ID.

Note : when switching an existing GP user to the 'Web Client User only' option, the user account gets deleted from the SQL server... but not the SY01400 table. So their is no SQL security anymore and it relies solely on the AD user-ID link to grant the user access into GP.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Beat,

Do you know the reason for this error in workflow approval:

"[Microsoft][SQL Server Native Client 11.0][SQL Server]A.NET Framework error occurred during execution of user-defined routine or aggregate "GetAssignedUsers". System.ArgumentNullException: Value cannot be null.Parameter name: UsersListGuidSystem.A

Thank you,

Was this reply helpful? Yes No
Bill Campbell 12 on at

Like (0)

Report

If there was not a user ID in GP for this Approver - not even once - I still have to create the WEB only user? What security to provide - or is that the only criteria?

Was this reply helpful? Yes No
Peter Muchira 1,912 on at

Like (0)

Report

Hi Mohannad,

I hope you did some system refreshing after running the query above (provided by Soma). You can consider, exiting GP, and restarting the SQL service as well.

Was this reply helpful? Yes No
Beat Bucher GP Gee... 28,058 Moderator on at

Like (0)

Report

Bill,

If you never had GP users defined for the BP TS & EE reports (which was not required, as the BP user was linked back to the Employee ID in GP), you will have to create them in GP and check the box for the 'Web Client User' only, so no SQL user gets created.

If you don't do that, the system will probably not be able to route the document to the proper person (though the question remains open if you use the GP Web Services and they reply directly by e-mail).

Was this reply helpful? Yes No