BCP Utility Error logging into GP Utilities as DYNSA, do not receive error when logging in as SA. This is a new install, the ODBC connection is 32-bit and was created by the installation. We are running GP Utilities by right click and run as administrator. Has anyone run into this before? The client does not want to create new client installs by using SA, they want to use DYNSA. I believe this is supported??? Any input is much appreciated.
*This post is locked for comments
This is on GP2015 and I believe the server had to be recreated, by the client, so it is very possible that DYNSA is not the owner on the databases. I am checking with the client and will update the post. Thank you for the response!
I agree with Vaidy, I've never seen this from a long while as well.
My quick fix would be to copy the whole GP folder from another existing client which is working with no issues, then go to the GP folder and make sure that the synchronization command is set to false (Syncronize = FALSE) . Then, proceed with deleting the ODBC and re-creating it all over again.
Let us know how things go with you,
This error is too old. And I haven't seen this in long time.
However, you may check the DB owner at the backend and set DB owner to DYNSA if it's someone else. This could be one possible reason.
Also run GP utilities once as "sa" and see if DYNSA is already setup. You may also try changing the password of DYNSA and see if that works.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,214
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (