1. What Is Visual Studio 2008

After installing Visual Studio 2008 Service Pack 1, adding or removing features from Visual Studio may prompt for the file SQLSysClrTypes.msi with the following text:

Setup is looking for file SQLSysClrTypes.msi.
Please insert Microsoft Visual Studio Team System 2008 Team Suite – ENU disk 1 now.

Recently, I posted some instructions for creating an installable layout for Visual Studio 2008 Express Editions and silently installing the components that are a part of the Visual Studio 2008 Express Edition setups. In addition, there are some new silent installation command line switches introduced in the Visual Studio 2008 product family. I’ve heard from. INSTALLATION REQUIREMENTS a compatible version of visual studio 2008 was not detected on the system. This update is designed for only microsoft visual studio 2008(ENU) product family,and is not compatible in any express editions. What should i apply requirements can u tell me please! You can't post conmments that contain an email address.

Visual

The text will read differently depending if you have Visual Studio 2008 Professional Edition or another edition or language installed.

What Is Visual Studio 2008

Workaround

SQLSysClrTypes.msi is a product package installed with VS2008 SP1. To satisfied this prompt you’ll need to obtain that file again.

  1. Download a complete layout of VS2008 SP1 if you haven’t already.
  2. Open the directory were you copied VS2008 SP1.
  3. Right click on SQLSysClrTypes.msi and select Copy.
  4. Open an Explorer window (ex: Windows key + E) and browse to the directory where you installed Visual Studio 2008. By default this is “C:Program FilesMicrosoft Visual Studio 9.0” where C: is your system drive.
  5. Double click on the folder that corresponds to the name of the product you installed (ex: “Microsoft Visual Studio Team System 2008 Team Suite – ENU”).
  6. Right click on empty space in the window, click New, then Folder, and type “wcu” (without quotes).
  7. Double click that new “wcu” folder to open it.
  8. Right click on empty space in the window, click New, then Folder, and type “smo” (without quotes).
  9. Double click that new “smo” folder to open it.
  10. Right click on empty space in the window and click Paste.
  11. In the dialog prompt requesting SQLSysClrTypes.msi, click the Browse button.
  12. Expand folders to select the directory you opened in step 5 and click the OK button. Do not select the “wcusmo” directory you created.
  13. Click the OK button on the dialog prompt.
VisualVisual studio 2008 professional edition

On 64-bit machines you will always see this prompt when adding or removing features so it is recommended you keep this file for future use. If you are a network administrator or have the installation source copied to your hard drive, you can also create this directory in the root of the original installation source directory and the setup executable will automatically find SQLSysClrTypes.msi.

Verbose logging started: 11/24/2016 16:39:16 Build type: SHIP UNICODE 4.05.6002.00 Calling process: c:059c6da1195fa72d1037d3da892cx64setup100.exe
MSI (c) (F0:08) [16:39:16:368]: Resetting cached policy values
MSI (c) (F0:08) [16:39:16:368]: Machine policy value 'Debug' is 0
MSI (c) (F0:08) [16:39:16:368]: ******* RunEngine:
******* Product: {288D79EE-A2D1-42AF-9597-B0ADCC23A8ED}
******* Action:
******* CommandLine: **********
MSI (c) (F0:08) [16:39:16:368]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (F0:08) [16:39:16:368]: Grabbed execution mutex.
MSI (c) (F0:08) [16:39:16:368]: Cloaking enabled.
MSI (c) (F0:08) [16:39:16:368]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (F0:08) [16:39:16:368]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (78:B8) [16:39:16:384]: Running installation inside multi-package transaction {288D79EE-A2D1-42AF-9597-B0ADCC23A8ED}
MSI (s) (78:B8) [16:39:16:384]: Grabbed execution mutex.
MSI (s) (78:D0) [16:39:16:399]: Resetting cached policy values
MSI (s) (78:D0) [16:39:16:399]: Machine policy value 'Debug' is 0
MSI (s) (78:D0) [16:39:16:399]: ******* RunEngine:
******* Product: {288D79EE-A2D1-42AF-9597-B0ADCC23A8ED}
******* Action:
******* CommandLine: **********
MSI (s) (78:D0) [16:39:16:399]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (78:D0) [16:39:16:399]: SRSetRestorePoint skipped for this transaction.
MSI (s) (78:D0) [16:39:16:399]: End dialog not enabled
MSI (s) (78:D0) [16:39:16:399]: Original package > c:WindowsInstaller6a8b90.msi
MSI (s) (78:D0) [16:39:16:399]: Package we're running from > c:WindowsInstaller6a8b90.msi
MSI (s) (78:D0) [16:39:16:415]: APPCOMPAT: looking for appcompat database entry with ProductCode '{288D79EE-A2D1-42AF-9597-B0ADCC23A8ED}'.
MSI (s) (78:D0) [16:39:16:415]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (78:D0) [16:39:16:415]: MSCOREE not loaded loading copy from system32
MSI (s) (78:D0) [16:39:16:431]: File will have security applied from OpCode.
MSI (s) (78:D0) [16:39:16:431]: Original patch > c:059c6da1195fa72d1037d3da892c1033_ENU_LPx64setupx64SqlWriter.msp
MSI (s) (78:D0) [16:39:16:431]: Patch we're running from > c:WindowsInstaller6ad19222.msp
MSI (s) (78:D0) [16:39:16:431]: SOFTWARE RESTRICTION POLICY: Verifying patch --> 'c:059c6da1195fa72d1037d3da892c1033_ENU_LPx64setupx64SqlWriter.msp' against software restriction policy
MSI (s) (78:D0) [16:39:16:431]: SOFTWARE RESTRICTION POLICY: c:059c6da1195fa72d1037d3da892c1033_ENU_LPx64setupx64SqlWriter.msp has a digital signature
MSI (s) (78:D0) [16:39:46:508]: SOFTWARE RESTRICTION POLICY: c:059c6da1195fa72d1037d3da892c1033_ENU_LPx64setupx64SqlWriter.msp is permitted to run at the 'unrestricted' authorization level.
MSI (s) (78:D0) [16:39:46:508]: SequencePatches starts. Product code: {288D79EE-A2D1-42AF-9597-B0ADCC23A8ED}, Product version: 10.50.1600.1, Upgrade code: {E9031696-DD39-4C25-BAEB-425FF28279EA}, Product language 1033
MSI (s) (78:D0) [16:39:46:508]: PATCH SEQUENCER: verifying the applicability of QFE patch c:059c6da1195fa72d1037d3da892c1033_ENU_LPx64setupx64SqlWriter.msp against product code: {288D79EE-A2D1-42AF-9597-B0ADCC23A8ED}, product version: 10.50.1600.1, product language 1033 and upgrade code: {E9031696-DD39-4C25-BAEB-425FF28279EA}
MSI (s) (78:D0) [16:39:46:508]: PATCH SEQUENCER: QFE patch c:059c6da1195fa72d1037d3da892c1033_ENU_LPx64setupx64SqlWriter.msp is not applicable.
MSI (s) (78:D0) [16:39:46:508]: SequencePatches returns success.
MSI (s) (78:D0) [16:39:46:508]: Final Patch Application Order:
MSI (s) (78:D0) [16:39:46:508]: Other Patches:
MSI (s) (78:D0) [16:39:46:508]: UnknownAbsent: {8B9F68F5-8191-4F48-B6C5-4A98858642AF} - c:059c6da1195fa72d1037d3da892c1033_ENU_LPx64setupx64SqlWriter.msp
MSI (s) (78:D0) [16:39:46:508]: Product: Microsoft SQL Server VSS Writer - Update '{8B9F68F5-8191-4F48-B6C5-4A98858642AF}' could not be installed. Error code 1642. Additional information is available in the log file C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20161124_163055SQLSERVER2008SqlWriter_Cpu64_1.log.