InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSat, 18 May 2013 03:52:09 GMT20http://www.sqlservercentral.com/Forums/Topic8379-7-1.aspx[quote][b]Hawkeye_DBA (4/26/2010)[/b][hr]Great post!Here's the article from Microsoft:http://support.microsoft.com/kb/914171[/quote]Thanks. It's resolved the issue.Fri, 19 Oct 2012 18:14:48 GMTsudhakarahttp://www.sqlservercentral.com/Forums/Topic8379-7-1.aspxWe had to re-install SQL Server and one of DBA ran a "ATLER DATABASE msdb modfiy file..." to point to the original msdb files, which worked great, but the jobs would not run. I had to create a Credential and a new proxy to repl dist. Once I change the jobs to use these I restarted the agent and started the jobs and they are all running.ThanksDMon, 07 Nov 2011 12:00:09 GMTDave Otthttp://www.sqlservercentral.com/Forums/Topic8379-7-1.aspxGreat post!Here's the article from Microsoft:http://support.microsoft.com/kb/914171Mon, 26 Apr 2010 14:38:05 GMTHawkeye_DBAhttp://www.sqlservercentral.com/Forums/Topic8379-7-1.aspx"TVR" you are the best! My problem was I have restored another MSDB from another Instance. running your script worked. thanks.Fri, 04 Sep 2009 06:39:10 GMTsightdev-358295http://www.sqlservercentral.com/Forums/Topic8379-7-1.aspxI realise this thread is a bit old, but I also came across a "suspended" status for my logreader as well as distribution agent for the first time, and since I couldn't find much info either about this unfamiliar "suspended" status, I thought I'll post my scenario as it might be usefull to someone.I was "playing" around on one of our test servers by using the distribution and msdb databases from a different test installation on my current test installation to see the effect on replication.After starting the SQL services, neither my logreader or distribution agent wanted to start.The following entries appeared in my agent's error log:logreader[i]2008-09-19 10:21:23 - ! [LOG] Step 2 of job 'SERVER\INSTANCE-repl_testdb-1' (0x23DDF76727) cannot be run because the LogReader subsystem failed to load. The job has been suspended[/i]distribution agent[i]2008-09-19 10:22:39 - + [000] Request to run job SERVER\INSTANCE-repl_testdb-pub_name-server\instance (from User domain\user) refused because the job has been suspended[/i]In my scenario, the reason for the suspension of these jobs was due to the fact that I didn't update the msdb.dbo.syssubsystems table after replacing the old msdb database files. (these files originated from a different instance and installation path)After updating the table with the script below, and restarting the SQL Server agent, my logreader and distribution agent's suspended statuses were removed.use msdbgodelete from msdb.dbo.syssubsystemsexec msdb.dbo.sp_verify_subsystems 1goSo it seems the suspended status is applied to jobs that are unable to execute due to underlying problems (in my case the logreader subsystem) and not neccessarily something relating to the steps of the jobIt seems that a job can't be started while in suspended status, and as Andy mentioned above, you will need to find the cause, fix that, and after a SQL Agent restart, the status should be gone.Fri, 19 Sep 2008 03:55:37 GMTT_VRhttp://www.sqlservercentral.com/Forums/Topic8379-7-1.aspxDid you open the job history to see what the failed message is all about. The fact the snapshot suspended is just that it could not run. Check the job history for more details on the root failure. Not sure but may have put more detail in SQL Logs and Event Viewer logs. Sun, 08 Dec 2002 07:25:00 GMTAntares686http://www.sqlservercentral.com/Forums/Topic8379-7-1.aspxInteresting. I guess the first thing is to figure out why the job is suspended? If you run as SA does it work? Possibly the snapshot job is still being created or is in progress when you try to run? Dont see much in BOL about why something is suspended.Andyhttp://www.sqlservercentral.com/columnists/awarren/Sun, 01 Dec 2002 15:50:00 GMTAndy Warrenhttp://www.sqlservercentral.com/Forums/Topic8379-7-1.aspxSorry I was away. I posted this description on ms newsgroup. Only response was to verify winnt/system32/sqlsrv32.dll was set in registry correctly and it it.***************I created my publication and then I see a new JOB in the Management/SQLServer Agent/Jobs which is a snapshot job and it is ATCMaster-ATCMaster-18.Then I push a subscription and then there is the other new job in theagent/jobs which is a distribution job and it is atcmater-inhousewebtest-92.(of course this number increases on each new attempt!<g>)Then I have an app where I am using sqldmoI create my dmo object, then my connetion to the database and then a job(the snapshot 18) and then I try to start the job.This is the right process right. First run the snapshot job then thedistribution. I have writen a similar program without sqldmo. Instead I usedsnapshot.exe and then create a distribution object.So back to this application!Here is the code******Dim server As New SQLDMO.SQLServer()server.Connect("brewster")Dim myjob As SQLDMO.Job =server.JobServer.Jobs.Item("BREWSTER-ATCMaster-ATCMaster-18")myjob.Start()*******Simple, right?It steps right through to myjob.start and then crashes when I try to startwith this message:[Microsoft][ODBC SQL Server Driver][SQL Server]SQLServerAgent Error: Requestto run job BREWSTER-ATCMaster-ATCMaster-18 (from User NT AUTHORITY\SYSTEM)refused because the job has been suspended.This leads me to look at Enterprise Mgr where I can see the evil red X nextto the snapshot and it says Runnable=NO(the job is supended)Status-SuspendedAfter this happend the first few times, that is when I started just fiddlingin Ent Mgr and deletin ghte subscription and the publication, recreating andwatching that snapshot go right to suspended status.boo hoo <g>Any ideas?My goal is to write a web app that will run the replication for me so that Ican let IIS handle the security and not have to open up permissions to usersfor doing the replication. Currently I have an app role on this database soI am the only person who can run my original replication application whichis a vb5 app that worked beautifully until I locked down the server. I havetried to get around this problem for months and this is my new theory totest, yet I keep getting stuck with this suspend!Thanks very much. Sun, 01 Dec 2002 14:52:00 GMTjlermanhttp://www.sqlservercentral.com/Forums/Topic8379-7-1.aspxSuspended how? Job is disabled? Agent just not running?Andyhttp://www.sqlservercentral.com/columnists/awarren/Thu, 28 Nov 2002 11:40:00 GMTAndy Warrenhttp://www.sqlservercentral.com/Forums/Topic8379-7-1.aspxAny error that you can post? Thu, 28 Nov 2002 10:21:00 GMTRodrigo Acostahttp://www.sqlservercentral.com/Forums/Topic8379-7-1.aspxI should clarify that this is a snapshot. The agent is running.I have created this before with no problems, but it was acting up so I deleted and recreated it (the publication) and this just keeps happening. I am a programmer, not a sql server admin, but I kind of get stuck doing this so I feel like a total hacker! <g> Sat, 23 Nov 2002 07:50:00 GMTjlermanhttp://www.sqlservercentral.com/Forums/Topic8379-7-1.aspxWhy would a push subscription job be suspended immediately after I create it?I just don't understand - boo hoo!Thanksjulie Fri, 22 Nov 2002 17:44:00 GMTjlerman