vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| For some weeks now, SQLServeragent hangs after I restart the computer. What could be a reason for this? I don't think I changed anything. The system protocol only says "SQLServeragent hung during start" (or similar - I have a German speaking system here). The application protocol says something like: "SQLServerAgent can not be started (reason: Connection to server can not be established. SQLServerAgent can not start.)" MSSQL runs without problems, and when I start SQLServeragent manually, it runs without problems too. System: Microsoft SQL Server 7.00 - 7.00.1077 (Intel X86) Sep 6 2002 15:10:15 Standard Edition on Windows NT 4.0 (Build 1381: Service Pack 6) -mpe |
| |||
| Hi It is usually good to post error numbers as they should be the same regardless of language. As the Agent starts manually without doing anything it seems like a timing problem, I assume that the Agent services dependency on MSSQL service is still present for the service? Is the MSSQL taking longer than before to start? John "Michael Peters" <mpeters@csi.com> wrote in message news:bquped$ais$05$1@news.t-online.com... > For some weeks now, SQLServeragent hangs after I restart the computer. What > could be a reason for this? I don't think I changed anything. > > The system protocol only says "SQLServeragent hung during start" (or > similar - I have a German speaking system here). > > The application protocol says something like: "SQLServerAgent can not be > started (reason: Connection to server can not be established. SQLServerAgent > can not start.)" > > MSSQL runs without problems, and when I start SQLServeragent manually, it > runs without problems too. > > System: Microsoft SQL Server 7.00 - 7.00.1077 (Intel X86) > Sep 6 2002 15:10:15 > Standard Edition on Windows NT 4.0 (Build 1381: Service Pack 6) > > > -mpe > > > |
| ||||
| > It is usually good to post error numbers as they should be the same > regardless of language. there was no error number. The application protocol says, event ID = 103. Don't know if this is an error number. > As the Agent starts manually without doing > anything it seems like a timing problem yes, it looks like it. > I assume that the Agent services dependency on MSSQL service is > still present for the service? yes. Is the dependency necessary, and if not, where can I modify it? > Is the MSSQL taking longer than before to start? I wouldn't know why, but if so, what could I do? -Michael |