Windows Server 2008 Snap-in - fails to create.
My newly created Windows Server Standard 2008 32 bit is having problems loading snap-ins.
Lauching Server Manager I get the following error:
MMC could not create the snap-in. The snap-in might have not been installed correctly
Name: Server Manager
CLSID: FX:{18ea3f92-d6aa-41d9-a20
If I open MMC and add the Computer Manager snap in I receive the following error:
MMC cannot initialize the snap-in because the snap-in requires version v2.0.50727 of the .Net Framework and version v1.1.4322 is already loaded. To load this snap-in, start a new instance of MMC and add the snap-in to a new console.
Name: Event Viewer
CLSID: FX: {b05566ae-fe9c-4363-be05-7
Since this is Windows Server 2008 I cannot install .NET 2.0 as it is already part of the operating system, nor can I uninstall it or remove it.
I installed Version 3.5 and received the same error.
Msot of the other snap-ins have been fine, however today the Terminal Services Manager snap-in reported a similar error.
Lauching Server Manager I get the following error:
MMC could not create the snap-in. The snap-in might have not been installed correctly
Name: Server Manager
CLSID: FX:{18ea3f92-d6aa-41d9-a20
If I open MMC and add the Computer Manager snap in I receive the following error:
MMC cannot initialize the snap-in because the snap-in requires version v2.0.50727 of the .Net Framework and version v1.1.4322 is already loaded. To load this snap-in, start a new instance of MMC and add the snap-in to a new console.
Name: Event Viewer
CLSID: FX: {b05566ae-fe9c-4363-be05-7
Since this is Windows Server 2008 I cannot install .NET 2.0 as it is already part of the operating system, nor can I uninstall it or remove it.
I installed Version 3.5 and received the same error.
Msot of the other snap-ins have been fine, however today the Terminal Services Manager snap-in reported a similar error.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hmmm... was thinking of OS reinstall. However, it sounds like you may have it in production - true?
Regardless, there's gotta be a way to re-install .Net 2.0 on Windows 2008... here's one workaround I found, it's part of a bigger doc on how to get PowerShell installed on Server Core, but in it it has a workaround for installing .Net 2.0
http://dmitrysotnikov.wordpress.com/2008/05/15/powershell-on-server-core/
Regardless, there's gotta be a way to re-install .Net 2.0 on Windows 2008... here's one workaround I found, it's part of a bigger doc on how to get PowerShell installed on Server Core, but in it it has a workaround for installing .Net 2.0
http://dmitrysotnikov.wordpress.com/2008/05/15/powershell-on-server-core/
That is not an answer - and falsifies the success rates -
Thanks for your input.
The recommendation for rebuild is not a fix, per se, for the root issue - but it the affected server is "early in life", then a flatten and rebuild is the most time effective solution to the issue.
However, as this question was created back in 2009, there are a lot of addtional options for resolution, one of those including the System Update Readiness Tool that fixes some Windows Updates issues and consequentially .NET issues as seen in the original question.
The success rate could be affected by bad media, or a downloaded .ISO issue that was burned at too fast of a speed (4x and under is recommended for DVD burns).
If you're seeing this issue and it's not resolved - please create a new question and it'll get answered by the Experts.
The recommendation for rebuild is not a fix, per se, for the root issue - but it the affected server is "early in life", then a flatten and rebuild is the most time effective solution to the issue.
However, as this question was created back in 2009, there are a lot of addtional options for resolution, one of those including the System Update Readiness Tool that fixes some Windows Updates issues and consequentially .NET issues as seen in the original question.
The success rate could be affected by bad media, or a downloaded .ISO issue that was burned at too fast of a speed (4x and under is recommended for DVD burns).
If you're seeing this issue and it's not resolved - please create a new question and it'll get answered by the Experts.
ASKER
Are you suggesting that I reinstall the apps or the Operating System?