I've been handling the system administration for one of my clients recently. They frequently create new GP company databases (6 last month). The process I've been using since we implemented the product was to go to GP Utilities, select "Create New Company", click "Process" and on the next screen use the drop down menu to select an existing company from which to copy the security access. This worked flawlessly on all of the previous databases (probably 10-15 in total), but with the last 6 something strange happened.
I created the company databases, configured them and then set the users loose on them. When users tried to log in to one of the new companies, they got the following message: "A get/change first operation on table 'coProcess' failed accessing SQL data." There are a couple of articles out there on this message:
https://support.microsoft.com/en-us/kb/850997: not applicable; we didn't move the server
https://www.experts-exchange.com/questions/24496163/Great-Plains-Error-A-get-change-first-operation-on-table-'coProcess'-failed.html: This solution works, however there's no explanation on how to prevent it from happening again.
And finally, the big kahuna: http://dynamicsgpgeek.blogspot.com/2009/10/dynamics-gpsql-database-user-disconnect.html: Again, the solution works but there's no explanation on how to prevent this from happening in the future.
Can anyone explain to me why my users are not being automatically added to the DYNGRP group in new companies when I copy security access from an existing company database while running the utilities?
*This post is locked for comments
I have the same question (0)
