|
Home > Archive > BizTalk Server > January 2007 > Failure executing the Receive Pipelines
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 |
Failure executing the Receive Pipelines
|
|
| Abdul Aziz 2007-01-24, 7:38 am |
| I encountered a problem when I drop a a text file in the HOT directory to be
process by the Receive Pipeline. The file dissappeared from the HOT drive
and the following error message was logged.
20070124121539[ERROR][BizTalk
Server][\\**.**.**. **\FileDrop\Highlander\Logs\SourceFiles\
][BizTalk Server:
W01RHGLAPP1A]There was a failure executing the receive pipeline:
"BTS.DBS.Highlander.FO.PV.Pipeline.FF_RCV" Source: "mscorlib" Receive
Location: "\\**.**.**.**\FileDrop\Highlander\FO\Inbound\PVs\*.*" Reason:
Could not find file
"\\**.**.**. **\FileDrop\Highlander\FO\Inbound\PVs\DI
VERSIFIED_001_20070123_20070124121212020
569.txt.BTS-WIP". (EVENT ID: 12588631)
20070124121610[ERROR][BizTalk
Server][\\**.**.**. **\FileDrop\Highlander\Logs\SourceFiles\
][BizTalk Server:
W01RHGLAPP1A]The Messaging Engine has suspended "1" message(s) from adapter
"FILE" due to failures in message processing. Please refer to Health and
Activity Tracking tool for more detailed information on this failure. (EVENT
ID: 12588664)
I have been running this before without any problem. What could be the
reason that it did not work this time? Besides, there was no change to the
current setup.
| |
| Jan Eliasen 2007-01-25, 7:16 am |
| On Wed, 24 Jan 2007 03:36:01 -0800, Abdul Aziz
<AbdulAziz@discussions.microsoft.com> wrote:
>I encountered a problem when I drop a a text file in the HOT directory to be
>process by the Receive Pipeline. The file dissappeared from the HOT drive
>and the following error message was logged.
>
>20070124121539[ERROR][BizTalk
>Server][\\**.**.**. **\FileDrop\Highlander\Logs\SourceFiles\
][BizTalk Server:
>W01RHGLAPP1A]There was a failure executing the receive pipeline:
>"BTS.DBS.Highlander.FO.PV.Pipeline.FF_RCV" Source: "mscorlib" Receive
>Location: "\\**.**.**.**\FileDrop\Highlander\FO\Inbound\PVs\*.*" Reason:
>Could not find file
>"\\**.**.**. **\FileDrop\Highlander\FO\Inbound\PVs\DI
VERSIFIED_001_20070123_20070124121212020
569.txt.BTS-WIP". (EVENT ID: 12588631)
>20070124121610[ERROR][BizTalk
>Server][\\**.**.**. **\FileDrop\Highlander\Logs\SourceFiles\
][BizTalk Server:
>W01RHGLAPP1A]The Messaging Engine has suspended "1" message(s) from adapter
>"FILE" due to failures in message processing. Please refer to Health and
>Activity Tracking tool for more detailed information on this failure. (EVENT
>ID: 12588664)
>
>I have been running this before without any problem. What could be the
>reason that it did not work this time? Besides, there was no change to the
>current setup.
Things to check:
1. Make sure the user running the host that your receive location is
running under has FULL rights to the fileshare - and not just
read/write
2. Try to disable your receive lcation and see if the message still
gets picked up. Perhaps some other process somewhere is also listening
for the same file folder?
--
eliasen, representing himself and not the company he works for.
Private blog: http://blog.eliasen.dk
Private email: jan@eliasen.dk
| |
| Abdul Aziz 2007-01-26, 1:23 am |
| My colleagues and I managed to find the reason for this problem. It was
because the Registry key - RenameReceivedFiles were missing. The Registry
key can be found in our other systems but not in the system that we
encountered the error. Somehow it went missing.
HKLM\System\CurrentControlSet\Services\B
TSSvc{GUID} RenameReceivedFiles
DWORD 1
This registry key rename the file before locking them for processing.
"Jan Eliasen" wrote:
> On Wed, 24 Jan 2007 03:36:01 -0800, Abdul Aziz
> <AbdulAziz@discussions.microsoft.com> wrote:
>
> Things to check:
> 1. Make sure the user running the host that your receive location is
> running under has FULL rights to the fileshare - and not just
> read/write
>
> 2. Try to disable your receive lcation and see if the message still
> gets picked up. Perhaps some other process somewhere is also listening
> for the same file folder?
>
> --
> eliasen, representing himself and not the company he works for.
>
> Private blog: http://blog.eliasen.dk
>
> Private email: jan@eliasen.dk
>
|
|
|
|
|