Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio
All postings are provided AS IS
with no warranties, and confer no rights. Additionally, views expressed
herein are my own and not those of my employer, Microsoft.
The .NET Framework 1.1 ships as an OS component on the 32-bit Windows Server 2003 family of operating systems. This .NET Framework component is a hidden, always-installed component with the exception of ASP.NET (which can be found as a selectable item underneath the Application Server item in the Add/Remove Windows Components control panel applet).
I have seen cases where the .NET Framework 1.1 stops working correctly on Windows Server 2003 (often due to bugs in daily builds of the .NET Framework 2.0). In those cases, it is useful to perform a repair to get the .NET Framework 1.1 back to a known good state. However, it can be difficult to figure out how to repair .NET 1.1 in these scenarios because the component is hidden and because there is some specific logic in the setup DLL that installs this component that prevents uninstall and reinstall after OS setup has completed.
In general, you can repair the .NET Framework 1.1 that ships with Windows Server 2003 by re-running OS setup and choosing to repair/reinstall, which will trigger the .NET Framework 1.1 component setup to rerun.
In addition, the following steps can be performed in order to repair the .NET Framework 1.1 on Windows Server 2003 while also avoiding the need to run a full OS reinstall:
<update date="11/1/2005"> There is a Knowledge Base article that also describes how to troubleshoot .NET Framework 1.1 installation issues on Windows Server 2003 that can be useful in this type of scenarios. You can find it at this location. </update>
<update date="9/29/2008"> Added a note about using source files with integrated service packs if the OS was originally installed with a service pack integrated. </update>
Thanks a lot for this article.
We're having serious issues with NET window forms application - they just hang if launched from task scheduler with a user that's not logged in console - on a production Windows 2003 SP2 server.
It could be related to the installation of this rollup package, in that the problems started the same day of the installation.
This is the verify log: http://www.prjteam.com/riservato/nf_fail_log.txt.
I suppose the failure is because our Windows installation is localized in Italian...
Before venturing in net framework repair, can somebody check the log and tell if the failure is real or not?
P.S. Other servers without the patch above fail the verification with the same results...
Found the error only log:
[03/06/10,18:48:05] Beginning of new SetupVerifier error logging session
[03/06/10,18:48:05] Activity log file location: C:\DOCUME~1\TS_USR~1\IMPOST~1\Temp\1\setupverifier_main_03-06-10_18.48.05.txt
[03/06/10,18:48:05] Error log file location: C:\DOCUME~1\TS_USR~1\IMPOST~1\Temp\1\setupverifier_errors_03-06-10_18.48.05.txt
[03/06/10,18:48:05] Build created on February 20, 2010
[03/06/10,18:48:05] Detected operating system: Windows Server 2003 (x86)
[03/06/10,18:48:08] File C:\WINDOWS\system32\MUI\0409\mscoreer.dll is not installed on the system
[03/06/10,18:48:08] File C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\1033\alinkui.dll is not installed on the system
[03/06/10,18:48:08] File C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\1033\cscompui.dll is not installed on the system
[03/06/10,18:48:08] File C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\1033\vbc7ui.dll is not installed on the system
[03/06/10,18:48:08] File C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\1033\Vsavb7rtUI.dll is not installed on the system
[03/06/10,18:48:08] File C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\MUI\0409\mscorsecr.dll is not installed on the system
[03/06/10,18:48:09] Key: HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v1.1.4322\1033
Actual Data: UNABLE TO OPEN REGISTRY KEY
Expected Data: 1
Actual Data: NOT FOUND
[03/06/10,18:48:09] Verification failed for product .NET Framework 1.1 SP1
Hi Mabian - All of the files and registry values that are being reported as errors in your scenario are English-specific files. If your version of Windows Server 2003 is non-English, then those errors can be safely ignored and I will need to update the verification tool accordingly.
If the problems with your application only started happening when you applied KB969612 to your system, then I'd first suggest trying to uninstall that to see if it helps before proceeding to a full repair of the .NET Framework on your system.
Hi I have installed .Net 2.0 on top of .Net 1.1 Framework in windows server 2003.
Now i want to uninstall .Net framework 2.0. What will be impact of uninstalling .Net 2.0 on .Net 1.1
Whether 1.1 Net framework will properly or not
Hi Boddu - You can safely uninstall the .NET Framework 2.0 and it will not impact the functionality of the .NET Framework 1.1 on your computer.