Please help!!

Our environment:  SQL Server 200, Windows Server 2003, Standard Edition,
Service Pack 1.

After deploying an orchestration using the BizTalk Deployment Wizard, we
cannot enlist it using BizTalk explorer in VS or BizTalk Administration.

When using BizTalk explorer in VS, we cannot see the Receive Location which
was supposedly installed during deployment.  When we tried to expand the
"Receive Locations" fold, we got the following error message:

Could not retrieve transport type data for Receive Location 'Receive
Location1' from config store.  Primary SSO Server '[BizTalk server name]
'
failed.  Could not import a DTC transaction.  Please check that MSDTC is
configured correctly for remote operation.  See the event lot (on computer
'[BizTalk server name]') for more details.

When we try to enlist the orchestration in BizTalk exporer anyway, we get
the following error message:
The transaction manager has disabled its supoort for remote/network
transactions.

Then we see an entry in the BizTalk server event log:
Event Type: Error
Event Source: ENTSSO
Event Category: Enterprise Single Sign-On
Event ID: 10605
Date:  5/23/2005
Time:  10:12:27 AM
User:  N/A
Computer: [BizTalk server name]
Description:
Could not import a DTC transaction. Please check that MSDTC is configured
correctly for remote operation. See documentation for details.
Error Code: 0x8004D025, The partner transaction manager has disabled its
support for remote/network transactions.

When we try to create a new receive location using BizTalk Explorer in VS,
we would see that the new name now is 'receive location2'.  We think that
one has already been created, but we couldn't retrieve it and it is not
listed in the Explorer.  We then are able to fill in info for the new
receive location, but we cannot save it.

Sorry for the long description and thanks for view.  Any help will be
appreciated.

Thanks in advance,
Yan Yi

[ Post a follow-up to this message ]

Hi,

just a suggestion but do you need to enable msdtc?
http://support.microsoft.com/?scid=...id=1444&sid=126


"MS" wrote:

> Please help!!
>
> Our environment:  SQL Server 200, Windows Server 2003, Standard Edition,
> Service Pack 1.
>
> After deploying an orchestration using the BizTalk Deployment Wizard, we
> cannot enlist it using BizTalk explorer in VS or BizTalk Administration.
>
> When using BizTalk explorer in VS, we cannot see the Receive Location whic
h
> was supposedly installed during deployment.  When we tried to expand the
> "Receive Locations" fold, we got the following error message:
>
> Could not retrieve transport type data for Receive Location 'Receive
> Location1' from config store.  Primary SSO Server '[BizTalk server nam
e]'
> failed.  Could not import a DTC transaction.  Please check that MSDTC is
> configured correctly for remote operation.  See the event lot (on computer
> '[BizTalk server name]') for more details.
>
> When we try to enlist the orchestration in BizTalk exporer anyway, we get
> the following error message:
> The transaction manager has disabled its supoort for remote/network
> transactions.
>
> Then we see an entry in the BizTalk server event log:
> Event Type: Error
> Event Source: ENTSSO
> Event Category: Enterprise Single Sign-On
> Event ID: 10605
> Date:  5/23/2005
> Time:  10:12:27 AM
> User:  N/A
> Computer: [BizTalk server name]
> Description:
> Could not import a DTC transaction. Please check that MSDTC is configured
> correctly for remote operation. See documentation for details.
>  Error Code: 0x8004D025, The partner transaction manager has disabled its
> support for remote/network transactions.
>
> When we try to create a new receive location using BizTalk Explorer in VS,
> we would see that the new name now is 'receive location2'.  We think that
> one has already been created, but we couldn't retrieve it and it is not
> listed in the Explorer.  We then are able to fill in info for the new
> receive location, but we cannot save it.
>
> Sorry for the long description and thanks for view.  Any help will be
> appreciated.
>
> Thanks in advance,
> Yan Yi
>
>
>

[ Post a follow-up to this message ]

Hi,

Sounds like there could be a permissions problem with the users and BizTalk
groups.

Are you running SQL Server on a seperate box to BizTalk?
Is the current logged on user a member of the BizTalk Administrators group?
Is the logged on user a member of the SSO Administrators group?

If you are using domain groups, you may need to add the user you log on to
access the BizTalk Admin console to the BizTalk Administrators  and SSO
Administrators groups.

Regards,

Alan




--
The Bloggers Guide to BizTalk
http://geekswithblogs.com/asmith



"MS" wrote:

> Please help!!
>
> Our environment:  SQL Server 200, Windows Server 2003, Standard Edition,
> Service Pack 1.
>
> After deploying an orchestration using the BizTalk Deployment Wizard, we
> cannot enlist it using BizTalk explorer in VS or BizTalk Administration.
>
> When using BizTalk explorer in VS, we cannot see the Receive Location whic
h
> was supposedly installed during deployment.  When we tried to expand the
> "Receive Locations" fold, we got the following error message:
>
> Could not retrieve transport type data for Receive Location 'Receive
> Location1' from config store.  Primary SSO Server '[BizTalk server nam
e]'
> failed.  Could not import a DTC transaction.  Please check that MSDTC is
> configured correctly for remote operation.  See the event lot (on computer
> '[BizTalk server name]') for more details.
>
> When we try to enlist the orchestration in BizTalk exporer anyway, we get
> the following error message:
> The transaction manager has disabled its supoort for remote/network
> transactions.
>
> Then we see an entry in the BizTalk server event log:
> Event Type: Error
> Event Source: ENTSSO
> Event Category: Enterprise Single Sign-On
> Event ID: 10605
> Date:  5/23/2005
> Time:  10:12:27 AM
> User:  N/A
> Computer: [BizTalk server name]
> Description:
> Could not import a DTC transaction. Please check that MSDTC is configured
> correctly for remote operation. See documentation for details.
>  Error Code: 0x8004D025, The partner transaction manager has disabled its
> support for remote/network transactions.
>
> When we try to create a new receive location using BizTalk Explorer in VS,
> we would see that the new name now is 'receive location2'.  We think that
> one has already been created, but we couldn't retrieve it and it is not
> listed in the Explorer.  We then are able to fill in info for the new
> receive location, but we cannot save it.
>
> Sorry for the long description and thanks for view.  Any help will be
> appreciated.
>
> Thanks in advance,
> Yan Yi
>
>
>

[ Post a follow-up to this message ]

Thank you very much for taking a look at this.  We actually got it fixed.
We enabled the DTC network access on our local machines and the problems
went away.  We have been changing the DTC settings on the remote machine but
totally forgot abut our local machines.


Thanks again

"Alan Smith" <AlanSmith@discussions.microsoft.com> wrote in message
news:541277BF-C3BB-4FDF-99CF-38D0AABEF18E@microsoft.com...[vbcol=seagreen]
> Hi,
>
> Sounds like there could be a permissions problem with the users and
> BizTalk
> groups.
>
> Are you running SQL Server on a seperate box to BizTalk?
> Is the current logged on user a member of the BizTalk Administrators
> group?
> Is the logged on user a member of the SSO Administrators group?
>
> If you are using domain groups, you may need to add the user you log on to
> access the BizTalk Admin console to the BizTalk Administrators  and SSO
> Administrators groups.
>
> Regards,
>
> Alan
>
>
>
>
> --
> The Bloggers Guide to BizTalk
> http://geekswithblogs.com/asmith
>
>
>
> "MS" wrote:
> 

[ Post a follow-up to this message ]