Solved: Suggestions To Fix Error 2908 Error Interno Office 2007

Recommended: Fortect

Here are some simple methods that can help you resolve your 2908 error interno office 2007 error.

Posted on Monday, November 12, 2007, every 9.20 am by Andrey Smolin.

Only one of our test PCs (Web VS) with the 2008 Beta connected running Windows XP had allthe following problems. If any of the Office Express and .NET Cream add-in packages are installed, uninstalled, but reinstalled a second time, you will see this Error 2908 message very often. It seems like common sense that a message is displayed in support of every file that is in the location. To make matters worse, after the build program finishes, you will get this error again when installing and uninstalling your MSI based product. This usually means that Windows will become unusable in its usual location. Windows technical error messages do not contain simple information.

If you do a Google search for “Error 2908”, you will find that a number of applications may encounter this error. There are workarounds for installing Office 2000 related to Windows 98 or NET me, Framework 1.1, Visual Studio 2005. But I doubt any of these workarounds helped anyone.

Then we found an interesting article attached to the www.eggheadcafe.com forum: You added Crystal Reports merge modules to your setup and got this error. This was done when reinstalling Windows on error-damaged computers y. Microsoft suggested to them “Ask Business Objects that a Crystal report was created for help.” As you might guess, the Crystal Reports contributors fired the poor fellow at Microsoft.

However, we at Google have been looking for strange evidence that the cause of this error may be related to the number of files in the software package. This was somehow provided by Orca’s simple message about the following obscure warning message: “Feature ‘DefaultFeature” contains XXXX components. This can cause problems with Win9X systems. You should try to create a function with less than 817 components. €

To test this hypothesis, we created a simple installation with some 2000 files. However, this installation of the program boasts that it goes through an install / uninstall / install process. But when we added the traditional repair action (install and uninstall), we got error 2098 again. In addition, it turned out that the program was enough during installation / uninstallation to completely destroy the Windows Installer. Then we found that the number of files that the key executes is between 1000 and 1022. We don’t know ifwhether this number depends on the number of popular promotions.

This investigation forced us to reduce this number of Add-in Express files because – the demo projects were moved to a ZIP archive. This is how we got rid of error 2908.

But this, of course, is not the end of the story. We were forced to find a way for our customers to restore their Si PCs, which they immediately fell into this trap by installing the Express add-on.

Removing the following key will restore Windows Installer properties:

Recommended: Fortect

Are you tired of your computer running slowly? Is it riddled with viruses and malware? Fear not, my friend, for Fortect is here to save the day! This powerful tool is designed to diagnose and repair all manner of Windows issues, while also boosting performance, optimizing memory, and keeping your PC running like new. So don't wait any longer - download Fortect today!

1. Download and install Fortect

2. Open the program and click "Scan"

3. Click "Repair" to start the repair process

 HKEY_LOCAL_MACHINE  SOFTWARE  Microsoft  Windows  CurrentVersion nInstaller  UserData  S-1-5-21-1123561945-1935655697-1060284298-1003 nComponents  AD95649F068525549B26938D7D18FEA7 

We do not yet know who created this key: restoring Office and all versions of the .NET Framework on a PC will not restore the main one. We currently think it is necessary to create a Visual Studio 2008 Beta 2 key. We do not know what kind of failure can occur when removing this key in the software used on most PCs.

Why do we think the director is suspicious? The registry usually consists of the following branches:

I also recommend switchingI’m on S-1-5-18 as ShortSID, but also on S-1-5-21-1409082233-343818398-725345543-1004 as LongSID.

Our experiments have shown that all products installed for all users are installed in the ShortSID / Products branch. As a result, products created for the current user only fall under the LongSID / Products branch. For each file in the install job, we have an entry in the component branch. This entry contains the most recent registry value, the name of which ultimately refers to the product entry in the Products section, the exact branch. Hope you can understand 🙂

The above key looks suspicious for the following reasons:
First, it is in the LongSID / Components branch (your computer’s Windows registry value is (B3414A45B4B628042B8446B35265C1BC), but there is no product to reconcile in the LongSID / Products branch.

Second, the value of this Windows registry entry contains a question mark or colon in the sidewalk: C? WINDOWS system32 rgbr9rast_2.dll

We tried this erase key and it helped too. Finally, we tried to generate this key on a clean PC and reproduce bug 2908 using the author’s test setup project.

For Exception:
1. It took the developers 1 X 4 days to fix an issue that we know for sure was not human-caused.
2. Any developer can create an installed project that can rationally render Windows unusable.
3. This is unreasonably attributed to the developer.

Update:
Thanks to Gabe’s comment, another simple thought: it looks like an unknown key could be generated if everyone updates the .NET Framework 2.0 (I’m pretty sure the VS Beta 2 installer is up to date). this is). We’re sorry we didn’t try to reproduce the app. It needs to be installed for training. Run the installer from where you originally installed some application. “The bug was reported by Gabe.

For a while I came across a message that just said to delete keys with values ​​”C?” with lets you install F #.

But all this is very sad, yes, after this article I posted all the necessary information in the Microsoft newsgroup; it was already November 2007, not yet 🙁

Fehler 2908 Fehler Interno Office 2007
Erro 2908 Erro Interno Office 2007
Fout 2908 Fout Interno Office 2007
Fel 2908 Fel Interno Office 2007
오류 2908 오류 내부 사무실 2007
Errore 2908 Errore Interno Office 2007
Erreur 2908 Erreur Interno Office 2007
Blad 2908 Blad Interno Office 2007
Oshibka 2908 Oshibka Interno Office 2007
Error 2908 Error Interno Oficina 2007

Justin Fernando

Related posts:

Best Way To Fix Ddeopen Macro Error No Refx Nexus Content Fix Tips Found The Best Way To Troubleshoot Typewriter Problems Repair Suggestions For Buscar La Verdad Del Error