Document Viewer Internal Error 2908
Contents |
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 internal error 2908 windows 7 times. It is obvious that the message is shown for every file included into the
Internal Error 2908 7d4b5591-4c80-42bb-b0e5-f2c0cee02c1a
package. What is worse, when the setup program is complete, you get this error again when you install or uninstall any MSI-based product.
Internal Error 2908 Windows Xp
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 of applications.
Internal Error 2908 Autocad
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 assistance". As error 2908 an internal error has occurred 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 solution was found by a
★★★★★★★★★★★★★★★ 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 wrapped up with https://blogs.msdn.microsoft.com/astebner/2004/11/10/troubleshooting-1935-and-2908-errors-during-installation/ some other stuff, but I'm back now! I've been working with some Product Support folks http://kb.act.com/app/answers/detail/a_id/14374/~/internal-error-2908-when-attempting-to-install-microsoft-.net-framework-1.1 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 2908) error that sometimes happens when trying error 2908 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 errors during .NET Framework, J# redistributable package, language internal error 2908 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 · Visual J# .NET redistributable 1.1 · Visual J# .NET redistributable 1.1 language packs · V
use the previous link instead. Select a product Sort by Default Summary New or Updated Description Date Updated Direction Ascending Descending Helpful search tips Find the answer to your question "Internal Error 2908" When Attempting To Install Microsoft .Net Framework 1.1 Answer ID 14374 | Updated 09/10/2016 12:00 PM During the .NET portion of installing ACT!, you receive the following error: "Internal Error 2908". This error may be followed by additional errors such as: "Error 1935 An error occurred during the installation of Assembly Microsoft Visual C version 7.0.5000.0 Public Key Token=b03f5f7f11d50a3a Culture = Neutral, file version 7.10.3052.4 HRESULT 0x800280F" This error may result from a damaged MSCOREE.dll file, or some of the companion components stored in the folder called URTTemp, the default location for the URTTemp folder is: C:\Windows\System32\URTTemp. To resolve this issue and install the Microsoft .Net Framework 1.1, you must move all files from this URTTemp folder and delete all temporary files. Follow the steps below: Launch Windows Explorer (or My Computer) and navigate to the following folder: C:\Windows\System32\URTTemp Create a new folder within URTTemp called Old (Click the File menu, point to New, and then click Folder).Cut (or drag) all files from the URTTemp folder, and then paste these into the Old folder. Be sure that the URTTemp folder is empty before you exit Windows Explorer (or My Computer). Disk Cleanup If you are using the Windows 2000 or Windows XP operating systems, you can run the Disk Cleanup utility to delete temporary files. Follow the steps below Click the Windows Start button, point to Programs, point to Accessories, point to System Tools, and then click Disk Cleanup. The Select Drive dialog box appears: Ensure that the appropriate drive is listed in the Drives field (this will normally be Local Disk (C:)), and then click OK. A Disk Cleanup dialog box appears as the amount of space you will be able to clean up is calculated: Once the system has determined the amount of space that you can free up, a Disk Cleanup for Local Disk (C:) dialog box appears: Warning: Ensure that the Compress old files option is disabled and do NOT delete Setup Log Files. ACT! is not designed to work with compressed files and synchronization issues will result if certai