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 |
|
SQLServerDBA_Dan
Aged Yak Warrior
752 Posts |
 Posted - 2004-06-25 : 11:58:28
|
 We rebooted our main SQL Server (SQL2k). It had 5 linked servers setup, 2 on the same network and 3 on another network.After the reboot the machines on the other network only work some of the time when trying to access them via a linked server. The 2 linked servers on the same network have no problems at all. All the routes are setup properly and are persistant. Linked serversSameNetwork1 -- No ProblemsSameNetwork2 -- No ProblemsServer1 -- "sqlserver does not exist or access is denied. [SQLSTATE 42000] (Error 17)."Server2 -- "sqlserver does not exist or access is denied. [SQLSTATE 42000] (Error 17)."Server3 -- "sqlserver does not exist or access is denied. [SQLSTATE 42000] (Error 17)."All SQL Server 2k Standard with 2 processor licenses and the latest service packs.All have been setup as TCPIP and the port has been defined in the client network utility using the IP address not the name.All servers can be "pinged" and you can pull up the physical drive folders from across the networks with no problems.All linked servers are running windows 2000. The main server is running NT.After the reboot only server1 was working with the linked server. The other 2 servers were getting either a timeout or "sqlserver does not exist or access is denied. [SQLSTATE 42000] (Error 17)."I tried to fiddle with the linked servers by changing the passwords and got Server1 and Server2 working over the linked server connection but could not get server3 to work. After about 30 minutes or so I noticed that server 2 was working on and off. It was not consistant about failing or working. I decided to go home for the night. When I came in this morning, only Server2 works. Server1 and 3 do not at all.I have a job setup to pull transactions from a table on server2 to our main sqlserver. This job was running every 5 minutes and it was failing here and there. I have now setup the job to run every 2 minutes and it has not failed for the past hour. When it does fail it gives the error above (server does not exist).I really hope this makes sence to someone... lol  DanielSQL Server DBA |
|
|
SQLServerDBA_Dan
Aged Yak Warrior
752 Posts |
Posted - 2004-06-25 : 13:24:02
|
| The link to the Server that I pull transactions from is still up. I dont understand how changing the job to 2 minutes from 5 could help because there are no time outs set anywhere. Anyone have any comments?DanielSQL Server DBA |
 |
|
|
keithc1
Yak Posting Veteran
88 Posts |
Posted - 2004-06-27 : 21:29:36
|
| May be a silly question but I was wondering if by any chance you rebooted server 1 or 3 . I was thinking that if you were using trusted authentication that if the account were to change for the linked servers well I beleive the sql box's would actually stay online until a service restart or server reboot at which time the changed credentials would take effect thus causing connection issues to all sql box's. If using trusted auth i would look at the sql services account on the NT PDC make sure everything is ok like password didnt expire etc then reapply the account credentials to your other sql box's and restart the services.Keithc MCSE MCSA |
|
|
|
SQLServerDBA_Dan
Aged Yak Warrior
752 Posts |
Posted - 2004-06-28 : 20:55:48
|
quote:
Originally posted by keithc1
May be a silly question but I was wondering if by any chance you rebooted server 1 or 3 . I was thinking that if you were using trusted authentication that if the account were to change for the linked servers well I beleive the sql box's would actually stay online until a service restart or server reboot at which time the changed credentials would take effect thus causing connection issues to all sql box's. If using trusted auth i would look at the sql services account on the NT PDC make sure everything is ok like password didnt expire etc then reapply the account credentials to your other sql box's and restart the services.Keithc MCSE MCSA
Hmm. I guess I didnt mention that. I generally always use trusted connections but these servers (1, 2, & 3) are not on a domain and not on the same network. I dont think that the token will pass across to a new network to allow the trust unless a domain trust is setup and I dont believe that you can do that unless the machines are on a domain. So I used SQL Authentication for my linked servers.I am able to create linked servers and have them all 100% work 100% of the time from my dev box. I cannot get them to work on the production server though. Any other thoughts?DanielSQL Server DBA |
|
|
|
SQLServerDBA_Dan
Aged Yak Warrior
752 Posts |
Posted - 2004-06-29 : 13:12:48
|
| I have noticed that since the reboot our server is getting Demo 19 errors from locking. I dont really understand why because I dont see any deadlocks or any situations that would cause this to occur. Could there be something that is causing the locking and the linked server problem?DanielSQL Server DBA |
|
|
|
|
|
|
Very confusing linked server problem. Please help