Prev: View SQLDmpr.mdmp File
Next: ActiveX component can't create object (DSO)
From: Tibor Karaszi on 15 Dec 2006 05:51
Then my guess is that server was in some strange state, schedulers all too busy or similar. You
might be able to pick up some error from SQL Server in the event log at that time. If not, I can't
really suggest any more, I'm afraid.

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/


"Shri.DBA" <ShriDBA(a)discussions.microsoft.com> wrote in message
news:188BAC3E-76CE-42FE-A8E8-25B70E2BCFD3(a)microsoft.com...
> Hi Tibor,
>
> The job ran successfully from the next run without any problem. All the job
> in the SQL Server are running without any issues.
>
> Regards
> Shri.DBA
>
> "Tibor Karaszi" wrote:
>
>> Sorry, you are right. Agent is a client app to SQL Server.
>>
>> Message says that Agent couldn't log on to SQL Server. This might be because SQL Server was
>> *extremely* busy or some strange state at that time. Can you run TSQL Agent jobsteps now? If no,
>> perhaps the login in SQL Server that agent uses is messed up?
>>
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>>
>> "Shri.DBA" <ShriDBA(a)discussions.microsoft.com> wrote in message
>> news:734E4207-A50C-4EE3-8CC6-2D6D1E6D632A(a)microsoft.com...
>> > Hi Tibro,
>> >
>> > I have given the actual error message returned by SQL Server. See below. The
>> > database is in Full recovery model.
>> >
>> > Regards
>> > Shri.DBA
>> >
>> > "Tibor Karaszi" wrote:
>> >
>> >> If you in job history check "show step details", you might find the actual error returned by
>> >> SQL
>> >> Server. Or, assuming you have an output file for the job step, check that file. We really need
>> >> the
>> >> error message returned by SQL Server. One possible reason if that the database was in simple
>> >> recovery mode.
>> >>
>> >> --
>> >> Tibor Karaszi, SQL Server MVP
>> >> http://www.karaszi.com/sqlserver/default.asp
>> >> http://www.solidqualitylearning.com/
>> >>
>> >>
>> >> "Shri.DBA" <ShriDBA(a)discussions.microsoft.com> wrote in message
>> >> news:AE551080-F51E-492B-9CB0-711C4A27847A(a)microsoft.com...
>> >> > All,
>> >> >
>> >> > I have a job to take transaction log backup every 15 mins. Today morning the
>> >> > job failed while it was taking transaction log backup of the databases.
>> >> >
>> >> > When I checked for the job failure reasons I got the follwoing information
>> >> > from the below sources
>> >> >
>> >> > Job Output File
>> >> > ---------------
>> >> > Msg 49999, Sev 19: Failed to login to SQL Server [SQLSTATE HY000]
>> >> >
>> >> > SQL Agent Error Log
>> >> > --------------------
>> >> > [SQLSTATE 42000] (ConnExecuteCachableOp)
>> >> >
>> >> > Can some body tell, why the job has failed.
>> >> >
>> >> > Regards
>> >> > Shri.DBA
>> >> >
>> >> >
>> >>
>> >>
>>
>>

First  |  Prev  | 
Pages: 1 2
Prev: View SQLDmpr.mdmp File
Next: ActiveX component can't create object (DSO)