August 24, 2003 at 9:50 am
Hi all,
I have one SQL Server 6.5 SP5a running on Windows NT 4.0 Server (not sure about NT sp). Couple of days back, it stopped taking new connections. I rebooted the box after few tries. Still same issue.
But when I checked ERRORLOG and AQLAGENT.OUT, it says that MSDB is full. cannot allocate segment... syslogs is full.
How can I fix this issue?
.
August 24, 2003 at 9:52 am
I have tried to start SQL Server in single user mode with "SQLservr.exe -m". I could see that the SQL Server is started. But I am not able to connect from EM or QA.
Can you please help....
.
August 24, 2003 at 10:04 am
I got it resolved... Please ignore this post...
.
August 25, 2003 at 3:08 am
Cool.
When your syslogs are full run the
DBCC checktable(syslogs)
August 25, 2003 at 5:30 am
Thanks.
.
August 25, 2003 at 5:30 am
I know... But I didn't get connected. Thats the problem I got into. Anyway this is resolved.
.
August 25, 2003 at 8:41 am
Hi,
How you fix it?
Gregoire
August 25, 2003 at 8:54 am
Shame on me.... One of the developer went into the Server with pcAnywhere and changed Network Configuration Utility on the server to TCP/IP.
Before changing it back to to Named Pipes, I have tried few other things including starting the database in Single-User Mode from command prompt, etc...
.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply