All already running Jobs are no longer executing

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.

All Forums

SQL Server 2005 Forums

SQL Server Administration (2005)

All already running Jobs are no longer executing

Author

Topic

vgarzon
Starting Member

11 Posts

Posted - 2008-12-01 : 11:21:43

Hi all,

I hope that one of you may come up to the solution of this issue.

I was developing a MS SQL tool on the production database at my office. As it was still in its test period, my tables and my jobs were named like "Test_blablabla" (starting all with test). My jobs were only executing a Stored Procedure, like this:


USE DB_LA_MASTER_DATA
GO
EXEC dbo.test_insert
GO

Until that, everything was allright.
------------
Last saturday, I changed all the table names, created new stored procedures with those new names (but exactly the same code as before) and changed all the names removing the initial "Test_". Additionally (and I don't know if this could have caused a malfunction), I gave some permissions to a user that was already created.

My stored procedures work perfectly but Now I can't start nor stop any job. I checked them, their steps, their schedule and everything is allright, but When I start my job it says:

quote:
Start failed for Job 'Queue_distribution'
Additional Information:
An exception occurred while executing a Transact-SQL statement or batch (Microsoft.SqlServer.ConnectionInfo)

SQLServerAgent is not currently running so it cannot be notified of this action (Microsoft SQL Server, Error: 22022)

But The agent is running. It was not but I put it to work with the following commands

sp_configure
'show advanced options','1' 
RECONFIGURE
go
sp_configure
'Agent XPs','1' 
RECONFIGURE
go

-----------------------------
Technical Details:

quote:

===================================

Start failed for Job 'Queue_distribution'. (Microsoft.SqlServer.Smo)

------------------------------
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Start+Job&LinkId=20476

------------------------------
Program Location:

at Microsoft.SqlServer.Management.Smo.Agent.Job.Start()
at Microsoft.SqlServer.Management.SqlManagerUI.StartAgentJobs.StartJobAction.DoAction(ActionCollection actions, Int32 index)
at Microsoft.SqlServer.Management.SqlManagerUI.ActionCollection.DoWorkOnThread()

Thanks in advance. I hope you can help me with this issue.

Victor

jholovacs
Posting Yak Master

163 Posts

Posted - 2008-12-02 : 15:01:55

This may sound dumb, but did you restart the machine you are connecting from? I've seen things like this a few times where the client loses its mind, and after a fresh restart the problem vanishes. If you haven't already done so, I'd recommend that as step one.

___________________________
Geek At Large

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources