Re: SBS 2003 - Sql server -management- scheduled job stops running

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Steve,

My Sql agent job reaapeared and my scheduled job stopped processing. The job
list displayed this message:
Next Run date - Suceeded 8-16-05 5:25:00 PM
Last Run Status - (date and time are not available)

Usually the job will run every 5 minutes. The Job history showed job
successfully completing at 05:25:00 PM. When all the sql services were
restored the next run date (8-16-05 18:07 PM) and last run status displayed
(8-16-05 18:10:00 PM).
Unknown what the error message was if any that shows in the error/message
dialog box in the job history.

I've looked on-line for any potential related issues like mine and as of yet
haven't found anything that would help me resolve this matter.

Any ideas would be greatly appreciated.

Michael


"mvk" wrote:

> Steve,
>
> Thanks for responding, I'll check it closer to see what happens when it
> occurs again possibly within the next 24 hours. Hopefully it will generate
> an event error to hopefully point me to a possible resolution.
>
> Michael
>
> "Steve Foster [SBS MVP]" wrote:
>
> > mvk wrote:
> >
> > >Recently moved my DB application from a SBS 4.5 to SBS 2003. The transfer
> > >of
> > >data went very smoothly. What I have been expericiencing though is that
> > >every
> > >6 days or so I have to stop and start the sql server services (ver. 8.0)
> > >due
> > >to my sql agent jobs stops processing my VB application at the scheduled
> > >time
> > >created. The job shows that its still running but it isn't running as it
> > >has
> > >been scheduled to run every 5 minutes. Once the scheduled jobs have been
> > >restarted I have 6 days until it does it again like clock work. Never had
> > >this problem when running on SBS 4.5.
> > >
> > >I also run across the same problem with my internal web page used for
> > >administration and report sending after so many days the the reports will
> > >start generating a run time error. After rebooting the server everything is
> > >back to normal.
> > >
> > >Any suggestions to resolve this would be very helpful.
> >
> > SQL Server Agent will only start recurring jobs on schedule if the
> > previous pass has completed. Since you indicate that SQL Server Agent
> > thinks the job is running, it *won't* start the job again. You need to
> > investigate what's actually happening when SQL Server Agent kicks the job
> > off for the first time.
> >
> > --
> > Steve Foster [SBS MVP]
> > ---------------------------------------
> > MVPs do not work for Microsoft. Please reply only to the newsgroups.
> >
.



Relevant Pages

  • Re: How to change the Credential for the replication
    ... It would be nice to know if this is from SQL 2000 or SQL 2005. ... SQL Agent job to sync a pull merge subscriber. ... > we are having mearge replication between two domains. ...
    (microsoft.public.sqlserver.replication)
  • Re: How to check if transaction log of a database fills up?
    ... "Geoff N. Hiten" wrote: ... > It also fires off a SQL agent job called 'TLog Backup MYDATABaSE' that backs ... > Microsoft SQL Server MVP ...
    (microsoft.public.sqlserver.server)
  • Re: DTS Through ASP Page permissions
    ... I am using SQL Server 2000. ... What version of SQL Server are you running? ... If it is a SQL Agent job running as a sysadmin account, ...
    (microsoft.public.sqlserver.dts)
  • Re: Scheduling
    ... The default behavior of a SQL Agent job step is to quit the job when an ... step 3 will execute only if both steps 1 and 2 ... SQL Server MVP ... > steps sayingexecute step2 on success of step1. ...
    (microsoft.public.sqlserver.server)
  • Re: Scheduling DTS Packages on 64-bit SQL Server
    ... My understanding is that DTS components are not available for 64-bit SQL ... > I found the following comment on Microsoft's website in regards to scheduling> a DTS package on a 64-bit SQL Server installation. ... do I need> to buy a 32-bit copy of SQL Server to store my packages on to be able to> schedule them? ...
    (microsoft.public.sqlserver.dts)