I had defined a send port that used the %SourceFileName% macro, and that por
t
(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 subscrib
e
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 fil
e
<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?

[ Post a follow-up to this message ]

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 p
ort
> (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 subscr
ibe
> to a receive port that used msmqt transport. got the following warning
> everytime the send port was meant to receive something from the receive po
rt:
>
> 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 interv
al
> specified for this Send Port. Details:"The FILE send adapter cannot open f
ile
> <path>\%SourceFileName% for writing. ".
>
> There were no permission issues encountered when the send port was bound t
o
> the orchestration. I changed the send port to use the %MessageID% macro, a
nd
> messages started to flow as expected.
>
> What's wrong with the %SourceFileName% picture?

[ Post a follow-up to this message ]

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

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

[ Post a follow-up to this message ]

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] 

[ Post a follow-up to this message ]