Cannot open database "EXT" requested by the login. The login failed
Daniel asked 7 years ago
The EXT company database is fairly new and my integrations work for other GP companies but not this one. I have run system maintenance in SC and also ran the GP Resource Cache to no avail…
I checked SQL security and the user (the one SC keeps trying to use) has access to the company database and is in the DYNGRP role. I even changed the tenant in SC to use ‘sa’ but it keeps trying to open the database with this one user…
Do anyone know how to change what user it is trying to use or get the user password in “sync”?
Thanks, Dan
I checked SQL security and the user (the one SC keeps trying to use) has access to the company database and is in the DYNGRP role. I even changed the tenant in SC to use ‘sa’ but it keeps trying to open the database with this one user…
Do anyone know how to change what user it is trying to use or get the user password in “sync”?
Thanks, Dan
Where/when are you getting this message in SmartConnect?
when I run a map, it selects the record and then takes a while but returns the error. I can run the same map into another GP company but for one company, I get the error: Cannot open database “EXT” requested by the login. The login failed.
Login failed for user ‘xxxxxx\gpconn’ FYI: I xx’ed out our domain…
another note: not sure how this relates.. I cannot log into GP with the “gpconn” user but I can log into SQL with that user. With that being said, I can integrate data into another GP company but this one company, I can’t. so not sure if that is the issue… If I change the user password in GP, I can log into GP but still get the same error running the map and then I can’t log into SQL.
how do I get SC to use another user or get the security the same for this company as it is with the other GP companies?
You will need to see what user is running your eConnect service and then make sure that user has the DYNGRP role in SQL.
I did and that user did have DYNGRP role in SQL and could import to other companies, just not this particular one. I changed the eConnect service to a different user and it worked with that user. I guess there is a mis-match in the password for my first user and that particular company database.
Thanks…