Sqlsupport.msi Download

0 views

Skip to first unread message

Suyay Escarsega

unread,

Aug 3, 2024, 11:25:27 AM8/3/24

to baunauprofbar

Ok, I'm trying to install this security patch. When I first started trying, it kept saying I can't files... I had to copy a ton of files to c:\windows\installer to even get the install wizard to pop up. I thought I had fixed it and it started installing. I got to the update progress section and then it popped up a window saying the feature you are trying to use is on a network resource is unavailable. It asked me to tell it where sqlsupport.msi is. I did... but it doesn't like it. It then says the file is not a valid installation package product for SQL Server 2008 R2.

Ok, nevermind... I think I fixed my own issue. I went to our production server and found another version of the file and gave it that file and that seemed to make it happy. Course its asking me for more files now..... heh.

We used to run into this issue in the past and we were using VBS script to fix ( -us/help/969052/how-to-restore-the-missing-windows-installer-cache-files-and-resolve-p)
Well, now there's a tool called "FixMissingMSI" from Microsoft to fix these annoying issues which is way more efficient than VBS script approach. Take a look at below
-setup-toolsuite-introduction-1-fixmissingmsi/
Hope this helps.

Ok I ran the Fix tool.... it shows me a ton of stuff that needs to be fixed... and I see "fix it" in the first column but nothing on the menu bar is enabled (everything is grayed out) .... how do I make it fix stuff?

FYI Here is the documentation for this tool.
, I didn't had any issues with this in the past. Well, they have two flavors of this tool, One for .Net3.5 and one for .Net4.5, Are you sure you got the right one? Go through the notes under section "FixMissingMSI Version 2.2" here:

I can't believe this patch is such an annoyance... should I stop it? Will it screw up my production server? I got it installed on the test server fine and didn't have any issues...it did take a long time but I always saw it moving on to different things. Its just been sitting on this one thing forever. The CPU isn't maxed out and the process still says "running" but I can't keep my prod server down this much just for a patch. ?

Totally agree, our sites are identical... as much as they can be. I am at a loss why the production site didn't go as smoothly. At least with production I didn't have all the missing MSI file stuff...

This article describes how to update or slipstream a failed installation of Microsoft SQL Server 2008 by using the latest Cumulative Update (CU) or latest Service Pack (SP). Use these instructions when you cannot install SQL Server 2008 because of a known issue in the Setup program. The SQL Server 2008 Setup hotfixes section lists the Microsoft Knowledge Base articles that describe known setup issues and explains how to obtain the latest update.

It is recommended that you update or slipstream the original SQL Server 2008 by using Service Pack 1 because Service Pack enables to update the entire product. A CU that is based on the original SQL Server 2008 release can only update the SQL Support component.

For SQL Server 2012 and later versions, you need to use /UpdateSource parameter to update your SQL Server installation files. For an example on how to do this, see How to patch SQL Server 2012 Setup with an updated setup package (using UpdateSource to get a smart setup).

When you run the original release version of SQL Server 2008 Setup, the Setup program copies itself on the local computer, and then reruns from the local copy. Therefore, if there is a later version of the support files on the computer, the Setup program will run these updated files. Therefore, you can update the SQL Server 2008 Setup support files before you run the Setup.exe file.

Starting from SQL Server 2008 Service Pack 1, you can update SQL Server 2008 by using the slipstream infrastructure. When you install Service Pack 1 by using the slipstream procedure or install to an existing SQL Server 2008 installation, an entry is created for the Service Pack in Add or Remove Programs. You can uninstall the service pack by using this entry.

To verify whether a service pack is installed correctly, run the SQL Discovery report that is available in the SQL Server 2008 Installation Center. You should see the features are version 10. n. xxxx, where n represents the service pack version. For example, 10.1. xxxx represents Service Pack 1.

If the SQL Server 2008 Setup support files are installed on the computer, you apply a CU or a hotfix to update the SQL Server 2008 Setup support files, and then rerun the Setup program from the DVD or the network share.

To determine whether the SQL Server 2008 Setup support files are installed on the computer, view the entry by using Add or Remove Programs in Control Panel in operating systems that are earlier than Windows Vista. In Windows Vista or later versions of Windows, view the entry by using Programs and Features in Control Panel. To apply a CU or a hotfix and run the Setup program, follow these steps:

If a fix is available through a hotfix, download the CU or the hotfix, and then install it on the computer by running the .exe file or by using the command line. The package detects the SQL Server 2008 Setup support files on the computer and then applies a new version of the SQLSupport.msi file.

Run the Setup program again from the DVD or from the network share. The Setup program detects that a later version of the SQLSupport.msi file is available on the computer, and the Setup program runs from the local version on the computer instead of from the DVD or network share.

If you add features to an instance that already has the database service installed through slipstreaming, the installation may fail. To work around this issue, you need to add feature by using the original SQL Server 2008 source media or upgrade the instance to SP1 and then use the slipstream infrastructure.

When you copy slipstream packages, use paths that do not contain spaces. If you specify a location that contains spaces for either /PCUSOURCE or /CUSOURCE parameters, a failure occurs with slipstream setup.

To use these methods, the administrator must obtain the updated SQL Server 2008 Setup support files by downloading the latest CU or hotfix, or service pack. For information about the Setup fixes that are included in the latest hotfix and for information about how to download the hotfix, see the SQL Server 2008 Setup hotfixes section. After you obtain the updated SQL Server 2008 Setup support files, use one of the following methods.

Run the service pack to install Setup files on the computer. You will receive a Setup Support Files dialog box if the setup support files have not been installed. You can also run the following file to install the setup support files C:\SP1\x64\setup\1033\sqlsupport.msi.

This procedure describes how to create a new source media that will slipstream the original source media and SQL Server 2008 Service Pack 1. When you create this merged drop, you can install SQL Server 2008 SP1 in a single step.

Run the following commands to copy all files (not the folders), except the Microsoft.SQL.Chainer.PackageData.dll file, in C:\SQLServer2008_FullSP1\PCU\Architecture to C:\SQLServer2008_FullSP1\Architecture to update the original files.

You shouldn't perform the slipstream procedure to apply SQL Server 2008 Service Pack 1 for the SQL Server 2008 Express edition. SQL Server 2008 Express Edition SP1 is already a merged drop. However, you can use the slipstream procedure to apply a cumulative update for the SQL Server 2008 Express edition.

Install any prerequisite components for SQL Server 2008 if they aren't already installed. Microsoft Windows Installer 4.5 must be installed. You must install the .NET Framework 2.0 SP2 for SQL Server 2008 Express Edition and the .NET Framework 3.5 SP1 for other editions. You must download the .NET Framework 3.5 SP1 from the Internet and apply the SP1 manually.

Double-click the hotfix package to install the SQL Server 2008 Setup support files. After you extract the contents of the package, the updated SQL Server 2008 Setup support files will be installed. The hotfix package will complete the installation without notifying you when it is completed. To confirm that the files are installed, view the entry by using the Add or Remove Programs item in Control Panel in operating systems that are earlier than Windows Vista. In Windows Vista or later versions of Windows, view the entry by using the Programs and Features item in Control Panel.