RE: SQLSERVERAGENT Warning in EventLog (Event ID 208)
From: Eldar Musayev (Eldar_Musayev_at_online.microsoft.com)
Date: 01/06/05
- Next message: Eldar Musayev: "RE: Load balancing BT server 2004"
- Previous message: eXavier: "Re: multiple receive locations"
- In reply to: Silly_King: "RE: SQLSERVERAGENT Warning in EventLog (Event ID 208)"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 06 Jan 2005 17:56:16 GMT
About the script, frankly, I am not sure why it was not posted. Probably,
for the same reason as the rest of BizTalk parts -- it's just coming with
the service pack. Glad, you were able to fix your issue,
good luck,
Eldar
This posting is provided "AS IS" with no warranties, and confers no rights.
EBusiness Server Team
--------------------
>> Thread-Topic: SQLSERVERAGENT Warning in EventLog (Event ID 208)
>> thread-index: AcTzem7Nvmh97W1+SQamUznYlOjwNQ==
>> X-WBNR-Posting-Host: 68.54.158.86
>> From: "=?Utf-8?B?U2lsbHlfS2luZw==?="
<SillyKing@discussions.microsoft.com>
>> References: <DEDCA8BF-F6A1-4257-B02E-B1DBB2D7BAF3@microsoft.com>
<oym4BS38EHA.3512@cpmsftngxa10.phx.gbl>
>> Subject: RE: SQLSERVERAGENT Warning in EventLog (Event ID 208)
>> Date: Wed, 5 Jan 2005 15:01:04 -0800
>> Lines: 96
>> Message-ID: <137B0DE5-8D29-4186-ACA2-450452D22D60@microsoft.com>
>> MIME-Version: 1.0
>> Content-Type: text/plain;
>> charset="Utf-8"
>> Content-Transfer-Encoding: 7bit
>> X-Newsreader: Microsoft CDO for Windows 2000
>> Content-Class: urn:content-classes:message
>> Importance: normal
>> Priority: normal
>> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>> Newsgroups: microsoft.public.biztalk.server
>> NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>> Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
>> Xref: cpmsftngxa10.phx.gbl microsoft.public.biztalk.server:10701
>> X-Tomcat-NG: microsoft.public.biztalk.server
>>
>> Eldar, thank you for replying. However, I did not reinstall BTS nor did
i
>> change the MessageBox db. I think i figured out (just in the last few
hours)
>> what happened, and it's not pretty:
>>
>> Some time last week I played with "Publish Schema as a web service"
option
>> of the BizTalk Web Services Publishing Wizard. When i created that web
>> service i specified a particular message schema as a type for one of the
web
>> service operations. Apparently, that was a mistake, as all messages of
that
>> type started to be sent to that web service, regardless of where they
>> *should* have been sent! So if a request came in on a different web
service
>> (Request/Response pattern), the Response to the request was sent to the
>> "test" WS i'd created via "Publish Schemas as a web service" option,
rather
>> than to the web service that received the Request! (This, as a
consequence,
>> caused the web service clients to time out, as they never got a response
from
>> me, even though the successfully sent a message...)
>>
>> I'm guessing here now because i'm not an expert on BizTalk database
internal
>> processes, but the fact that all messages of the misdirected type were
now
>> "delivered, not consumed", the delivery queue started to pile up,
especially
>> as i was doing more and more frenetic "testing". I don't know how this
>> affected the part purging job, exactly. i do know, however, that when i
tried
>> to run the bts_PartsPurge sproc directly, i got an error message (which
i
>> failed to record, sadly). The gist of the error (or as well as i
remember it)
>> was that the number of Parts exceeded the storage capacity provided by a
>> signed short integer (>32K), and so the sproc bombed out.
>>
>> i think the upcoming SP1 script would have helped me out by clearing the
>> MsgBox db of debris, but i resolved my problem by removing &
reinstalling
>> BizTalk & starting fresh with new, clean, and happy databases.
>>
>> By the way, i saw the SP1 scripts mentioned in a few posts here - any
reason
>> the scripts couldn't be posted somewhere as an unsupported "use at your
own
>> risk" option for other almost S.O.L souls out there?
>>
>> "Eldar Musayev (MSFT)" wrote:
>>
>> >
>> > You probably reinstall BizTalk or changed the MessageBox db. When you
>> > uninstall BizTalk, purge jobs are left in the SQL database along with
the
>> > data. If you later remove the data, the purge jobs starts to fail. In
this
>> > case, you can remove the purge job manually, by going in SQL Server
>> > administration into the database -> SQL Agent jobs and removing these
jobs
>> > manually.
>> >
>> > Regards,
>> > Eldar
>> >
>> > This posting is provided "AS IS" with no warranties, and confers no
rights.
>> >
>> > EBusiness Server Team
>> > --------------------
>> > >> Thread-Topic: SQLSERVERAGENT Warning in EventLog (Event ID 208)
>> > >> thread-index: AcTybwsFSCjSAHMzRaO6ntshk58yAA==
>> > >> X-WBNR-Posting-Host: 68.54.158.86
>> > >> From: "=?Utf-8?B?U2lsbHlfS2luZw==?="
>> > <SillyKing@discussions.microsoft.com>
>> > >> Subject: SQLSERVERAGENT Warning in EventLog (Event ID 208)
>> > >> Date: Tue, 4 Jan 2005 07:07:01 -0800
>> > >> Lines: 15
>> > >> Message-ID: <DEDCA8BF-F6A1-4257-B02E-B1DBB2D7BAF3@microsoft.com>
>> > >> MIME-Version: 1.0
>> > >> Content-Type: text/plain;
>> > >> charset="Utf-8"
>> > >> Content-Transfer-Encoding: 7bit
>> > >> X-Newsreader: Microsoft CDO for Windows 2000
>> > >> Content-Class: urn:content-classes:message
>> > >> Importance: normal
>> > >> Priority: normal
>> > >> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>> > >> Newsgroups: microsoft.public.biztalk.server
>> > >> NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>> > >> Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
>> > >> Xref: cpmsftngxa10.phx.gbl microsoft.public.biztalk.server:10687
>> > >> X-Tomcat-NG: microsoft.public.biztalk.server
>> > >>
>> > >> Hi all,
>> > >>
>> > >> Recently i started receiving a SQLSERVERAGENT warning in the event
log
>> > >> (Event ID 208), with the following message:
>> > >>
>> > >> "SQL Server Scheduled Job
'MessageBox_Parts_Cleanup_BizTalkMsgBoxDb'
>> > >> (0x[GUID]) - Status: Failed - Invoked on [Date] - Message: The job
>> > failed.
>> > >> The Job was invoked by Schedule 13 (Schedule). The last step to run
was
>> > step
>> > >> 1 (Purge)."
>> > >>
>> > >> This message gets logged every minute (the job is scheduled to run
every
>> > >> minute and, of course, it fails every minute). Any idea why it
started
>> > to
>> > >> fail? What does it affect? What do i need to do to make it stop
failing?
>> > >>
>> > >> Thank you!
>> > >>
>> >
>> >
>>
- Next message: Eldar Musayev: "RE: Load balancing BT server 2004"
- Previous message: eXavier: "Re: multiple receive locations"
- In reply to: Silly_King: "RE: SQLSERVERAGENT Warning in EventLog (Event ID 208)"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
