Microsoft.BizTalk.DefaultPipelines.XMLReceive
(1)
Microsoft.BizTalk.DefaultPipelines
(1)
BizTalk
(1)
PublicKeyToken
(1)
Stefan
(1)
Disassembler
(1)
Increments
(1)
Remarks
(1)

Receive location errors

Asked By Jeff
10-Nov-09 08:58 AM
I have started getting the following errors on 2 receive locations:

There was a failure executing the receive pipeline:
Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35" Source: "XML disassembler" Receive Port:
component has thrown an exception.


The path(s) given are the folders where BizTalk picks up XML files (both
folders are on different machines on the network). Sometimes the errors are
severe enough that the receive location shuts down. Oddly enough it seems to
run in 15 minute increments (the batch of warnings and errors on this), but
at different times of the day. I have removed virus scanning from these folders
and all BizTalk executables.  I have also checked the event logs for the
machines in question to no avail. Any thoughts?

More info, the above error is usually followed by this:An unhandled win32

Jeff replied to Jeff
12-Nov-09 09:30 AM
More info, the above error is usually followed by this:

An unhandled win32 exception occurred in BTSNTSvc.exe [4072]. Just-In-Time
debugging this exception failed with the following error: Debugger could not
be started because no user is logged on.

Any ideas on this? Thanks in advance.

Hi Jeff,Why are you using a path containing a C$ ?

Stefan[www.itsconsulting.fr] replied to Jeff
12-Nov-09 01:24 PM
Hi Jeff,

Why are you using a path containing a C$ ?
Few remarks :
- storing data in System drive is not a good practice at all ! if for
any reason the drive get filled then you are stuck
- I guess that the BizTalk User is Administrator of your B3App
otherwise, the user might not access the C$

Why do not you use the adress of the sharing folder, in your case it
might look like
\\B3App\B3ExportService\BizTalk\
or just
\\B3App\BizTalk\
You share your folder, and you give the BizTalk User the rights to
connect and have full Access on the Directory.

If the server or the network are for some reason not available then
the receive location is disabled after several retries, you could
modify the number of retries to make it live longer. The distant
server B3App, might not be available because of a reboot for
instance !

Take care,
Stefan
http://www.itsconsulting.fr
http://www.elbeb.com
Post Question To EggHeadCafe