|
Home > Archive > BizTalk Server > August 2006 > BizTalk 2006 PassThruTransmit Pipeline Failing Unexpectedly
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 |
BizTalk 2006 PassThruTransmit Pipeline Failing Unexpectedly
|
|
| Adam Beal 2006-08-10, 1:25 am |
| Our newly upgraded BTS 2006 server has been running fine for 2+ weeks now but
this morning from 11am - 11:30am I noticed about 100 errors in the event log
from many different orchestrations. They all had the same error that
basically the PassThruTransmit pipeline was failing. This cleared up at about
11:30 after a forced host instance restart. A sample event log entry is below
(very interesting looking). Has anyone this kind of thing before or know
roughly what may have happened to BizTalk?
A message sent to adapter "FILE" on send port "prtAS_Snd_AppSend_INTERIM"
with URI
" \\bizprod2\biztalkdata\AppSend\APPSEND_I
NTERIM_RECEIVE\%datetime_bts2000%.%SourceFileName%.CL4" is suspended.
Error details: There was a failure executing the send pipeline:
"Microsoft.BizTalk.DefaultPipelines.PassThruTransmit,
Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35" Source: "Unknown " Send Port:
"prtAS_Snd_AppSend_INTERIM" URI:
" \\bizprod2\biztalkdata\AppSend\APPSEND_I
NTERIM_RECEIVE\%datetime_bts2000%.%SourceFileName%.CL4"
Reason: Unable to cast COM object of type 'System.__ComObject' to interface
type 'Microsoft.BizTalk.Message.Interop.IBaseMessagePart'. This operation
failed because the QueryInterface call on the COM component for the interface
with IID '{FFF93003-75A2-450A-8A39-53120CA8D8FA}' failed due to the following
error: No such interface supported (Exception from HRESULT: 0x80004002
(E_NOINTERFACE)).
| |
| Tom Canter - Neudesic 2006-08-11, 7:23 pm |
|
Adam,
This appears to be simply that the COM call to the underlying
"C:\Program Files\Microsoft BizTalk Server 2004\BTSCommonPS.dll"
library did not execute.
There is certainly a a number of reasons that this may happen, but I'm
suspicious, was there network problems or connection problems to the
URI Specified? Review the System and Security logs on both servers
during that time frame.
Addition, make sure that Object Access auditing has Failure enabled in
your security policies on both servers, so if you have a sudden remote
file system failure, then you may increase the chances of detecting the
cause.
Tom Canter
Neudesic
| |
| Adam Beal 2006-08-15, 7:17 pm |
| Tom it looks like you were correct. There was an event immediately prior to
all of these pipeline failures where we tried to hit a web service several
times and it was timing out. Looks like our network may have just had a
"glitch" ;)
|
|
|
|
|