BizTalk Server General - HAT Error - Scheduled Job Failed

This is Interesting: Free IT Magazines  
Home > Archive > BizTalk Server General > May 2004 > HAT Error - Scheduled Job Failed





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author HAT Error - Scheduled Job Failed
Sachin Kulkarni

2004-05-19, 2:40 am

Health and Activity Tracking tool generates errors whenever "Save all tracked messages" is clicked. It doesn't save any messages and displays probable causes message (Message not found in the message box....)

I have SQL Server Agent running on the server and tracking properties of all corresponding ports/pipelines/orchestrations are enabled.

For each tracking request, the Event log records following warning message.

------------------------------------------
Event Type: Warning
Event Source: SQLSERVERAGENT
Event Category: Job Engine
Event ID: 208
Date: 19/05/2004
Time: 02:00:00 PM
User: N/A
Computer: <<>>
------------------------------------------
Description:
SQL Server Scheduled Job 'TrackedMessages_Copy_BizTalkMsgBoxDb' (0x1693FD264A78D6408E6297F83857ED07) - Status: Failed - Invoked on: 2004-05-19 14:00:00 - Message: The job failed. The Job was invoked by Schedule 101 (Schedule). The last step to run was s
tep 1 (Purge).For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
-----------------------------------------
Matt Milner

2004-05-19, 8:40 pm

Not sure about the sql error message, but only messages you have marked to
be tracked, and not just their properties, will be available to be exported
that way. There is another command in that same menu to save messages that
will allow you to save suspsended messages for example. You need to turn on
document tracking at the send or receive port configuration.

Matt


"Sachin Kulkarni" <anonymous@discussions.microsoft.com> wrote in message
news:EF373215-8C0A-410E-9F49-DD8E7D252142@microsoft.com...
> Health and Activity Tracking tool generates errors whenever "Save all

tracked messages" is clicked. It doesn't save any messages and displays
probable causes message (Message not found in the message box....)
>
> I have SQL Server Agent running on the server and tracking properties of

all corresponding ports/pipelines/orchestrations are enabled.
>
> For each tracking request, the Event log records following warning

message.
>
> ------------------------------------------
> Event Type: Warning
> Event Source: SQLSERVERAGENT
> Event Category: Job Engine
> Event ID: 208
> Date: 19/05/2004
> Time: 02:00:00 PM
> User: N/A
> Computer: <<>>
> ------------------------------------------
> Description:
> SQL Server Scheduled Job 'TrackedMessages_Copy_BizTalkMsgBoxDb'

(0x1693FD264A78D6408E6297F83857ED07) - Status: Failed - Invoked on:
2004-05-19 14:00:00 - Message: The job failed. The Job was invoked by
Schedule 101 (Schedule). The last step to run was step 1 (Purge).For more
information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
> -----------------------------------------



Sachin Kulkarni

2004-05-19, 11:43 pm

One thing I forgot to mention - Tracking was working properly for some time.
I was able to save all tracked messages.So send and receive ports are
properly configured. I don't remember any particular change in my
application that could have affected the execution of SQL scheduled job
required for tracking. (if that really is the cause of this error!)
I did bit of investigation in SQL server and found out that it complains
about null BodyPartId column or something. But again, it may totally be
irrelevant to the error.

"Matt Milner" <matt.milner@m3technologypartners dot com> wrote in message
news:usTcWFgPEHA.3804@TK2MSFTNGP12.phx.gbl...
> Not sure about the sql error message, but only messages you have marked to
> be tracked, and not just their properties, will be available to be

exported
> that way. There is another command in that same menu to save messages

that
> will allow you to save suspsended messages for example. You need to turn

on
> document tracking at the send or receive port configuration.
>
> Matt
>
>
> "Sachin Kulkarni" <anonymous@discussions.microsoft.com> wrote in message
> news:EF373215-8C0A-410E-9F49-DD8E7D252142@microsoft.com...
> tracked messages" is clicked. It doesn't save any messages and displays
> probable causes message (Message not found in the message box....)
> all corresponding ports/pipelines/orchestrations are enabled.
> message.
> (0x1693FD264A78D6408E6297F83857ED07) - Status: Failed - Invoked on:
> 2004-05-19 14:00:00 - Message: The job failed. The Job was invoked by
> Schedule 101 (Schedule). The last step to run was step 1 (Purge).For more
> information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
>



Matt Milner

2004-05-21, 5:55 pm

I am pretty sure there was another message on this very topic, but I can't
find it right now. If you search the newsgroup, you might have better luck
than I in finding it. It had some resolution to the problem.

Matt

"Sachin Kulkarni" <sachinkmail-tech@yahoo.com> wrote in message
news:Ob0Y88gPEHA.2996@TK2MSFTNGP12.phx.gbl...
> One thing I forgot to mention - Tracking was working properly for some

time.
> I was able to save all tracked messages.So send and receive ports are
> properly configured. I don't remember any particular change in my
> application that could have affected the execution of SQL scheduled job
> required for tracking. (if that really is the cause of this error!)
> I did bit of investigation in SQL server and found out that it complains
> about null BodyPartId column or something. But again, it may totally be
> irrelevant to the error.
>
> "Matt Milner" <matt.milner@m3technologypartners dot com> wrote in message
> news:usTcWFgPEHA.3804@TK2MSFTNGP12.phx.gbl...
to[vbcol=seagreen]
> exported
> that
turn[vbcol=seagreen]
> on
of[vbcol=seagreen]
more[vbcol=seagreen]
>
>



Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com