Problem with instantiating a DLL that resides on a network share

I am migrating my sites fro Win2K to Win2K3 web server. My servers (in the
DMZ, of course) run IIS anonymous access under a custom local account. I have
the same account set up on the network in AD (same name and password). I also
have the same account set up as local account on the systems on my network
that I need access to from the web servers. These systems have shares that
need to be accessed by my ASP.NET applications. One of those shares contains
a DLL that my apps instantiate - all applications that use this functionality
use the same DLL.
This worked fine on Win2K IIS server, but after migrating one of the sites
to Win2K3 system I am now getting the following error:
"System.Runtime.InteropServices.COMException error was encountered!". The
DLL in question is permitted in the Web Service Extensions. Moreover, a copy
of same DLL, when placed on local machine, has no problems.
I tested access to the network share by logging onto my IIS server with the
account used for Anonymous Access, and it can see the sharte without
prompting me for username and password.
What else can I try?
--
Alexey Aksyonenko

Re: Problem with instantiating a DLL that resides on a network share

On Aug 30, 4:30 pm, Alexey Aksyonenko
wrote:
> I am migrating my sites fro Win2K to Win2K3 web server. My servers (in the
> DMZ, of course) run IIS anonymous access under a custom local account. I have
> the same account set up on the network in AD (same name and password). I also
> have the same account set up as local account on the systems on my network
> that I need access to from the web servers. These systems have shares that
> need to be accessed by my ASP.NET applications. One of those shares contains
> a DLL that my apps instantiate - all applications that use this functionality
> use the same DLL.
> This worked fine on Win2K IIS server, but after migrating one of the sites
> to Win2K3 system I am now getting the following error:
> "System.Runtime.InteropServices.COMException error was encountered!". The
> DLL in question is permitted in the Web Service Extensions. Moreover, a copy
> of same DLL, when placed on local machine, has no problems.
> I tested access to the network share by logging onto my IIS server with the
> account used for Anonymous Access, and it can see the sharte without
> prompting me for username and password.
> What else can I try?
> --
> Alexey Aksyonenko


This does not sound like an IIS6 issue. Web Service Extensions is not
needed -- it is your applications privately using the same DLL and IIS
has no knowledge of that DLL, so Web Service Extension is extraneous
and irrelevant.

It sounds like you are seeing the usual security exception with .Net
applications accessing anything over network share -- it is not
allowed. I suspect there is either a .Net security policy that you
depend on but failed to migrate to Windows Server 2003, or the .Net
framework version no longer allows that sort of remote access.

You may find better support by querying a .Net-specific newsgroup.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//