Error 2908 Visual Studio 2005
Contents |
★★★★★★★★★★★★★★★ Aaron StebnerNovember 10, 200535 0 0 0 I have heard from a couple of customers who have tried to install the final release of error 2908 could not register component Visual Studio 2005 or one of the Express Editions and have gotten 1935
Error Code 2908 Windows 7
(or 2908) errors with HRESULT values of 0x8002802F, and then setup failed and rolled back. The cases I have internal error 2908 windows 7 seen so far have had the same root cause as the problemI described in this previous blog post. In the cases I have seenfor this problem in the finalrelease of VS 2005,
Error 1935. An Error Occurred During The Installation Of Assembly Component
the machines had the .NET Framework 1.1 installed, and the version of %windir%\system32\mscoree.dll was 1.1.4322.573 or 1.1.4322.2032. WhenVS setuptried to install assemblies to the GAC, it failed because Windows Installer tried to call into a 2.0-specificAPI from mscoree.dll (needed because there are new processor architecture attributes on VS 2005 assemblies that only 2.0 knows about). Since the version of mscoree.dll on the system was fsutil resource setautoreset true c:\ 1.1, these API calls failed. This issue is described in more detail in my 1935 troubleshooting guideif you are interested. The underlying problem was that VS setup detected that the .NET Framework 2.0 was already installed and skipped that prerequisite step. However, the machine did not actually have the .NET Framework 2.0 installed, but instead only had the registry key that VS setup uses to detect whether or not the .NET Framework 2.0 is installed. I found that the machines had the following orphaned registry key/value that VS setup uses to determine that .NET Framework 2.0 was already installed: Key name: HKLM\Software\Microsoft\NET Framework Setup\NDP\v2.0.50727 Value name: MSI Data type: REG_DWORD Value data: 1 Once the customers deleted this key/value and re-ran VS 2005 setup, it detected that it needed to install the .NET Framework 2.0, and after installing that, VS setup worked perfectly. As a side note if you're really interested, you could use some of the setup reverse engineering tricks that I describe here to determine the exact location of this registry key. In this case, the key/value are listed in the [gencomp18] section of the file named baseline.dat in
★★★★★★★★★★★★★★★ Aaron StebnerNovember 10, 2004192 0 0 0 Hey all, first off I want to apologize for not posting anything in a couple of weeks. I have had a couple of mini-vacations and been
.net Framework
wrapped up with some other stuff, but I'm back now! I've been working with
Ccleaner
some Product Support folks I know to turn some documents I wrote for internal troubleshooting into knowledge base articles, and I decided that I wanted to go ahead and post some of the information here so it would be available sooner rather than later. The first installment is some detailed information about the dreaded 1935 (or https://blogs.msdn.microsoft.com/astebner/2005/11/10/vs-2005-setup-fails-with-1935-or-2908-error/ 2908) error that sometimes happens when trying to install the .NET Framework or other MSI-based products that install managed assemblies to the GAC. This is a long post, but hopefully with some useful info. Let me know if you see any scenarios not covered by this information or have any questions…. 1935 Errors in Setup Abstract The following document describes causes https://blogs.msdn.microsoft.com/astebner/2004/11/10/troubleshooting-1935-and-2908-errors-during-installation/ of 1935 errors during .NET Framework, J# redistributable package, language pack, or Visual Studio setup. It also explains how to diagnose the root cause of a 1935 error and workaround or fix the error. Introduction A 1935 error is one of the most common problems that can prevent a user from being able to install the .NET Framework, J# redistributable package, Visual Studio or any other application that uses the Windows Installer MSIAssembly and MSIAssemblyName tables to install assemblies. In general, this error means that Windows Installer encountered an error while trying to install assemblies to the Global Assembly Cache (GAC) or the Win32 GAC (WinSxS). This error is considered fatal and causes setup to fail and initiate rollback. If the setup is run in UI mode, the user will see a message box indicating that a 1935 error occurred, and it will list the HRESULT and the Windows Installer component GUID of the assembly that caused the error. If the setup is run in silent mode, the user will see no visible error. In both cases, more detailed information about the error can be found in the Windows Installer verbose log file. Affected Products · .NET Framework 1.0 · .NET Framework 1.1 · .N
we got the following problem. If any of Add-in Express for Office and .NET product packages are installed, uninstalled and re-installed for the second time, the "Error 2908″ message is shown a tremendous number of https://www.add-in-express.com/creating-addins-blog/2007/11/12/windows-installer-error-2908/ times. It is obvious that the message is shown for every file included into the package. What is worse, when the setup program is complete, you get this error again when you install or uninstall any MSI-based product. That is, from the common point of view, Windows becomes inoperable. Windows Installer Error Messages doesn't provide any useful info. If you google for "Error 2908″, you'll find out that this error occurs for a number error 2908 of applications. Workarounds exist for installing Office 2000 on Windows 98 or ME, NET Framework 1.1, Visual Studio 2005. But none of those workarounds worked for us. Then we found an interesting post on the www.eggheadcafe.com forum: they added Crystal Reports merge modules to their setup and got this error. This resulted in "reinstalling windows on computers affected with the error." What Microsoft suggested is "ask Business Objects company that produces the Crystal Report for 2908 windows 7 assistance". As you may assume, Crystal Reports supporters sent poor devils back to Microsoft. However, we googled out some vague notes that the cause of this error may relate to the number of files included into the package. This was somehow backed up by Orca that reported the following incomprehensible warning message: "Feature ‘DefaultFeature' has XXXX components. This could cause problems on Win9X systems. You should try to have fewer than 817 components per feature." To verify this assumption, we created a simple setup with some 2000 files. Nevertheless, this setup program has run through the install/uninstall/install procedure successfully. But when we added a custom action (Install, Rollback, and Uninstall), we got Error 2098 again. Moreover, it turned out that install/uninstall is enough for breaking the Windows Installer down. Then we found that the number of files that does the trick lies between 1000 and 1022. We don't know if this number depends on the number of custom actions. This research forced us to decrease the number of Add-in Express files by moving demo projects to a ZIP archive. And in this way, we overpowered Error 2908. But this was not the end of the story. We felt obliged to find a way for our customers to restore their PCs if they have got into this trap by installing Add-in Express. The solutio