Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Windows Installer (C#) error code 2869

I have a project, in VS 2005, which has a console application and a setup project associated to install the application. I also have an installer class in the console application that the setup project will use to do some validation before installation. Those tasks are checking the database connection string and checking some directory locations to make sure they exist prior to installation.

I am getting an error code of 2869 when I try to install the application. All the code is written in C#. I have googled for this error code on Windows XP, but only found articles that deal with Vista and Windows 7. Any ideas what might be happening? Is there a workaround?

like image 362
Skadoosh Avatar asked Apr 12 '10 15:04

Skadoosh


People also ask

What is the C :\ Windows Installer?

The C:\Windows\Installer folder contains Windows installer cache, it's used to store important files for applications installed using the Windows Installer technology and should not be deleted. The installer cache is used to maintain (remove / update) the applications and patches installed on the computer.

What is C :\ Windows Installer \$ PatchCache $\ managed?

After your computer applies a Windows patch, the patch file along with other files related to the installation are cached in the hidden system folder C:\Windows\Installer\$PatchCache$. The files in this cache are mainly used to roll the system back when a patch is uninstalled.

How do I clean the C Windows Installer folder?

Step 2: Input the command “rmdir /s /q C:\Windows\Installer” in the prompted Command Prompt and hit Enter to execute it. Then the C:\Windows\Installer directory and folder will be deleted.

Can I delete C :\ Windows WinSxS?

Deleting files from the WinSxS folder or deleting the entire WinSxS folder may severely damage your system so that your PC might not boot and make it impossible to update.


1 Answers

This won't help with fixing the installer code, but just in case this happens to anyone when doing in install on a Windows 2008 Server you probably need to run the installer from an elevated command prompt:

  1. Open a command prompt with Run As Administrator and then run the installer
  2. msiexec /i installer.msi
like image 119
Jason Massey Avatar answered Oct 14 '22 19:10

Jason Massey