01-30-04 06:34 PM
So what is the actual problem? I do not understand what you mean by
"ASP.net MSI executables" at all.
Frequently, only Administrators have the privilege to be able to install a
MSI file. On a per-machine basis, you can configure MSI to allow
non-Administrators to be able to install a MSI file. This part really has
nothing to do with ASP.Net nor IIS.
As for the MMC Snapin UI -- only Administrator can view that (on IIS5 there
is also a curious concept called "Server Operators" which can also view
limited operations in the MMC Snapin UI).
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"rodney" <rodney.barnesanonymous@ky.gov> wrote in message
news:762701c3e756$bb189520$a401280a@phx.gbl...
I am try to set up and allow a Visual Source safe 6.o
librarian staff (non - Server admin level user) to execute
ASP.net MSI executables on a IIS 5.0 web server. I get an
error that says path not found when they try to execute
the program and point to the location of where the content
should go. I get this even when I elevate the user access
level to "Power user" with load device and driver security
policies. When I run the MSI (as the server
administrator, it loads correctly. The user with Power
user status can load other programs, etc. just nothing
that need the IIS constructs that allow functionally like
seeing the IIS MMC snap-in with Virtual sites and or
directories displayed. The ASP.net MSI once executed,
looks for the default web sites home directory via Port
HTTP/80 location. As an administrator, access is granted
and the content is pushed to the correct directory. This
is not the case for a non-administrator.
Any help would be greatly appreciated:-).
[ Post a follow-up to this message ]
|