Something very strange is going on.  Two different errors are happening that
may be related.  The first error that was recognized occured while trying to
modify the send pipeline for a send port that exists on a development server
.
The error is "Failed to enlist in a distributed transaction", and occured
when I tried to apply, or OK the port in Biztalk Explorer.

I have since verified this only happens when the send port uses SQL
transport and only if the machine I attempt to configure the port for is on 
a
remote machine.  That is to say, I can confgure a local servers port using
SQL adapter with the  exact settings as the one that fails on a remote
machine.

After spending about 3 hours attempting to figure out exactly why this is
occuring, with no luck, I decided to mitigate the problem by configuring the
port and using BTSDeploy IMPORT to import the bindings.  This is when the
second symptom manifested.  I cannot import a binding file either through
BTSDeploy or the Deploy wizard.  I get the following error:

"Failed updating binding information. BindingException: Could not validate
TransportTypeData or Address properties for Primary Transport of Send Port
'SendPort1'. Exception from HRESULT: 0x80131500."

There are no curcumstances in which I am able to get this to work, I am now
"Dead in the water"  with no way to configure a remote port, unless,
possibly, I install VS on the remote server, this is not an option in a
production environment of course.

I appreciate any prompt attention to this error, and if this is somehow new
to the group, I might have to open a ticket.  Please help.

[ Post a follow-up to this message ]

Chris,

The first step is to verify that DTCping can work from both servers. Please
search for DTCping utility from the web or microsoft site. Follow the
instructions and verify that your servers can
see each other (i.e can do RPC ping and reverse RPC ping) with the DTCping
utility.

First,  you may have issues with Firewall. In this case, you need to search
for "BizTalk And Firewall" on Microsoft site and that should give you a list
of Firewall ports that you
must open in order for your Servers or workstations to work together across
common Distributed Transactions if a firewall exist between the servers.

Secondly, you may have a name resolution issues. You need to also verify
that each server can see ping each other by name and by IP address.

Third, if you are working from a workstation, you may simply point your
workstation at the Server's DTC. Search for how to configure DTC on
Microsoft site.

I hope all these will help you. Please let me know if you need additional
help.


Anthony O.


"ChrisTucker" <ChrisTucker@discussions.microsoft.com> wrote in message
news:EAA6367D-022C-4EC9-9610-0E13C8E5B63D@microsoft.com...
> Something very strange is going on.  Two different errors are happening
that
> may be related.  The first error that was recognized occured while trying
to
> modify the send pipeline for a send port that exists on a development
server.
>  The error is "Failed to enlist in a distributed transaction", and occured
> when I tried to apply, or OK the port in Biztalk Explorer.
>
> I have since verified this only happens when the send port uses SQL
> transport and only if the machine I attempt to configure the port for is
on a
> remote machine.  That is to say, I can confgure a local servers port using
> SQL adapter with the  exact settings as the one that fails on a remote
> machine.
>
> After spending about 3 hours attempting to figure out exactly why this is
> occuring, with no luck, I decided to mitigate the problem by configuring
the
> port and using BTSDeploy IMPORT to import the bindings.  This is when the
> second symptom manifested.  I cannot import a binding file either through
> BTSDeploy or the Deploy wizard.  I get the following error:
>
> "Failed updating binding information. BindingException: Could not validate
> TransportTypeData or Address properties for Primary Transport of Send Port
> 'SendPort1'. Exception from HRESULT: 0x80131500."
>
> There are no curcumstances in which I am able to get this to work, I am
now
> "Dead in the water"  with no way to configure a remote port, unless,
> possibly, I install VS on the remote server, this is not an option in a
> production environment of course.
>
> I appreciate any prompt attention to this error, and if this is somehow
new
> to the group, I might have to open a ticket.  Please help.

[ Post a follow-up to this message ]