RE: Distributed Transactions in .NET 2.0 on WIN XP SP2 & WIN2K3 SP
- From: Rodrigo García <RodrigoGarca@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 16 Jan 2006 01:42:01 -0800
Hi.
Do you have guest accounts enabled on both machines?, they have to be
enabled for the DTCs to communicate correctly.
Did you try to use another DTC in one of the machines (i.e. to use the W2003
DTC in the WIN XP machine instead of using the local one or vice-versa).
I don't know if you tried that. Good luck.
"RashmiN" wrote:
> Is any body there...
> I have seen this problem on many posts but no solution helped.
> I would be good if Microsoft can comment on this.
>
>
>
> "RashmiN" ने लिखा:
>
> > Hi,
> >
> > I used TransactionScope Object in .NET 2.0 on WIN XP SP2.
> > My web site is hosted on WIN XP SP2 and SQL 2000 SP4 DATABASE on WIN 2003
> > Server SP1.
> >
> > The TransactionScope object fails, when i run the code.
> >
> > I siwtched off the FIREWALL. Changed the RPC and MSDTC Registry Key settings
> > as suggested on Microsoft site for WIN XP SP2 and WINDOWS 2003 Server SP1.
> > I used a tool MSDTCPing.exe to test the MSDTC communication between 2
> > machines. (Tool available on Internet)
> > The result was it FAILED.
> >
> > The Output was XP was able to Invoke the RPC method on WIN2K3. BUT inreturn
> > the WIN2K3 server was not able to REVERS BIND to the RPC call.
> >
> > Now since WIN2k3 was unable to invoke RPC method on XP.
> > so i tested the RPC functionality on my machine, using RPCDump.exe tool
> > provided by Microsoft.
> > The default protocol sequence used by RPC was ncacn_ip_tcp.
> > On running the tool this protocol sequence on XP showed ACCESS_DENIED.
> > Whereas on WIN2K3 there was no ACCESS_DENIED message.
> > copying the part of output below , as recieved on XP
> > ------------------------------------------------------------------------
> > ncacn_ip_tcp(Connection-oriented TCP/IP)
> >
> > 192.0.0.67[1153] [906b0ce0-c70b-1067-b317-00dd010662da] :ACCESS_DENIED
> >
> > 192.0.0.67[1153] [906b0ce0-c70b-1067-b317-00dd010662da] :ACCESS_DENIED
> >
> > 192.0.0.67[1153] [906b0ce0-c70b-1067-b317-00dd010662da] :NO
> >
> > 192.0.0.67[1153] [906b0ce0-c70b-1067-b317-00dd010662da] :ACCESS_DENIED
> >
> > 192.0.0.67[1025] [bfa951d1-2f0e-11d3-bfd1-00c04fa3490a] :ACCESS_DENIED
> >
> > 192.0.0.67[1025] [8cfb5d70-31a4-11cf-a7d8-00805f48a135] :ACCESS_DENIED
> >
> > 192.0.0.67[1025] [82ad4280-036b-11cf-972c-00aa006887b0] :ACCESS_DENIED
> >
> > 192.0.0.67[1160] [75687379-aaaa-44f6-9512-080ac70f8ad9] TraceServer
> > :ACCESS_DENIED
> >
> > This appears unusual to me, but not sure where is the exact problem and how
> > to FIX it.
> >
> > It appears to be the problem with basic RPC and MSDTC calls.
> >
> > Please help.
> >
> > This problem appeared after installing WIN XP SP2 and WIN2k03 SP1.
> >
> > Thanks.
> > Rashmi
> >
.
- Prev by Date: Re: ClickOnce Publishing errors
- Next by Date: Re: Effect of ensureSecurity parameter
- Previous by thread: ClickOnce Publishing errors
- Next by thread: Re: Effect of ensureSecurity parameter
- Index(es):
Relevant Pages
|
