.NET Framework 1.1 Configuration won't launch

15 Feb 2005 7:53 PM

Bryan Linton

I get the following error when trying to launch the .NET Framework 1.1
Configuration Snap-in:

    Snap-in failed to initialize.
        Name:.Net Framework 1.1 Configuration
        CLSID:{1270E004-F895-42BE-8070-DF90D60CBB75}

Clicking 'OK' on the message box allows the MMC to start, which displays the
following message:

        Snap-in Creation Failed.
    The snap-in is not created, it may not be installed properly.

If I open an MMC console and try to manually add the .NET Framework 1.1
Configuration snap-in, the MMC hangs when I select the snap-in from the list
of Available Standalone Snap-ins and click "Add". The MMC must be killed
with Task Manager.

I'm running Windows XP SP2. It's a new Dell Optiplex that came
preconfigured with .NET Framework 1.1 eight weeks ago, but our domain has a
GPO that installs .NET framework 1.1 on client workstations. This resulted
in the .NET Framework appearing twice in Add/Remove programs. I couldn't be
sure which resulted from the GPO, so I uninstalled one, and had to remove
the other entry via the registry. Then I rebooted so the GPO would
reinstall the .NET Framework. It shows installed, but will not run. The
relevant registry key reports that my .NET 1.1 SP level is SP1. No programs
that rely on the .NET framwork will run.

Any help appreciated.

Thanks,

Bryan

15 Mar 2005 6:41 PM

Kenneth

Did you find a solution? I am having the same problem. Thanks.

17 Mar 2005 2:46 PM

Rixxx Caxxx

Hi! I am experiencing the same problem. Have you found the solution? I
would appreciate it a lot if somebody could contact me by e mail and
tell me how to solve it.

thanks

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

7 Apr 2005 1:28 PM

Matt M via DotNetMonster.com

I managed to cause this error to happen by accidentally modifying the Code
Group Properties on the All_Code code group to require a strong name - now
any .Net code that is not signed will not run - this includes the .NET
Framework 1.1 Configuration application!

If anyone knows a way around this I'd be grateful to hear it...
matt_is_a_muppet[at]hotmailDOTcom

--
Message posted via http://www.dotnetmonster.com

7 Apr 2005 1:53 PM

Matt M via DotNetMonster.com

Well my problem was solved by replacing my Enterprisesec.config file with
the Enterprisesec.config.old file (the previous version). The article that
tells you where to locate this (and all the other security configuration
files) is here: http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/cpguide/html/cpconsecurityconfigurationfiles.asp

although the article that got me started in the right direction was here:
http://www.error-bank.com/microsoft.public.dotnet.security/0b6501c3c3e9
$8c4ae260$a401280a@phx.gbl_Thread.aspx

Caspol.exe is the command line version of Code Access Security Policy Tool
which you are accessing via the .NET
Framework 1.1 Configuration application

--
Message posted via http://www.dotnetmonster.com