Dotnetfx Internal Error 2908
Contents |
★★★★★★★★★★★★★★★ 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 internal error 2908 windows 7 wrapped up with some other stuff, but I'm back now! I've been working with some internal error 2908 7d4b5591-4c80-42bb-b0e5-f2c0cee02c1a Product Support folks I know to turn some documents I wrote for internal troubleshooting into knowledge base articles, and I decided
Internal Error 2908 Windows Xp
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 2908) error
Error 2908 Could Not Register Component Windows 7
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 of 1935 error 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 · .NET Framework 1.1 language packs
would get a message saying "Internal Error 2908". http://xenomorph.net/windows/issues/dot-net-internal-error-2908/ Fix: I had .NET 1.1 installed before. Part of it remained on the system. I had to manually delete this file: C:\Windows\System32\mscoree.dll Cause: .NET uses the MSCOREE.DLL file to see if .NET is already installed. Solution found: http://blogs.msdn.com/junfeng/archive/2004/01/31/65457.aspx Home Log in Copyright © 1999-2016 XdN
ProFile Community Quicken Community (visit U.S. site) Support Intuit Canada Support QuickBooks Desktop Support QuickBooks Online Support TurboTax Support ProFile Support Quicken Support GoPayment Support http://support.intuit.ca/quickbooks/en-ca/kb/errors/error-messages/1402.html About Intuit About Intuit Canada Careers Intuit News & Press Releases Privacy Policy Intuit's Social Responsibility Contact Us Please enable JavaScript in your Web browser. To help your computer access and navigate QuickBooks Support more easily, JavaScript must be enabled in your Web browser. Learn how to enable JavaScript print Your Answer Error: error 2908 Internal Error 2908, when installing an update Error: Internal Error 2908, when installing an update Last updated: Sep 18, 2016 Article ID: SLN40581 When you try to install a QuickBooks Desktop update you see this error:"Internal Error 2908 {7D4B5591-4C80-42BB-B0E5-F2C0CEE02C1A}" Why this is happening The Microsoft .NET Framework is damaged. To resolve the issue, you must internal error 2908 uninstall and reinstall the .NET Framework. How to fix it Solution:Uninstall and reinstall the .NET FrameworkImportant: These troubleshooting steps may help resolve your issue. They focus on the Windows operating system, which is not an Intuit product. Intuit recommends that you find the expert assistance that you need by consulting your computer's manufacturer or a Windows expert to work with these steps. If the difficulty persists after performing these steps, contact your computer's manufacturer or Microsoft. Uninstall the .NET Framework: Click the Microsoft WindowsStartbutton and chooseControl Panel. Double-click theAdd or Remove Programsicon. Scroll down and selectMicrosoft .NET framework, then click theChange/Removebutton. Note:If you have multiple versions of .NET framework installed, remove all of them starting with the one at the bottom. Reinstall the.NET Framework: Insert your QuickBooks CD in the CD drive. Click theStartbutton and chooseMy Computer. Right-click the CD drive and chooseExplore. Double-click theThirdPartyfolder, and then double-click then: QuickBooks Desktop 2016 and 2017: double-click theDOTNET46folder, and then double-clickDOTNETFX46.exe. QuickBooks De