| Mark Thompson 2004-02-23, 7:34 pm |
|
I have this problem as well.
One possibility is a Virus Checker. Biztalk receive
functions can give up quite easily if they cant access a
file. This was actually mentioned in the BTS 2000 release
notes.
If you search http://support.microsoft.com for Biztalk
and virus there are about a dozen hits.
One of the articles explains how to alter registry
settings to increase the amount of time the receive
function waits before disabling itself.
Not sure if this is the cause fo your problem but it's
worth checking.
mark
>-----Original Message-----
>We are receiving many files that are being sent directly
to
>directories on the BizTalk server via FTP. There seems
to be a
>disconnect sporadically when the receive function
attempts to pick up
>the file. We are seeing the receive function fail every
so often.
>Here is the error from the event log:
>
>Details:
>------------------------------
>[0x1916] There was a serious failure in the receive
function
> 'FinishMaster_File_Receive_Invoice_From_
Tandem_2'. This
receive
>service will be shut down, please check the event log for
additional
>error messages.
>
>[0x80004005] Unspecified error
>
>[0x172d] The receive function
> 'FinishMaster_File_Receive_Invoice_From_
Tandem_2' has
experienced
>problems, it will be shut down and disabled. Once these
problems have
>been corrected, re-enable this receive function in
BizTalk Server
>Administration.
>
>[0x1704] There was a failure processing the
> 'FinishMaster_File_Receive_Invoice_From_
Tandem_2' receive
function.
>Check your receive function configuration in BizTalk
Server
>Administration.
>
>We either see "Unspecified error" or "The server threw an
exception".
>The only thing that I can think of is that the Receive
Function is
>trying to pick up the file before the FTP process has
been completed.
>Would this action cause this behavior in the Receive
Function. We do
>not seem to lose any data. When the it gets re-enabled
the file
>processes without issue.
>
>Any ideas would be appreciated on how to fix this.
>
>Thanks,
>Michael
>.
>
|