Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / Component Services / December 2003

Tip: Looking for answers? Try searching our database.

Problem with transactions from Win2k app server to Win2k3 SQL Server

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
paul crowder - 21 Oct 2003 15:39 GMT
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] - 21 Oct 2003 20:15 GMT
Hi Paul,

The two machines are running in a domain?

Regards,
Signature

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.

> Here's my set-up:
>
[quoted text clipped - 13 lines]
>
>     Paul
Paul Crowder - 21 Oct 2003 21:01 GMT
> Hi Paul,
>
> The two machines are running in a domain?

Yes, both machines are on the same domain.

   Paul
Florin Lazar [MSFT] - 21 Oct 2003 21:38 GMT
Paul,

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

Regards,

Signature

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.

> Hi Paul,
>
> The two machines are running in a domain?

Yes, both machines are on the same domain.

   Paul
Paul Crowder - 22 Oct 2003 21:44 GMT
> 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
Lars Westholm - 23 Oct 2003 22:08 GMT
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,
> >
[quoted text clipped - 8 lines]
>
>     Paul
Pawel Smolarkiewicz - 10 Dec 2003 07:36 GMT
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

> Paul,
>
[quoted text clipped - 10 lines]
>
>     Paul
Pawel Smolarkiewicz - 10 Dec 2003 20:19 GMT
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

> Here's my set-up:
>
[quoted text clipped - 13 lines]
>
>     Paul

Rate this thread:







Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.