BizTalk Server Orchestration - problem using %SourceFileName%???

This is Interesting: Free IT Magazines  
Home > Archive > BizTalk Server Orchestration > December 2004 > problem using %SourceFileName%???





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 problem using %SourceFileName%???
biztalker

2004-12-15, 6:27 pm

I had defined a send port that used the %SourceFileName% macro, and that port
(using file transport) was originally bound to an orchestration that I had
created to test out some stuff, and everything worked fine. Later, I
undeployed the orchestration and through filters had that send port subscribe
to a receive port that used msmqt transport. got the following warning
everytime the send port was meant to receive something from the receive port:

Event Type: Warning
Event Source: BizTalk Server 2004
Event Category: BizTalk Server 2004
Event ID: 5743

Description:
The adapter failed to transmit message going to send port
<path>"\%SourceFileName%". It will be retransmitted after the retry interval
specified for this Send Port. Details:"The FILE send adapter cannot open file
<path>\%SourceFileName% for writing. ".

There were no permission issues encountered when the send port was bound to
the orchestration. I changed the send port to use the %MessageID% macro, and
messages started to flow as expected.

What's wrong with the %SourceFileName% picture?
biztalker

2004-12-15, 6:27 pm

so how do i make the %SourceFileName% macro work just using filters??

"biztalker" wrote:

> I had defined a send port that used the %SourceFileName% macro, and that port
> (using file transport) was originally bound to an orchestration that I had
> created to test out some stuff, and everything worked fine. Later, I
> undeployed the orchestration and through filters had that send port subscribe
> to a receive port that used msmqt transport. got the following warning
> everytime the send port was meant to receive something from the receive port:
>
> Event Type: Warning
> Event Source: BizTalk Server 2004
> Event Category: BizTalk Server 2004
> Event ID: 5743
>
> Description:
> The adapter failed to transmit message going to send port
> <path>"\%SourceFileName%". It will be retransmitted after the retry interval
> specified for this Send Port. Details:"The FILE send adapter cannot open file
> <path>\%SourceFileName% for writing. ".
>
> There were no permission issues encountered when the send port was bound to
> the orchestration. I changed the send port to use the %MessageID% macro, and
> messages started to flow as expected.
>
> What's wrong with the %SourceFileName% picture?

biztalker

2004-12-15, 6:27 pm

sorry, forgot to add that i figured out what was wrong in the problem scenario

"biztalker" wrote:
[vbcol=seagreen]
> so how do i make the %SourceFileName% macro work just using filters??
>
> "biztalker" wrote:
>
Greg Forsythe

2004-12-15, 6:27 pm

The %SourceFileName% macro just inserts the "FILE.ReceivedFileName" message
context property

This property is normally added to the message context on input by the file
or FTP adapter.
The MSMQT adapter does not read a file it receives a message so there is no
filename.

You can set the FILE.ReceivedFileName property inside the orchestration and
use the %SourceFileName% macro on the send port

OutputMessage(FILE.ReceivedFileName) = "myoutputfilename.xml"
or
OutputMessage(FILE.ReceivedFileName) =
OutputMessage. MyDistiguishedPropertyContainingFileName



Greg



"biztalker" <biztalker@discussions.microsoft.com> wrote in message
news:34E180A6-1E9A-41A0-BD39-9BA92DC1DAE1@microsoft.com...[vbcol=seagreen]
> so how do i make the %SourceFileName% macro work just using filters??
>
> "biztalker" wrote:
>
port[vbcol=seagreen]
had[vbcol=seagreen]
subscribe[vbcol=seagreen]
port:[vbcol=seagreen]
interval[vbcol=seagreen]
file[vbcol=seagreen]
to[vbcol=seagreen]
and[vbcol=seagreen]


Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com