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 |
|
bfsteel
Starting Member
2 Posts |
 Posted - 2008-12-09 : 11:29:05
|
| Looking for someone with experience dealing with Agent problems in 2000 SQL SERVER. Please reply with a post so I can describe my problem. THanksBob |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2008-12-09 : 11:31:09
|
| post your problem and somebody will help you out |
 |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-12-09 : 11:38:11
|
| Please reply with your post so we know what you are stuck in? |
|
|
|
bfsteel
Starting Member
2 Posts |
Posted - 2008-12-09 : 12:10:00
|
| I have a Sql server agent that will not start correctly not allowing backup jobs to complete. The agent is set to start automatically and the agent was not starting the first time I looked into the problem. I tried rebooting and that didn't help either. So I noticed that the messenger service was disabled. So I enabled it and tried a reboot and the agent service came up to started. But when you went to the job and tried to start the job, it stated the agent was starting and could not do the job(error 14258). If you looked in the viewer the agent was started and also in service manager it was started. so I went into the agent.out log file and it stated that the database was recovering. So i looked in the viewer and it stated that the database was 100% complete. Next I went into the sqlserver log and it gave me a 15457 error that the config file had been displayed/changed and do a reconfigure. This being an informational message, I think this does not effect the operation of the agent.Last night I went to do a manual backup of the db and trans log, so I stopped the sqlserver and it advised me that it would stop the agent but it could not stop the agent so it didn't stop the sqlserver. So I had to disable the agent in order to do a backup of the db and trans log. When I rebooted the computer after setting everything to automatic, the agent would not start completely. So it shows starting.There is something about lightweight pooling that causes fiber mode which will give this type of error but I am in thread mode as it stated in the sql server log.This appeared several days after a new antivirus Sophos was installed. I have been thinkin about removing it and seeing what effect this has on it.Any suggestions.Bob |
|
|
|
|
|
|
Sql Server 2000 Agent