Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
jparker
Posting Yak Master
118 Posts |
Posted - 2005-01-11 : 11:12:22
|
I have set the connection string correctly on my new server. Set the IIS permissions as of the old server. Set the security on the folder where the database resides to be the same as the old serverYet I get the following problem which is a connection string.Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database requested in login 'my_live'. Login fails.Can you please advise me on things to try  |
|
|
MichaelP
Jedi Yak
2489 Posts |
Posted - 2005-01-11 : 11:43:18
|
| Sounds like the user that you are connecting with doesn't have access to the database. Check the user security settings in EM.Michael<Yoda>Use the Search page you must. Find the answer you will.</Yoda> |
 |
|
|
jparker
Posting Yak Master
118 Posts |
Posted - 2005-01-11 : 11:49:30
|
| The users are intact and look to be the same as the old server. Is there a log to check.In addition can you think of anything else I may have overlooked? |
 |
|
|
Sitka
Aged Yak Warrior
571 Posts |
Posted - 2005-01-11 : 12:04:07
|
| I have set the connection string correctly on my new server..Set the security on the folder where the database resides to be the same as the old serverI'm not sure what that stuff means but..I'll guess this is a new SQL Server install I'd guess the accessing User is in an "orphaned" state. That is the User is intact but not the User/Login association. "orphaned" is the search termI wish someone would start an Official XML Rant Thread. |
 |
|
|
jparker
Posting Yak Master
118 Posts |
Posted - 2005-01-11 : 12:32:30
|
| spot on thats exactly what the problem was.never encountered that one before |
 |
|
|
Sitka
Aged Yak Warrior
571 Posts |
Posted - 2005-01-11 : 13:13:57
|
| Just for the future, I don't know if it's only here but the Enterprise Managerhas been a bad place for me to track down orphaned users. It can get out of sync and makeschasing permission problems difficult. The QA and procs are the way to go if there is lotsof work to be done in a rebuild.I wish someone would start an Official XML Rant Thread. |
 |
|
|
|
|
|