I'm getting this error when I try to create a recieve location. I already
have a recieve location setup that points to the same server same database.
Why can't I create another recieve location oin the same database. Here's th
e
error...

Address should be unique.

Address 'SQL://MNVORAPPBTDEV/MNCBTRD/' is already present for <Receive
Location - SQLSettings_ReceiveLocation> Refresh and try again.

How can I get around this...?


Thanks.
Dan

[ Post a follow-up to this message ]

You can not have the mutiple end points pointing to the same address, that
will cause a conflic when BTS trys to evaluate messages againest subscrbtion
in the msgbox DB,
i believe you can go around this by changing your resonse schema namespace
or something like that. however i have a question if ur executing the same
statment (SP or whatever) why don't u reuse the port previously created?

Kal


"Alien2_51" <dan.billow.remove@monacocoach.removeme.com> wrote in message
news:93D0EB35-0661-4A5A-AA85-E766A41F877F@microsoft.com...
> I'm getting this error when I try to create a recieve location. I already
> have a recieve location setup that points to the same server same
> database.
> Why can't I create another recieve location oin the same database. Here's
> the
> error...
>
> Address should be unique.
>
> Address 'SQL://MNVORAPPBTDEV/MNCBTRD/' is already present for <Receive
> Location - SQLSettings_ReceiveLocation> Refresh and try again.
>
> How can I get around this...?
>
>
> Thanks.
> Dan

[ Post a follow-up to this message ]

Hello Kal,

Thanks for your response... Please see my comments below...

"Khaled M. Hnidk" wrote:

> You can not have the mutiple end points pointing to the same address, that
> will cause a conflic when BTS trys to evaluate messages againest subscrbti
on
> in the msgbox DB,
> i believe you can go around this by changing your resonse schema namespace
> or something like that.

Would I do this using the schema designer tool in VS..?

> however i have a question if ur executing the same
> statment (SP or whatever) why don't u reuse the port previously created?

I won't be executing the same sp. I have already considered having multiple
subscribers subscribing to the same message type each performing seperate
actions, it's still only theory for me at this point. I would be wanting to
generate several different mesage types from the same SQL server database. I
haven't put much of the training or research I've done on BTS to practical
use yet but the time for that is coming soon. My company just bought
Enterprise One and we're in the middle of a large ERP implementation. There
will be much integration needed.

Thank you for your help.

Dan


>
> Kal
>
>
> "Alien2_51" <dan.billow.remove@monacocoach.removeme.com> wrote in message
> news:93D0EB35-0661-4A5A-AA85-E766A41F877F@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]

Dan,

Try editing the response schema namespace in the schema designer tool in
namespace (I always still know it as the Biztalk editor.. I am from the old
Biztalk 2000 days).

Or you may wanna generate a fresh schema using the adapter wizard (i.e. add
generated item -> adapter) and provide a different response schema name when
prompted for.

Experts, correct me i am wrong.

regards,
red

"Alien2_51" wrote:
[vbcol=seagreen]
> Hello Kal,
>
> Thanks for your response... Please see my comments below...
>
> "Khaled M. Hnidk" wrote:
> 
>
> Would I do this using the schema designer tool in VS..?
> 
>
> I won't be executing the same sp. I have already considered having multipl
e
> subscribers subscribing to the same message type each performing seperate
> actions, it's still only theory for me at this point. I would be wanting t
o
> generate several different mesage types from the same SQL server database.
 I
> haven't put much of the training or research I've done on BTS to practical
> use yet but the time for that is coming soon. My company just bought
> Enterprise One and we're in the middle of a large ERP implementation. Ther
e
> will be much integration needed.
>
> Thank you for your help.
>
> Dan
>
> 

[ Post a follow-up to this message ]

I think I'll want to generate a new schema for the different message types
I'll be retrieving from the SQL server. I copied my schema into the post
below. I generated the schema using the adapter wizard (SQL adapter). I'm a
little confused when you say response schema, what are you referring to here
?
Can you describe the change needed using this schema assuming that the
message attributes will be different for each message type...?

Thanks for your help!!

Dan

<?xml version="1.0" encoding="utf-16" ?>
- <xs:schema xmlns:b="http://schemas.microsoft.com/BizTalk/2003"
attributeFormDefault="unqualified" elementFormDefault="qualified"
targetNamespace="http://SQLSettingsRecieve" version="1.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
- <xs:annotation>
- <xs:appinfo>
<msbtssql:sqlScript value="exec [esp_Settings_Messages_Get]"
xmlns:msbtssql="http://schemas.microsoft.com/BizTalk/2003" />
</xs:appinfo>
</xs:annotation>
- <xs:element name="InRootName">
- <xs:complexType>
- <xs:sequence>
<xs:element xmlns:q1="http://SQLSettingsRecieve" minOccurs="0"
maxOccurs="unbounded" name="Settings_Messages"
type="q1:Settings_MessagesType" />
</xs:sequence>
</xs:complexType>
</xs:element>
- <xs:complexType name="Settings_MessagesType">
<xs:attribute name="id" type="xs:int" />
<xs:attribute name="name" type="xs:string" />
<xs:attribute name="description" type="xs:string" />
<xs:attribute name="createddate" type="xs:string" />
<xs:attribute name="createdby" type="xs:string" />
</xs:complexType>
</xs:schema>

"red" wrote:
[vbcol=seagreen]
> Dan,
>
> Try editing the response schema namespace in the schema designer tool in
> namespace (I always still know it as the Biztalk editor.. I am from the ol
d
> Biztalk 2000 days).
>
> Or you may wanna generate a fresh schema using the adapter wizard (i.e. ad
d
> generated item -> adapter) and provide a different response schema name wh
en
> prompted for.
>
> Experts, correct me i am wrong.
>
> regards,
> red
>
> "Alien2_51" wrote:
> 

[ Post a follow-up to this message ]