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
[quoted text, click to view] "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
>
>
>