exception thrown during install

microsoft.public.dotnet.framework

3 Oct 2006 2:49 PM

advantage

(This post is informational only, I don't know what the problem was,
but I found a solution - see the bottom of this post.)

Recently my framework v1.1 and v2.0 installations became unstable after
installing an update. From then on, each time I tried to repair them
or uninstall/reinstall them, regsvcs.exe threw an unhandled exception
during the install. Here's the command that fails followed by the
exception information:

Registering System.EnterpriseServices.dll
Executing: "C:\windows\microsoft.net\framework\v2.0.50727\regsvcs.exe"
/bootstrapi

Unhandled Exception: System.TypeInitializationException: The type
initializer for 'RegSvcs' threw an exception. --->
System.Security.SecurityException: That assembly does not allow
partially trusted callers.
   at
System.Security.CodeAccessSecurityEngine.ThrowSecurityException(Assembly
asm, PermissionSet granted, PermissionSet refused, RuntimeMethodHandle
rmh, SecurityAction action, Object demand, IPermission permThatFailed)
   at RegSvcs..cctor()
The action that failed was:
LinkDemand
The assembly or AppDomain that failed was:
RegSvcs, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a
The Zone of the assembly that failed was:
MyComputer
The Url of the assembly that failed was:
file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/RegSvcs.exe
   --- End of inner exception stack trace ---
   at RegSvcs.Main(String[] args)

I eventually noticed that if someone else logged into my PC and ran the
install, it worked fine for them. This led me to move my existing user
profile and create a new one. Using the new profile, the 1.1 and 2.0
framework installs worked fine as well as VS 2005 (the initial issue I
had). Having to create a new profile is a pain, but it got me up and
running again. Hopefully this information helps someone else.

Regards,
Peter