RE: SQL-Server and Win2k3

• Previous message: Rand Boyd [MSFT]: "RE: Connection Error 18452 - Login failed for user '(null)'"
• In reply to: Fiete: "SQL-Server and Win2k3"
• Messages sorted by: [ date ] [ thread ]

Date: Sat, 20 Nov 2004 06:53:30 GMT

If your servername is the same, and ip address is the same then you should
not have to resetup your DSN's. Perhaps this newly installed instance is
listening on a different port?

1. Examine closely what is different from the "OLD" DSN vs the "NEW" DSN
2. Check if your DSN creates an alias. To do go to start->run->cliconfg.exe
select the alias tab
3. If you have to recreate your DSN after moving SQL, even though the name
is exactly the same and the IP is exactly the same, then it is possible that
a) your "old" dsn was setup to use a specific network library(for example
named pipes), but your instance of sql is NOT listening on this network
library. To view what network libraries SQL is listening on, examine the
sql error log. For Example:

2004-11-17 02:01:22.54 server SQL server listening on 192.0.0.0: 1433.

2004-11-17 02:01:22.54 server SQL server listening on 127.0.0.1: 1433.

…

2004-11-17 02:01:24.14 server SQL server listening on TCP, Shared
Memory, Named Pipes.

b) your "old" dsn could have hard coded the port where sql was listening on
and now SQL is listening on a different port than what it was listening on
before

There could be many other reasons for the difference in behavior. Knowing
what error you get when trying to connect with the "OLD" dsn would aide in
determining why there is such a difference. For instance if when trying to
connect with the old DSN you get error: "SQL Server does not exist or
access denied" then I would suspect the problem is one of the reasons I
mentioned above. However, if you get an error like "login failed for user
'usr'" then it may be that not all logins were migrated,etc.

Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.

Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.

Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx

• Previous message: Rand Boyd [MSFT]: "RE: Connection Error 18452 - Login failed for user '(null)'"
• In reply to: Fiete: "SQL-Server and Win2k3"
• Messages sorted by: [ date ] [ thread ]