Net Framework 3.0 Sp1 Setup Error
3.5 installation error caused by orphaned registry value ★★★★★★★★★★★★★★★ Aaron StebnerJune 24, 20087 Share 0 0 Recently, I heard from a customer who could not get the .NET Framework 2.0 SP1 to install correctly on their system, and I wanted to explain the issue and how we were eventually able to resolve it in case anyone else runs into a similar issue in the future. Description of the issue The customer was able to successfully install the .NET Framework 1.1 and the original version of the .NET Framework 2.0. However, when they launched the .NET Framework 2.0 SP1 installer, it allowed them to accept the license agreement, and then briefly showed the progress page before transitioning to a blank error page that looks like the following: This error dialog is obviously not very helpful, and to complicate matters, there are not any errors reported in the .NET Framework 2.0 SP1 log files that are created in this scenario. I had the customer use these steps to gather a list of installed products, and it did not list the .NET Framework 2.0 SP1, and the information in the application event log seemed to indicate that setup had not even attempted to install the 2.0 SP1 MSI. Root cause of this issue for the .NET Framework 2.0 SP1 Eventually I discovered that there was an orphaned registry value on the system that was causing .NET Framework 2.0 SP1 setup to get confused and think that the product was already installed, even though the MSI was not actually installed on the system. Once I discovered this issue, I was able to reproduce it on my test machine. This is the exact registry value that causes this issue during .NET Framework 2.0 SP1 setup: On x86 systems: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v2.0.50727]Version On x64 and ia64 systems: [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\NET Framework Setup\NDP\v2.0.50727]Version How to resolve this issue for the .NET Framework 2.0 SP1 Here are the steps that can be used to resolve this issue if you encounter it during .NET Framework 2.0 SP1 setup: Click on the Start menu, choose Run, type cmd and click OK Run this command: reg delete "HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v2.0.50727" /v Version /f Run this command: reg delete "HKLM\SOFTWARE\Wow6432Node\Microsoft\NET Framework Setup\NDP\v2.0.50727" /v Version /f Try again to download and install the .NET Framework 2.0 SP1 from here for x86, from here for x64 or
and 3.5 installation failures related to the ServiceModelReg.exe custom action ★★★★★★★★★★★★★★★ Aaron StebnerMarch 28, 200816 Share 0 0 I often get questions from fellow employees or customers who find my blog regarding how to troubleshoot .NET Framework installation errors. I want to outline the process that I use to narrow down one of the most common errors that I see that can cause the .NET Framework 3.0, the .NET Framework 3.0 SP1 or the .NET Framework 3.5 to fail in the hopes that it will help some folks who read this post in the future be able to narrow down https://blogs.msdn.microsoft.com/astebner/2008/06/24/strange-net-framework-2-0-sp1-3-0-sp1-and-3-5-installation-error-caused-by-orphaned-registry-value/ and resolve this issue on their system if they encounter it. This particular error occurs when a custom action that runs an EXE named ServiceModelReg.exe during .NET Framework 3.0 setup fails. This custom action is inside of the Windows Communication Foundation (WCF) MSI in the .NET Framework 3.0, and it also is run during .NET Framework 3.5 setup because the .NET Framework 3.5 requires the .NET Framework 3.0 SP1 https://blogs.msdn.microsoft.com/astebner/2008/03/28/steps-i-use-to-diagnose-net-framework-3-0-and-3-5-installation-failures-related-to-the-servicemodelreg-exe-custom-action/ as a prerequisite. I use the following process to narrow down the root cause of the error and attempt to identify useful workarounds: Step 1 - Find the exact component that is failing I start the investigation process by looking at the .NET Framework 3.0 setup log files or the .NET Framework 3.5 setup log files, depending on what setup is failing. If the error occurs during .NET Framework 3.0 setup, the main .NET Framework 3.0 setup error log file (named %temp%\dd_dotnetfx3error.txt) will show an error like the following in this case: [03/25/08,11:11:11] Windows Communication Foundation: [2] Error: Installation failed for component Windows Communication Foundation. MSI returned error code 1603 If the error occurs during .NET Framework 3.5 setup, then the main .NET Framework 3.5 setup error log file (named %temp%\dd_dotnetfx35error.txt) will show an error like the following in this case: [03/25/08,11:11:11] Microsoft .NET Framework 3.0a: [2] Error: Installation failed for component Microsoft .NET Framework 3.0a. MSI returned error code 1603 Step 2 - Find the verbose MSI log for the failing component From here, I proceed to locate the verbose MSI log file for the specific component that is failing. As I described in this blog post, the .NET Framework 3.0 and 3.5 installers crea
Windows XP and Server 2003 if the Print Spooler is not started ★★★★★★★★★★★★★★★ Aaron StebnerDecember 19, 20079 Share 0 0 I just noticed this https://blogs.msdn.microsoft.com/astebner/2007/12/19/net-framework-3-0-and-3-5-setup-can-fail-on-windows-xp-and-server-2003-if-the-print-spooler-is-not-started/ post on Aaron Ruckman's blog and wanted to link to it here to help raise visibility. Description of this issue There is an issue in the XPS component that is a https://www.youtube.com/watch?v=1dUxYcwGtws prerequisite for the .NET Framework 3.0, 3.0 SP1 and 3.5 that can cause each of these versions of the .NET Framework to fail to install on Windows XP and Windows Server net framework 2003. The XPS component can fail to install correctly if the Print Spooler service is not running on the system, and that in turn will cause the .NET Framework 3.0 or 3.5 setup to fail. In most cases of this error that we've seen so far, an Visual C++ runtime error dialog appears during .NET Framework 3.0, 3.0 SP1 or 3.5 setup with net framework 3.0 the following text on it: The application has requested the Runtime to terminate it in an unusual way. This error usually occurs while the PrintFilterPipelineSvc.exe process is being run during the installation of the XPS component that is a prerequisite for the .NET Framework 3.0, 3.0 SP1 and 3.5 on Windows XP and Windows Server 2003 operating systems. We have not yet heard of a case of this particular error affecting Windows Vista or later operating systems because the necessary XPS components are already present as a part of the OS, and therefore .NET Framework setup does not need to run PrintFilterPipelineSvc.exe. How to work around this issue If you are running into this issue on Windows XP and Windows Server 2003, you can resolve it by doing the following: Click on the Start menu, choose Run, type services.msc and click OK In the Services snap-in, locate the service named Print Spooler, right-click on it and choose Start Note - if the Print Spooler service is already started and you are still seeing failures during .NET Framework 3.0 or 3.5 setup, then you are not running into
Επιλέξτε τη γλώσσα σας. Κλείσιμο Μάθετε περισσότερα View this message in English Το YouTube εμφανίζεται στα Ελληνικά. Μπορείτε να αλλάξετε αυτή την προτίμηση παρακάτω. Learn more You're viewing YouTube in Greek. You can change this preference below. Κλείσιμο Ναι, θέλω να τη κρατήσω Αναίρεση Κλείσιμο Αυτό το βίντεο δεν είναι διαθέσιμο. Ουρά παρακολούθησηςΟυράΟυρά παρακολούθησηςΟυρά Κατάργηση όλωνΑποσύνδεση Φόρτωση... Ουρά παρακολούθησης Ουρά __count__/__total__ How to solve NET Framework 3.5 Installation Error(Doing it live ) Make Knowledge Free ΕγγραφήΕγγραφήκατεΚατάργηση εγγραφής40.57340 χιλ. Φόρτωση... Φόρτωση... Σε λειτουργία... Προσθήκη σε... Θέλετε να το δείτε ξανά αργότερα; Συνδεθείτε για να προσθέσετε το βίντεο σε playlist. Σύνδεση Κοινή χρήση Περισσότερα Αναφορά Θέλετε να αναφέρετε το βίντεο; Συνδεθείτε για να αναφέρετε ακατάλληλο περιεχόμενο. Σύνδεση Μεταγραφή Στατιστικά στοιχεία 115.644 προβολές 239 Σας αρέσει αυτό το βίντεο; Συνδεθείτε για να μετρήσει η άποψή σας. Σύνδεση 240 86 Δεν σας αρέσει αυτό το βίντεο; Συνδεθείτε για να μετρήσει η άποψή σας. Σύνδεση 87 Φόρτ