I used Database Disabler on GP 2013 to disable all databases before I began an upgrade to GP 2016. That upgrade included a server migration.
Now when I try to login on the new install (upgrade went fine) no companies are shown. I suspect it is because of database disabler, but there isn't a database disabler listed in PSTL on GP 2016. So I can't simply uncheck the databases. We have 50 companies, so I do not want to have to reset all security to the companies if I don't have to.
Is there a way reverse whatever Database Disabler does on my new instance so that users can get logged back in, thanks. I have used SQL profiler to try and nail down what it does, but I can't find the sprocs it references in the database to review them...
Any ideas?
*This post is locked for comments
I have the same question (0)

Report
All responses (
Answers (