Error Code 2755 on Uninstall w/ Call DLL

[skibbs]

I was wondering if anyone has encountered an error while uninstalling an application that uses a custom call DLL action in their uninstall.

My Call DLL successfully executes and calls a Win32 DLL that loads a .NET DLL through COM that pops up a GUI Wizard, this all works fine and the uninstall seems to go great but at the end an error dialog pops up,

"Error

The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2755."
<OK>

The application does not get uninstalled either.

Is there a way to suppress this unexpected error message? Is it acceptable to call DLLs while uninstalling?

Thanks!

[Tinus]

Is it acceptable to call DLLs while uninstalling?

I call a DLL 2 times on uninstall before Apply Uninstall is called. No problem.

Can you try to put the custom DLL into the $SUPPORTDIR$ folder?

[MichaelNesmith]

This error has nothing to do with Call DLL. Its a regular Windows Installer error, which can be looked up in MSDN documentation. Feel free to use Call DLL anywhere in your script.

However, the error description on MSDN doesn't seem to be of much help:

Server returned unexpected error [2] attempting to install package [3].

Just a wild guess - if you did a lot of uninstalls and reinstalls of a changing package with the same product and revision codes, this might have confused MSI and lead to the above. In that case, use the attached msizap tool, and try again.

Its always best to test setup packages on clean machines (such as VMware), or if you are testing natively, make sure that InstallAware is changing the revision code every time you do a new build, and that you let the automatic uninstalls of the old version proceed normally.

Windows Installer's registry for a product can become corrupt under a variety of circumstances, please see:
http://support.microsoft.com/default.as ... -us;290301

If, on the other hand, this is an error that happens even on clean machines, then my guess is that one of your commands which take effect on uninstall has some wrong settings/parameters (one of the purple Windows Installer commands, not anything like Call DLL). In that case, log the setup when uninstalling; that should provide detailed information.

File Attached:

msicuu2.exe