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 |
|
elancaster
A very urgent SQL Yakette
1208 Posts |
 Posted - 2005-01-17 : 06:37:34
|
| This is another one of those lovely problems where it's been working fine for years and now suddenly doesn't, but everyone swears nothing has changed.We have several SQL Servers, all of which need to communicate with each other. As of a few days ago...Server A - cannot register Server B through EM (IP or Alias). you can ping Server B fine but through EM it says "Server does not exist or Access is denied"Server B can register Server A with no problemsAll other Server can register both A and B with no problems.(Did I explain that ok?)Any help appreciated |
|
|
RM
Yak Posting Veteran
65 Posts |
Posted - 2005-01-17 : 07:15:18
|
| Cross check the user name and pwd with which you are registering Server B. Are you able to connect Server B through query Analyzer? |
 |
|
|
elancaster
A very urgent SQL Yakette
1208 Posts |
Posted - 2005-01-17 : 08:03:31
|
| No, QA does not connect to it either.We have some users who access a web page (physically stored on Server A), which in turn uses a DB on Server B. This is not working due to the connection problems either.How will I usernames / passwords? Are we talking windows or SQL logins?Windows doesn't have any specific logins for any of the servers, SQL has a login for some (incl Server A & B) with sysAdmin rights.thanks |
|
|
|
RM
Yak Posting Veteran
65 Posts |
Posted - 2005-01-17 : 09:49:00
|
| I was talking about the sql login and pwd only. Well, this means that the SQL Server B is available on network and is in the list of active servers on Server A. If you are sure on the login and pwd then try creating Server Alias using the client network utility. Specify network library as TCP/IP and the port number. |
|
|
|
elancaster
A very urgent SQL Yakette
1208 Posts |
Posted - 2005-01-17 : 11:23:10
|
| That's worked, thanks.But I don't understand how it can work one day but not the next. None of the other servers have an alias set up and they work fine. |
|
|
|
RM
Yak Posting Veteran
65 Posts |
Posted - 2005-01-18 : 00:53:15
|
| As per BOL "an instance of SQL Server may be configured to listen on alternate network addresses. If this is done, client applications connecting to that instance must explicitly specify the alternate address. While applications could specify the alternate addresses on each connection request, it is easier to use the Client Network utility to set up an alias specifying the alternate addresses. Applications can then specify the alias name in place of the server network name in their connection requests."May be SQL Server has been re-installed at your end on a different network address |
|
|
|
|
|
|
SQL Server registration error