Thursday, April 2, 2009
6:59 PM | 
Posted by
David E. Patrick
If you ever move your Great Plains databases from one server to another, make sure you do the following:
use master
go
GRANT EXEC ON smDEX_Max_Char TO PUBLIC
GRANT EXEC ON smDEX_Build_Locks TO PUBLIC
I've been burned more than once by forgetting these. Without them, you can't login and you'll pull your hair out because everything looks right (and indeed is right!) security setup-wise.
Having trouble logging in after a server move? Try this and see if it helps!
use master
go
GRANT EXEC ON smDEX_Max_Char TO PUBLIC
GRANT EXEC ON smDEX_Build_Locks TO PUBLIC
I've been burned more than once by forgetting these. Without them, you can't login and you'll pull your hair out because everything looks right (and indeed is right!) security setup-wise.
Having trouble logging in after a server move? Try this and see if it helps!
Subscribe to:
Post Comments (Atom)
4 comments:
This is part of what is handled by the KB878449_dex_req.sql script, which is part of the server move process. grant.sql should also be run against the DYNAMICS and all company databases after a server move.
Interesting tidbit Lyn! In that script, they grant permissions to these procs in tempdb (versus me doing it in the master db). A slightly different way to skin the same cat. Thanks for the tip!
lifesaver. 3 years later. Thanks for this.
Glad to hear this is still useful info!
Post a Comment