I am trying to set up a ftp site location, place 4 different files in the
folder and set up a convoy that waits for all four files from the specific
ftp folder.  I set up a correlation as Legacy.FilePath and set the
subscription in the receive shape filter as 'legacy.filepath exists'.  WHen 
I
run the orchestration the files all are read in however they are suspended i
n
HAT with a routing failure.  Is Legacy.FilePath supposed to allow me to do
what I am trying to do?  Should I be provided specific detail as to the
FilePath?

[ Post a follow-up to this message ]

Hello.

I do not know off hand what the Legacy.FileName property relates to.

I think you have some other options available to set up your convoy.

You can take a look at one of your suspended messages in HAT.  View the
message context and see what properties are available for use.  Look for
items that say Promoted = “true”, otherwise you have to promote them you
rself
in a pipeline.

You could start off with using BTS.InboundTransportLocation or
BTS.InboundTransportType just to get it working.  Then, you can narrow down
the convoy as needed.  I do not know if all 4 messages are the same type or
what type of convoy you are using.

If you have additional questions please let me know.

Stephen W. Thomas
http://www.geekswithblogs.net/sthomas


"Hank Sumner" wrote:

> I am trying to set up a ftp site location, place 4 different files in the
> folder and set up a convoy that waits for all four files from the specific
> ftp folder.  I set up a correlation as Legacy.FilePath and set the
> subscription in the receive shape filter as 'legacy.filepath exists'.  WHe
n I
> run the orchestration the files all are read in however they are suspended
 in
> HAT with a routing failure.  Is Legacy.FilePath supposed to allow me to do
> what I am trying to do?  Should I be provided specific detail as to the
> FilePath?

[ Post a follow-up to this message ]

Thanks Stephen,  I used the BTS.InboundTransportType="FTP" and apparently it
started working.  3 out of 4 messages look like they are handled  However no
w
I'm getting a the following message regarding the one that isn't working
"CorrelationViolationException: Failed to initialize the correlation
property name: UserName namespace:
http://schemas.microsoft.com/BizTal.../ftp-properties from message:
MsgSUNSTARWire.

at Microsoft.XLANGs.Core.Correlation.InitializeFromMsg(XLANGMessage msg,
XlangStore store)"
T
Any Ideas
Thanks for your help.
Hank

"Stephen W. Thomas" wrote:
[vbcol=seagreen]
> Hello.
>
> I do not know off hand what the Legacy.FileName property relates to.
>
> I think you have some other options available to set up your convoy.
>
> You can take a look at one of your suspended messages in HAT.  View the
> message context and see what properties are available for use.  Look for
> items that say Promoted = “true”, otherwise you have to promote them y
ourself
> in a pipeline.
>
> You could start off with using BTS.InboundTransportLocation or
> BTS.InboundTransportType just to get it working.  Then, you can narrow dow
n
> the convoy as needed.  I do not know if all 4 messages are the same type o
r
> what type of convoy you are using.
>
> If you have additional questions please let me know.
>
> Stephen W. Thomas
> http://www.geekswithblogs.net/sthomas
>
>
> "Hank Sumner" wrote:
> 

[ Post a follow-up to this message ]

Hello.

Good to hear you have it somewhat working.

It seems strange that it works on 3 of the 4.

Are you trying to access or set that property someplace else?

It sounds like this value is Promoted inside the schema and not getting set
in by the adapter.  You might want to check the schema and make sure you are
not promoting/accessing this value and do not mean to.
Or, maybe try looking at the Correlation Type.  Just to make sure it isn’t
looking for something else you do not want.

Just some thoughts.

If all else fails, you can email me the solution and I can take a look at it
.

Stephen W. Thomas
http://www.geekswithblogs.net/sthomas


"Hank Sumner" wrote:
[vbcol=seagreen]
> Thanks Stephen,  I used the BTS.InboundTransportType="FTP" and apparently 
it
> started working.  3 out of 4 messages look like they are handled  However 
now
> I'm getting a the following message regarding the one that isn't working
> "CorrelationViolationException: Failed to initialize the correlation
> property name: UserName namespace:
> http://schemas.microsoft.com/BizTal.../ftp-properties from message:
> MsgSUNSTARWire.
>
>    at Microsoft.XLANGs.Core.Correlation.InitializeFromMsg(XLANGMessage msg
,
> XlangStore store)"
> T
> Any Ideas
> Thanks for your help.
> Hank
>
> "Stephen W. Thomas" wrote:
> 

[ Post a follow-up to this message ]

Stephen,
Thanks for your response.  The only property I was subscribing to was the
bts.inboundtransaporttype = "FTP".  I don't see anywhere in the schema a
reference to properties that I am mistakenly using.

I've taken a different approach now and I'm trying to implement a
non-uniform sequential convoy.  This should work as I'm receiving all the
files concurrently from a single source. I set this up using one receive por
t
with 4 request operations.  I set up one correlation which is activated on
the first  recieve.  The others reference the correlation set in the
'Following Correlation Set' property.

I've bound the single port to the orchestration and I identify the
different file types as separate locations within the port each with their
own pipeline.  When I do this the files all end up in the same instance in
HAT however the solution is suspended without any further details.

When I look in the event viewer it gets ugly:
See the following:
-----------------------------------------------------------------
Failed while creating a WiresSUNSTARProject.Orchestration_1 service.

Exception type: ServiceCreationException
Source:
Target Site:
Help Link:
Additional error information:

The parameter is incorrect.

Exception type: ArgumentException
Source: Microsoft.XLANGs.BizTalk.Engine
Target Site: Int32 GetCapabilities(System.Guid ByRef)
Help Link:
Additional error information:

Is there anything obviously wrong here?
Thanks for your help.
regards,
Hank


"Stephen W. Thomas" wrote:
[vbcol=seagreen]
> Hello.
>
> Good to hear you have it somewhat working.
>
> It seems strange that it works on 3 of the 4.
>
> Are you trying to access or set that property someplace else?
>
> It sounds like this value is Promoted inside the schema and not getting se
t
> in by the adapter.  You might want to check the schema and make sure you a
re
> not promoting/accessing this value and do not mean to.
> Or, maybe try looking at the Correlation Type.  Just to make sure it isn�
�t
> looking for something else you do not want.
>
> Just some thoughts.
>
> If all else fails, you can email me the solution and I can take a look at 
it.
>
> Stephen W. Thomas
> http://www.geekswithblogs.net/sthomas
>
>
> "Hank Sumner" wrote:
> 

[ Post a follow-up to this message ]

Hank,

Well, I have never seen that behavior before.

It sounds like you are doing everything correct on the Convoy side.

Are you able to check Orchestration Debugging in HAT and see what shape in
the Orchestration it is getting this exception at?

This is the 2nd strange problem you have had.  Was this a fresh installation
of BizTalk 2004 with all the hot fixes and rollup installed?  Is it possible
something else is messing things up?  You might want to try getting someone
else sample and testing it to make sure it works on your computer.  Might be
off track, but it is just a thought.

Stephen W. Thomas
http://www.geekswithblogs.net/sthomas



"Hank Sumner" wrote:
[vbcol=seagreen]
> Stephen,
> Thanks for your response.  The only property I was subscribing to was the
> bts.inboundtransaporttype = "FTP".  I don't see anywhere in the schema a
> reference to properties that I am mistakenly using.
>
> I've taken a different approach now and I'm trying to implement a
> non-uniform sequential convoy.  This should work as I'm receiving all the
> files concurrently from a single source. I set this up using one receive p
ort
> with 4 request operations.  I set up one correlation which is activated on
> the first  recieve.  The others reference the correlation set in the
> 'Following Correlation Set' property.
>
>  I've bound the single port to the orchestration and I identify the
> different file types as separate locations within the port each with their
> own pipeline.  When I do this the files all end up in the same instance in
> HAT however the solution is suspended without any further details.
>
> When I look in the event viewer it gets ugly:
> See the following:
> -----------------------------------------------------------------
> Failed while creating a WiresSUNSTARProject.Orchestration_1 service.
>
> Exception type: ServiceCreationException
> Source:
> Target Site:
> Help Link:
> Additional error information:
>
> The parameter is incorrect.
>
> Exception type: ArgumentException
> Source: Microsoft.XLANGs.BizTalk.Engine
> Target Site: Int32 GetCapabilities(System.Guid ByRef)
> Help Link:
> Additional error information:
>
> Is there anything obviously wrong here?
> Thanks for your help.
> regards,
> Hank
>
>
> "Stephen W. Thomas" wrote:
> 

[ Post a follow-up to this message ]

Stephen,
How can I tell if I have the hotfixes etc?

"Stephen W. Thomas" wrote:
[vbcol=seagreen]
> Hank,
>
> Well, I have never seen that behavior before.
>
> It sounds like you are doing everything correct on the Convoy side.
>
> Are you able to check Orchestration Debugging in HAT and see what shape in
> the Orchestration it is getting this exception at?
>
> This is the 2nd strange problem you have had.  Was this a fresh installati
on
> of BizTalk 2004 with all the hot fixes and rollup installed?  Is it possib
le
> something else is messing things up?  You might want to try getting someon
e
> else sample and testing it to make sure it works on your computer.  Might 
be
> off track, but it is just a thought.
>
> Stephen W. Thomas
> http://www.geekswithblogs.net/sthomas
>
>
>
> "Hank Sumner" wrote:
> 

[ Post a follow-up to this message ]

Hello.

You should be able to see the BizTalk Hotfixes if you go to Add/Remove
Programs.  They will look like this: Microsoft BizTalk Server 2004 Hotfix �
�
(KB837168).

Stephen W. Thomas
http://www.geekswithblogs.net/sthomas


"Hank Sumner" wrote:
[vbcol=seagreen]
> Stephen,
> How can I tell if I have the hotfixes etc?
>
> "Stephen W. Thomas" wrote:
> 

[ Post a follow-up to this message ]

Stephen:
Thanks for your help.  I found out what the problem is.  The properties need
to be promoted in the schemas that are referenced in the pipelines.  In
theses cases the properties are external to the actual data so they have to
be imported.  In the schemas properties the biztalk\promote properties
section allows you to add the bts, ftp soap etc property schemas into the
schema.  property schemas exist for numerous options in
references\microsoft.globalpropertyschemas.  After you do so, apparently
these details are promoted into the message and available for resolving
subscriptions.

I imported bts.bts_system_properties, bts_end_properties and
ftp.bts_ftp_properties.  I'm not yet sure which one has what I needed for my
subscription (BTS.InboundTransportType == "FTP"), but one of them did the
trick.

One other thing I found out is that a Non-Uniform Sequential convoy really
does need the source to enforce the order.  If all the imported files are in
the source locations currently, there is no assurance that they will be take
n
in the right order.  In this case, a parallel is the best solution.

Thanks again for your help and comraderie.
best regards,
Hank

"Stephen W. Thomas" wrote:
[vbcol=seagreen]
> Hello.
>
> You should be able to see the BizTalk Hotfixes if you go to Add/Remove
> Programs.  They will look like this: Microsoft BizTalk Server 2004 Hotfix 
–
> (KB837168).
>
> Stephen W. Thomas
> http://www.geekswithblogs.net/sthomas
>
>
> "Hank Sumner" wrote:
> 

[ Post a follow-up to this message ]