none
Can't install .net framework 3.5 SP1 & 2.0 SP2 on my Windows Server 2003 R2 RRS feed

  • Question

  • Hi all, I previously have problem with updates for .net framework 3.5 for my server 2003, so I follow this post

    "When you try to install an update for the .NET Framework 1.0, 1.1, 2.0, 3.0, or 3.5, you may receive Windows Update error code "0x643" or Windows Installer error code "1603" (http://support.microsoft.com/kb/923100)"

    to uninstall all the .net products, reboot and re-install again.

    So I tried the following steps:

    1. Verify the .net installed (using verification tool from http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx) and it showed I still had .net 1.1 SP1 which was successfully verified.

    2. Install .net framework 3.5 SP1 full package directly but fail:

    [11/10/12,16:31:34] Microsoft .NET Framework 2.0a: [2] Error: Installation failed for component Microsoft .NET Framework 2.0a. MSI returned error code 1603
    [11/10/12,16:31:48] WapUI: [2] DepCheck indicates Microsoft .NET Framework 2.0a is not installed.

    3. Then I install .net 2.0 SP2 but fail as well:

    [11/10/12,16:43:05] Microsoft .NET Framework 2.0a: [2] Error: Installation failed for component Microsoft .NET Framework 2.0a. MSI returned error code 1603
    [11/10/12,16:43:17] WapUI: [2] DepCheck indicates Microsoft .NET Framework 2.0a is not installed.

    4. I tried to use Add/remove Windows components to install .net 2.0. It shows that I have .net 2.0 (the box is ticked) but the size is 0.0MB. If I tried to install using windows server 2003 setup disc, it said installation is successful. So I go back to Add/remove Windows components, same screen appeared.  If I untick the box,  it said I have File Server Management, Storage Manager for SANs, File Server Resource Manager and DFS Management requires .net 2.0 and ask if I need to uninstall them as well.  Then I cancel.

    I have searched many forums but no solution for my case.  I am now very confused and frustrated.  Could anyone help me on that?  Where can I collect and upload logs?

    Thank you very much.

    Terry

    Saturday, November 10, 2012 2:05 PM

Answers

  • "Actually the WS expert also recommend the same things:"

    Then, go ahead and try sfc, if you wish.

    As far as "reinstall the OS" is to erase everything? or repair using OS setup disc?" goes. my standard procedure in such cases is to format the OS partition and reinstall on the formatted partition. I do it that way because of too many past experiences (my own and others) where just repairing left whatever was corrupt/incorrect in place and wasted my time.

    Tuesday, November 13, 2012 8:46 PM

All replies

  • By attempting to remove .NET Framework versions that come as part of your WS 2003 R2 OS, it's possible that an OS reinstall will be required.

    The repair process for embedded .NET Frameworks is here:

    http://blogs.msdn.com/b/astebner/archive/2007/03/26/how-to-repair-the-net-framework-2-0-and-3-0-on-windows-vista.aspx

    After following the repair procedure, verify .NET Framework 2.0 with this tool:

    http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx

    Run the tool with 2.0 selected, then post the last 15 lines of the tool log here.

    Sunday, November 11, 2012 2:25 PM
  • Thanks pvdg42.

    Before I proceed, I found the repair process (sfc /scannow) is for vista, is it also okay for windows server 2003 R2? I know only .net 1.1 comes as part of windows server 2003 OS.

    Thanks

    Terry

    Sunday, November 11, 2012 5:28 PM
  • The repair procedure is for embedded .NET Frameworks (i.e. frameworks that come as part of the OS).

    You say you have WS 2003 R2. WS 2003 R2 comes with .NET Framework 2.0. For clarification, see Yi Chun Chen's answer in this thread:

    http://social.msdn.microsoft.com/Forums/en/netfxsetup/thread/6f77f7f6-7365-4412-b739-02ba4142846a

    From his answer, it appears that .NET 2.0 comes with WS 2003 R2, but is not truly embedded. So, please try following his instructions to check it. However, please do NOT use the "Cleanup Tool" he links, as this tool should only be used as a last resort.

    Sunday, November 11, 2012 10:59 PM
  • Thanks pvdg42

    I have checked the his answer and confirm my server 2003 is R2 and has .net 2.0 under Add/Remove Windows Component:


    Unfortunately, I have tried the cleanup tool before as many searched results/forums quote Aaron Stebner's cleanup tools.

    So now, is it still okay for me to follow your suggestion (run sfc /scannow -> verify -> post log)?  Thanks.

    Terry

    Monday, November 12, 2012 3:35 AM
  • At this point, do only the following. Attempt to verify your .NET 2.0 with this tool:

    http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx

    Run the tool with .NET Framework 2.0 selected, then post the first 15 lines AND the last 15 lines of the tool log here.

    Monday, November 12, 2012 2:38 PM
  • Thanks pvdg42

    Actually, I have tried this verification tool but I can't select .net 2.0 as it does not let me choose:

    The result for verification of .net 1.1 SP1 is successful.

    From the log file "setupverifier_main", the first 15 lines:

    [11/10/12,16:48:50] Beginning of new SetupVerifier activity logging session
    [11/10/12,16:48:50] Activity log file location: C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\setupverifier_main_11-10-12_16.48.50.txt
    [11/10/12,16:48:50] Error log file location: C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\setupverifier_errors_11-10-12_16.48.50.txt
    [11/10/12,16:48:50] Build created on September 10, 2012
    [11/10/12,16:48:50] Detected operating system: Windows Server 2003 (x86)
    [11/10/12,16:48:50] For more information about repairing the .NET Framework, see http://support.microsoft.com/kb/2698555 and http://go.microsoft.com/fwlink/?LinkID=246062
    [11/10/12,16:48:50] Install state for .NET Framework 1.0: not installed.
    [11/10/12,16:48:50] Install state for .NET Framework 1.1: installed with service pack 1.
    [11/10/12,16:48:50] Install state for .NET Framework 2.0: not installed.
    [11/10/12,16:48:51] Install state for .NET Framework 3.0: not installed.
    [11/10/12,16:48:51] Install state for .NET Framework 3.5: not installed.
    [11/10/12,16:48:51] Install state for .NET Framework 4 Client: not installed.
    [11/10/12,16:48:51] Install state for .NET Framework 4 Full: not installed.
    [11/10/12,16:48:51] Install state for .NET Framework 4.5: not installed.
    [11/10/12,16:48:51] Windows directory: C:\WINDOWS

    Last 15 lines:

    [11/10/12,16:49:18] Key: HKLM\SYSTEM\CurrentControlSet\Services\.NET CLR Data\Performance
     Value: Open
     Expected Data: openperformancedata
     Actual Data: openperformancedata
    [11/10/12,16:49:18] Key: HKLM\SYSTEM\CurrentControlSet\Services\.NET CLR Data\Performance
     Value: Collect
     Expected Data: collectperformancedata
     Actual Data: collectperformancedata
    [11/10/12,16:49:18] Key: HKLM\SYSTEM\CurrentControlSet\Services\.NET CLR Data\Performance
     Value: Close
     Expected Data: closeperformancedata
     Actual Data: closeperformancedata
    [11/10/12,16:49:18] Key: HKLM\SYSTEM\CurrentControlSet\Services\.NET CLR Data\Performance
     Value: Library
     Expected Data: netfxperf.dll
     Actual Data: netfxperf.dll
    [11/10/12,16:49:18] Key: HKLM\SYSTEM\CurrentControlSet\Services\.NET CLR Data\Performance
     Value: Counter Types
    [11/10/12,16:49:18] Key: HKLM\SYSTEM\CurrentControlSet\Services\.NET CLR Data\Performance
     Value: Counter Names
    [11/10/12,16:49:18] Section [Registry - .NET Framework 1.1 NT and higher (Wow6432Node)] - stop parsing entries
    [11/10/12,16:49:18] Section [Files - .NET Framework netfxperf.dll] - start parsing entries
    [11/10/12,16:49:18] ***WARNING*** File C:\WINDOWS\system32\netfxperf.dll is not installed on the system
    [11/10/12,16:49:18] Section [Files - .NET Framework netfxperf.dll] - stop parsing entries
    [11/10/12,16:49:18] Verification succeeded for product .NET Framework 1.1 SP1
    [11/10/12,16:49:19] Launching process 'change user /execute' now
    [11/10/12,16:49:19] Process successfully launched. Waiting 4294967 seconds for it to complete.
    [11/10/12,16:49:19] ****ERROR**** Process 'change user /execute' exited with return code 1
    [11/10/12,16:49:19] SetupVerifier exiting with return value 0

    From log file "setupverifier_errors":

    [11/10/12,16:48:50] Beginning of new SetupVerifier error logging session
    [11/10/12,16:48:50] Activity log file location: C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\setupverifier_main_11-10-12_16.48.50.txt
    [11/10/12,16:48:50] Error log file location: C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\setupverifier_errors_11-10-12_16.48.50.txt
    [11/10/12,16:48:50] Build created on September 10, 2012
    [11/10/12,16:48:50] Detected operating system: Windows Server 2003 (x86)
    [11/10/12,16:48:50] For more information about repairing the .NET Framework, see http://support.microsoft.com/kb/2698555 and http://go.microsoft.com/fwlink/?LinkID=246062
    [11/10/12,16:48:51] Windows directory: C:\WINDOWS
    [11/10/12,16:48:51] System directory: C:\WINDOWS\system32
    [11/10/12,16:48:51] Program Files directory: C:\Program Files
    [11/10/12,16:48:51] Common Files directory: C:\Program Files\Common Files
    [11/10/12,16:49:06] ***WARNING*** File C:\WINDOWS\system32\mscoree.dll is not installed on the system
    [11/10/12,16:49:06] ***WARNING*** File C:\WINDOWS\system32\mscorier.dll is not installed on the system
    [11/10/12,16:49:06] ***WARNING*** File C:\WINDOWS\system32\mscories.dll is not installed on the system
    [11/10/12,16:49:06] ***WARNING*** File C:\WINDOWS\Microsoft.NET\Framework\NETFXSBS10.exe is not installed on the system
    [11/10/12,16:49:06] ***WARNING*** File C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\installutil.exe.config is not installed on the system
    [11/10/12,16:49:06] ***WARNING*** File C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\mscormmc.cfg is not installed on the system
    [11/10/12,16:49:06] ***WARNING*** File C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\mscormmc.dll is not installed on the system
    [11/10/12,16:49:07] ***WARNING*** File C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\regsvcs.exe.config is not installed on the system
    [11/10/12,16:49:18] ***WARNING*** File C:\WINDOWS\system32\netfxperf.dll is not installed on the system
    [11/10/12,16:49:19] ****ERROR**** Process 'change user /execute' exited with return code 1
    [11/10/12,16:49:19] SetupVerifier exiting with return value 0

    Thanks again.

    Terry

    Monday, November 12, 2012 4:31 PM
  • First, let's clarify the relationship between .NET Framework versions.

    .NET 1.1 and 2.0 are separate, unrelated entities. They install side by side on the same system, but have no impact on each other. So, whatever is going on with 1.1 has no bearing on your 2.0 issues.

    The image you provided earlier indicates (from the checkmark on .NET 2.0) that it was installed at some point. Please try this for me:

    Uncheck .NET 2.0 from your System Components, then reboot. If 2.0 is unchecked after the reboot, check it again to see if your system will attempt to reinstall it.

    Monday, November 12, 2012 5:19 PM
  • Thanks pvdg42 for your clarification.

    Actually I have tried to uncheck .net 2.0 before: (same image in my first post)

    It reminds me the components File Server Management, Storage Manager for SANs, File Server Resource Manager & DFS Management will be removed as well.

    Is it okay for me to do that? What is the consequence if my server acts as DC, File Server, Print Server, DNS Server & Application Server? Once these components are removed, how can I get them back?

    Sorry for so many questions.  Thanks again.

    Terry

    Tuesday, November 13, 2012 2:23 AM
  • If those components require .NET Framework 2.0, but it is not properly installed (if it were, it would show up in the verification tool), I wonder if they are working properly now.

    For expert advice on those other components and the ramifications of allowing them to be removed, I suggest you ask the Windows Server experts in the WS forums, here:

    http://social.technet.microsoft.com/Forums/en-us/category/windowsserver

    Tuesday, November 13, 2012 4:37 AM
  • Thanks pvdg42

    Do you mean that although I have these 4 components, they are not working properly? Actually I am afraid these 4 components will affect the File Server role and other raid settings.

    I have posted the same thing on their forum and hope someone could help.  So do you think your previous advice (sfc /scannow) still workable?

    Terry

    Tuesday, November 13, 2012 5:23 AM
  • "So do you think your previous advice (sfc /scannow) still workable?"

    I'm hesitant to recommend it in your situation because:

    a) The tool article does no mention WS 2003 and I have no WS 2003 to test with.

    b) I do not know your propensity to accept risk.

    In your situation, I'd wait for suggestions from the WS experts, and if that does not help, reinstall the OS.

    Tuesday, November 13, 2012 1:41 PM
  • Thanks pvdg42

    You mean the tool article for sfc? It said it can apply to Windows Server 2003:

    http://support.microsoft.com/kb/310747?wa=wsignin1.0

    Actually the WS expert also recommend the same things:

    http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/f953d25a-ff28-4972-9e86-67f95ee3bf8e/

    You mean "reinstall the OS" is to erase everything? or repair using OS setup disc?

    Thanks

    Terry

    Tuesday, November 13, 2012 2:57 PM
  • "Actually the WS expert also recommend the same things:"

    Then, go ahead and try sfc, if you wish.

    As far as "reinstall the OS" is to erase everything? or repair using OS setup disc?" goes. my standard procedure in such cases is to format the OS partition and reinstall on the formatted partition. I do it that way because of too many past experiences (my own and others) where just repairing left whatever was corrupt/incorrect in place and wasted my time.

    Tuesday, November 13, 2012 8:46 PM
  • Hi pvdg42

    I am sorry to say that there is not much progress since last reply.  But I would like to know how you reinstall the server OS.  Please advise whether these steps are enough:

    1. Backup the system state

    2. Downgrade the DC role to member server (by dcpromo?)

    3. Reinstall the server OS

    4. Setup raid & other softwares

    5. Restore the AD

    Thank you very much

    Terry



    • Edited by terryamk Sunday, January 13, 2013 4:01 PM
    Sunday, January 13, 2013 4:01 PM
  • As I said earlier, my "standard" approach to an OS reinstall (to be sure of a truly fresh start) is:

    " format the OS partition and reinstall on the formatted partition. I do it that way because of too many past experiences (my own and others) where just repairing left whatever was corrupt/incorrect in place and wasted my time."

    If you need expert advice specific to server OS repair/reinstall, you should ask in the Windows Server forums,here:

    http://social.technet.microsoft.com/Forums/en/category/windowsserver/

    Sunday, January 13, 2013 4:42 PM