Problem with transactions from Win2k app server to Win2k3 SQL Server : DOTNET

Here's my set-up:

- Windows 2000 application server with serviced components registered in
Component Services
- Windows 2003 Server Standard running SQL Server 2000

Here's my problem:

I'm trying to create a transaction in my Windows 2000 .Net application which
executes a SQL statement and commits or aborts based on that statement's
success or failure. I'm getting this error message: Exception Details:
System.ApplicationException: Exception from HRESULT: 0x8004D00E. In the
past when my SQL machine was running Windows 2000, I was able to fix this by
enabling NetBIOS on that machine. This solution no longer works now that
I'm running Windows 2003. Any suggestions? TIA.

Paul

Hi Paul,

The two machines are running in a domain?

Regards,
--
Florin Lazar - Microsoft

Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.


"paul crowder" <paul.crowder@REMOVEacstechnologies.comME> wrote in message
news:%232gSWG%23lDHA.1084@tk2msftngp13.phx.gbl...
> Here's my set-up:
>
> - Windows 2000 application server with serviced components registered in
> Component Services
> - Windows 2003 Server Standard running SQL Server 2000
>
> Here's my problem:
>
> I'm trying to create a transaction in my Windows 2000 .Net application
which
> executes a SQL statement and commits or aborts based on that statement's
> success or failure. I'm getting this error message: Exception Details:
> System.ApplicationException: Exception from HRESULT: 0x8004D00E. In the
> past when my SQL machine was running Windows 2000, I was able to fix this
by
> enabling NetBIOS on that machine. This solution no longer works now that
> I'm running Windows 2003. Any suggestions? TIA.
>
> Paul
>
>
>

"Florin Lazar [MSFT]" <xwscom@online.microsoft.com> wrote in message
news:esVVyeAmDHA.2312@TK2MSFTNGP12.phx.gbl...
> Hi Paul,
>
> The two machines are running in a domain?
>

Yes, both machines are on the same domain.

Paul

Paul,

Did you enable network transactions on W2K3 server using Component Services
UI? By default they are off.

Regards,

--
Florin Lazar - Microsoft

Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.


"Paul Crowder" <paul.crowder@REMOVEacstechnologies.comME> wrote in message
news:eu5Lx6AmDHA.2364@TK2MSFTNGP11.phx.gbl...
"Florin Lazar [MSFT]" <xwscom@online.microsoft.com> wrote in message
news:esVVyeAmDHA.2312@TK2MSFTNGP12.phx.gbl...
> Hi Paul,
>
> The two machines are running in a domain?
>

Yes, both machines are on the same domain.

Paul

"Florin Lazar [MSFT]" <xwscom2@online.microsoft.com> wrote in message
news:uD57WNBmDHA.2272@tk2msftngp13.phx.gbl...
> Paul,
>
> Did you enable network transactions on W2K3 server using Component
Services
> UI? By default they are off.
>

Yes, I've turned it on. The odd thing is, there's another person in the
office running Windows 2000 that has the same problem as mine, and another
running Windows 2000 who is having no problem at all. I'm beginning to
think it's a network problem.

Paul

Hi Paul,

We are having exactly the same problem with the same setup. We spent the
whole afternoon trying to figure out what is going on and so far we have
isolated it to "probably" a network problem. Do you have any news?

Lars

"Paul Crowder" <paul.crowder@REMOVEacstechnologies.comME> wrote in message
news:ukuln3NmDHA.1740@TK2MSFTNGP12.phx.gbl...
>
> "Florin Lazar [MSFT]" <xwscom2@online.microsoft.com> wrote in message
> news:uD57WNBmDHA.2272@tk2msftngp13.phx.gbl...
> > Paul,
> >
> > Did you enable network transactions on W2K3 server using Component
> Services
> > UI? By default they are off.
> >
>
> Yes, I've turned it on. The odd thing is, there's another person in the
> office running Windows 2000 that has the same problem as mine, and another
> running Windows 2000 who is having no problem at all. I'm beginning to
> think it's a network problem.
>
> Paul
>
>

Seem to be having the same problem as well - I have spent the afternoon and
much of the night looking for a fix. I have tried all the obvious "enable
network transaction" fixes. In my case I am accessing the W2003k Sql server
by its ip, the App server (Win XP) and the Sql server are not on the same
subnet
(thought this may be important) - also they are NOT in a domain - with
transactionOption.Disabled all works fine. The network between the machines
is open, I have tested with the firewall disabled and still experience
the problem. Could it be lookup related, do I need some entries in my
LMHosts files, I havn't tried this yet? Also, when I run the DB on my laptop
(Windows XP) and same subnet as the App Server in this case everything works
fine.

Any ideas?

Thanks,
Pawel

"Florin Lazar [MSFT]" <xwscom2@online.microsoft.com> wrote in message
news:uD57WNBmDHA.2272@tk2msftngp13.phx.gbl...
> Paul,
>
> Did you enable network transactions on W2K3 server using Component
Services
> UI? By default they are off.
>
> Regards,
>
> --
> Florin Lazar - Microsoft
>
> Please do not send email directly to this alias. This alias is for
newsgroup
> purposes only.
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
>
> "Paul Crowder" <paul.crowder@REMOVEacstechnologies.comME> wrote in message
> news:eu5Lx6AmDHA.2364@TK2MSFTNGP11.phx.gbl...
> "Florin Lazar [MSFT]" <xwscom@online.microsoft.com> wrote in message
> news:esVVyeAmDHA.2312@TK2MSFTNGP12.phx.gbl...
> > Hi Paul,
> >
> > The two machines are running in a domain?
> >
>
> Yes, both machines are on the same domain.
>
> Paul
>
>
>

POSSIBLE SOLUTION:

I experienced very similar problems (HRESULT: 0x8004D00E when using a remote
SQL Server [on a different subnet, win2k3] and followed similar initial
steps as everyone else (enable Network DTC, check MSDTC security settings,
uninstall/reinstall MSDTC, reboot, ping machines, etc..), ultimately the
solution for me was to add an entry to both server and client's LMHOSTS
files to allow name resolution of each other (MSDTC seems to use the names,
not IP's for routing and my machines were on different subnets, also run
"nbtstat -R" and "nbtstat -c" after updating LMHOSTS to clear and update
name-resolution cache).

FYI, I found the DTCPing.exe utility (available from MS) very helpful to
isolate the problem and configure the firewall between the machines
correctly.

Hope this helps somebody, Cheers,
Pawel

"paul crowder" <paul.crowder@REMOVEacstechnologies.comME> wrote in message
news:%232gSWG%23lDHA.1084@tk2msftngp13.phx.gbl...
> Here's my set-up:
>
> - Windows 2000 application server with serviced components registered in
> Component Services
> - Windows 2003 Server Standard running SQL Server 2000
>
> Here's my problem:
>
> I'm trying to create a transaction in my Windows 2000 .Net application
which
> executes a SQL statement and commits or aborts based on that statement's
> success or failure. I'm getting this error message: Exception Details:
> System.ApplicationException: Exception from HRESULT: 0x8004D00E. In the
> past when my SQL machine was running Windows 2000, I was able to fix this
by
> enabling NetBIOS on that machine. This solution no longer works now that
> I'm running Windows 2003. Any suggestions? TIA.
>
> Paul
>
>
>