January 13, 2004 at 10:33 am
I am running SQL 2000 with SP 2.
The system had been running fine for about a year. I we have not made any recent changes.
Problem:
The SQL jobs no longer run.
We have been sucessfully running SQL jobs. About a week ago one job stopped running and after re-booting the server none of the jobs run. I have stopped and restarted the SQL Agent several times and the computer logs reports no problems. However when I select a job, the computer displays the following error message.
SQL-DMO (ODBC SQLState:4200) - Error 14258: Cannot perform this operation while SQLServer Agent is starting try again later.
Any help or suggestions would be greatly appreciated
I fixed the problem. Upon further examination, the serveragent log under information category said, that is was waiting for the SQL server to recover databases. It turned out someone unknown had set NT fibers - ON. NT Fibers conflict with DTC transactions. I turned off NT fibers and everthing worked.
January 13, 2004 at 1:53 pm
Is everything working now? It's hard to tell from the post. Are your jobs executing?
January 16, 2004 at 8:40 am
Yes, thank you.
I found the answer in the Microsoft Knowledge base (article 303287). The conflict between NT fiber mode and the DTC services is a known "bug."
After further checking I decided that no one had recently set the system to run NT fibers, and that it had always been on. So the little mystery would be why all of a sudden on a stable unmodified system did it start to fail? Most likely it will always be a mystery!
May 25, 2007 at 1:19 pm
I can appreciate that this is a dead post but we have a client that experienced the exact opposite; while troubleshooting a server slow down issue, the IT manager found an article that stated fibers bad, so, he turned it off. Every automated process died and refused to run until he turned it back on. Of course, we don't know whether he did a full configuration change in a query analyzer or just set the flag in the server configuration window.
Now they want me to find out why turning fibers off would kill the scheduled processes.
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply