I have a com+ component written in vb.net that is installed on a
Win2k3 server. The component reads and writes files to local or
network file path that is sent to it. I need the file that is written
to be 'locked' by the transaction so that a process on another server
cannot access it, so I have the component setup in COM+ with
Transaction.Required on, with the transaction isolation level set to
'serialized'.

Both the main server and the other server run Windows 2003 Server,
with the latest service packs.

This component is able to write the file OK when I write to a local
drive (eg. e:\myfolder) but when the component tries to write a file
to a path specified by a UNC path (e.g \\sn012345\myfolder) I get the
error:

'The partner transaction manager has disabled its support for
remote/network transactions'

I googled this error and found out that network DTC must be enabled,
so I have turned this on on both servers. I have also set the network
security settings on both servers in Component Services->My
Computer->Properties->MSDTC->Security Configuration to all be checked,
as specified in the MS articles that I found on the subject:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/troubleshooting/htm/ebiz_ops_bas_admin_khfe.asp

http://support.microsoft.com/default.aspx?scid=kb;en-us;817064&Product=winsvr2003

I have rebooted both servers, but I still get the same error.

Any help would be much appreciated!

Regards,
Andy

Hi Andy,

Are the two servers part of the same Windows domain? If not, you might need
to follow http://blogs.msdn.com/florinlazar/archive/2004/03/02/82916.aspx

Regards,
--
Florin Lazar - Microsoft - [ http://blogs.msdn.com/florinlazar ]
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.

"Andy Smith" <spamspamspam (AT) andyandleeann (DOT) com> wrote

Florin, thanks for the reply.

Just FYI for anyone else that might come across this error, I found out what
the problem was. In the UNC path I was specifying the server name, eg:

\\sn01234m1\out

instead, I tried putting the IP address in instead, eg.

\\10.120.120.99\out

and this solved the problem! It turned out to be something to do with the
routing and proxy settings on the machine - when the component tried to write
to the "server name" UNC path, the request was somehow treated as not 'local'
to the machine, so was routed elsewhere on the network, hence the 'partner
transaction manager has disabled its support for remote/network transactions'
error. When I used the IP address, the 'bypass proxy for local addresses'
thing kicked in, and the request got routed OK. (Excuse the vagueness of my
explaination, but I'm no networking expert.)

So I guess the moral of my tail is: this error message might not necessarily
indicate the exact cause of the problem - check your network and proxy
settings if all else fails!

Cheers,
Andy.


"Florin Lazar [MSFT]" wrote:

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!