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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2006-10-02 : 07:50:22
|
| Brent writes "I am at the end of my rope.I have a Windows 2000 Server SP4 server, with SQL Server 2000 SP4 installed. SQL Server is the only thing this machine does.Until recently, the server had only 1 database, and it worked flawlessly. My trouble began when I imported another database from a SQL Server 7.0 SP6 server. When the import was completed, the Windows Authentication users and SQL users security permissions were all hosed. I had to resort to deleting all the users, and recreate each one and assign them to their roles.All was well after that. There were no connectivity or rights issues. SQL Job Agent jobs ran with no problems.That very evening, at 6:00pm, the server stopped accepting connections. All VB applications, MS Access, Enterprise Managers, and SQL Query Analyzers refused to connect. Even at the server console, Enterprise Manager would get the "General Network Error" message. I tried connecting via Named Pipes and TCP/IP; no connection.I went into the Windows services and stopped and started SQL Server and the Agent. All was immediately well again. Everyone connected with no problems.The Windows Event Log showed nothing. The SQL Server Logs showed nothing. None of the SQL Agent jobs reported failure, and none are scheduled to run within 30 minutes of 6:00pm anyway. None of my VB applications logged anything queer. There are no Windows Job Scheduler jobs scheduled for that time either.For an entire week, at exactly 6:00pm, the SQL Server became an island onto itself. I tried having the Server and Agent start with the Local System account, and the problem went away for a couple days, but then at 6:00pm on the 3rd day it went down again. I changed it back to log on with a domain account, and the problem went away for 3 days, and then went down at 6:00pm on the 4th day.I'm at a loss I don't know what to try next. Is there some verbose logging I can turn on somewhere? Should I run a bunch of DBCCs on all the databases? Should I re-install the entire server, and restore the databases with scripts? Should I just start taking shots of Jim Beam?Please advise." |
|
|
mcrowley
Aged Yak Warrior
771 Posts |
Posted - 2006-10-02 : 10:22:47
|
| Check in the Client Network Utility on the server to make sure that the Shared Memory protocol is enabled. This should bypass the network when you test the server from the console. Can you set up a ping to start at say 5:55, and run until "the event"? I am thinking this is somehow network related, but actual network related problems are very rare. |
 |
|
|
|
|
|
|
|
SQL Server suddenly won't accept connections