none
SQL Server Setup Error: This action is only valid for products that are currently installed

    Question

  • Hi board,

    after two days of desperate trial and error I decided to finally give up and ask for some professional help. We need to install SQL Server 2008 Mananagement studio on our client PCs to access a newly installed SQL Server 2008 machine.

    At first, setup wouldn't even start because there were registry leftovers from an earlier installation of the trial version. I removed these entries manually, then setup would at least start.

    Then, it complained that visual studio 2008 was not updated to Service Pack 1. I couldn't apply Service Pack 1 and had to completely uninstall and reinstall Visual Studio. At least, I could then apply Service Pack 1.

    Now, however, the SQL Server 2008 setup aborts while preparing the setup files with the following error message:

    SQL Server Setup has encountered the following error:
    This action is only valid for products that are currently installed.

    It doesn't say which product is missing or give any further information what the problem might be. I am stuck ...

    Your help is greatly appretiated!

    Thank you very much

    - spitfire_ch

    Friday, April 30, 2010 4:09 PM

All replies

  • Installation process check

    1. Download and run the SSME installer from http://www.microsoft.com/downloads/details.aspx?familyid=08e52ac2-1d62-45f6-9a4a-4b76a8564a2b&displaylang=en
    2. Click Installation on the left side of the the wizard.
    3. Select "New SQL Server stand-alone installation or add features to an existing installation". Click OK.
    4. On the Setup Support Files page, select Install.
    5. On the Setup Support Rules page, click Next (the Windows Firewall warning is ok).
    6. On the Installation Type page of the wizard, select "Perform a new installation of SQL Server 2008", then click Next. (I realize that this is counter-intuitive, but if you select "Add features to an existing instance of SQL Server 2008", you will be met with a greyed out pre-selected option to install the SQL Client Connectivity SDK, and you will not even see an option to install "Management Tools - Basic".) You will see that SQLEXPRESS is recognized as an installed instance.
    7. The Product Key screen is all greyed out with the "Specify a free edition" selected. Click Next.
    8. Agree to the License Terms as usual. Click Next.
    9. On the Feature Selection page, you will FINALLY have a blank checkbox next to "Management Tools - Basic". Put a check in that box. SQL Client Connectivity SDK is selected and greyed out by default; so is the install location. Click Next.
    10. Click Next on the Disk Space Requirements screen.
    11. Check both boxes to send error info to Microsoft if you wish. I usually do so that they can make the product better. :-) Click Next.
    12. Click Next on Installation Rules page if your system passed.
    13. Click Install on the Ready to Install page.
    14. Hopefully you will see a "Management Tools - Basic Success" message on the Installation Progress page of the wizard. Click Next.
    15. You should see a "Your SQL Server 2008 installation completed successfully" message on the Complete page. Click Close.

    or

    Make sure the computer has plenty of free hard drive space
    Install .NET 3.5
    Install Windows Installer 4.5
    Install Windows PowerShell, available here:

    http://www.microsoft.com/windowsserver2003/technologies/management/powershell/download.mspx

    Install SQL Server 2008 Express. I used the executable en_sql_server_2008_express_sp1_x86.exe, downloaded from

    http://www.microsoft.com/downLoads/details.aspx?familyid=01AF61E6-2F63-4291-BCAD-FD500F6027FF&displaylang=en.

    Note: Be aware that the installer interface is extremely complex and can be confusing. Just take your time with it.
    Note: I got a cryptic error during the installation, and to fix it I had to uncompress the C:\Program Files\Microsoft SQL Server directory.

    Install SQL Management Studio. I used the executable SQLManagementStudio_x86_ENU.exe, downloaded from

    http://www.microsoft.com/downloads/details.aspx?FamilyID=08E52AC2-1D62-45F6-9A4A-4B76A8564A2B&displaylang=en

    Important note: When the installer asks if this is a new install or an update of a previous install, specify a new install, even though this is not really true.
    When the installer presents the list of available features, select "Management Tools - Basic" and complete the installation

     

    Saturday, May 01, 2010 12:33 PM
  • Sekhara, thanks a lot for your reply. I will try that. Is the express version of Management Studio somehow restricted? We are running the enterprise edition of Sql Server 2008 64 bit on our server. I just need to access (and manage) it from my office PC. So is it ok to install the express edition on my office PC - or will I lack important features to manage the server?

    Regards

    - spitfire

    Saturday, May 01, 2010 3:40 PM
  • Hi Sekhara,

    I tried to install SQL Server 2008 ManagementStudio as you suggested, but again got the same error during setup. It crashes somewhere during the step "Setup Support Files" with this message:

    SQL Server Setup has encountered the following error:
    This action is only valid for products that are currently installed.

    I checked the install logs and found the following:

    Exception type: System.ComponentModel.Win32Exception
        Message:
            Dieser Vorgang ist nur für Produkte gültig, die zurzeit installiert sind.
           
        Data:
          DisableWatson = true
        Stack:
            at Microsoft.SqlServer.Chainer.Infrastructure.MsiNativeMethodHelpers.GetInstalledSummaryInformationStringProperty(ServiceContainer context, String productCode, SummaryInformationStreamPropertySet propertyId)
            at Microsoft.SqlServer.Configuration.SetupExtension.MsiInstallEngineActionBehavior.ModifyAction(String installedProductCode, String installedProductVersion, String pathOfPackageOnMedia, InstallAction pkgAction)
            at Microsoft.SqlServer.Configuration.SetupExtension.MSIInstallerEngine.InstallPackage(PackageId pkg, InstallAction pkgAction)
            at Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallAction.Execute(String actionId, TextWriter errorStream)
            at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
            at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)

    This, however, still doesn't tell me what is missing, or does it?

    I also tried removing all corrupt registry entries using CCCleaner, uninstall all traces of SQL-Server 2008 using Your Uninstaller and Total Uninstall ... all to no avail.

    It seems, the setup routine is expecting something on my machine, which is not there. Of course, the error message has to be cryptic and can't simply tell me what's missing :(

    If you or someone else has any idea, it would be greatly appreciated!

    Best regards

    - spitfire

    P.S. The link to PowerShel http://www.microsoft.com/windowsserver2003/technologies/management/powershell/download.mspx

    is not valid anymore. I found various other versions of powershell, but am unsure which one I would need:

    http://blogs.msdn.com/powershell/pages/download-windows-powershell.aspx

    Could Powershell be the compononent that's missing?

     

    Monday, May 03, 2010 10:23 AM
  • I found a more detailed error report, but still, my knowledge isn't deep enough to be able to interpret it:

     

     12:07:49 Slp: Running Action: MsiTimingAction
    2010-05-03 12:07:49 Slp: ----------------------------------------------------------------------
    2010-05-03 12:07:49 Slp: Running Action: Install_WatsonX86_Cpu32_Action
    2010-05-03 12:07:49 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
    2010-05-03 12:07:49 Slp: Sco: Attempting to open registry subkey
    2010-05-03 12:07:49 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\VisualStudio\9.0
    2010-05-03 12:07:49 Slp: Sco: Attempting to get registry value InstallDir
    2010-05-03 12:07:49 Slp: Error: Action "Install_WatsonX86_Cpu32_Action" threw an exception during execution.
    2010-05-03 12:07:49 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Dieser Vorgang ist nur für Produkte gültig, die zurzeit installiert sind.
    2010-05-03 12:07:49 Slp:  ---> System.ComponentModel.Win32Exception: Dieser Vorgang ist nur für Produkte gültig, die zurzeit installiert sind.
    2010-05-03 12:07:49 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.MsiNativeMethodHelpers.GetInstalledSummaryInformationStringProperty(ServiceContainer context, String productCode, SummaryInformationStreamPropertySet propertyId)
    2010-05-03 12:07:49 Slp:    at Microsoft.SqlServer.Configuration.SetupExtension.MsiInstallEngineActionBehavior.ModifyAction(String installedProductCode, String installedProductVersion, String pathOfPackageOnMedia, InstallAction pkgAction)
    2010-05-03 12:07:49 Slp:    at Microsoft.SqlServer.Configuration.SetupExtension.MSIInstallerEngine.InstallPackage(PackageId pkg, InstallAction pkgAction)
    2010-05-03 12:07:49 Slp:    at Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallAction.Execute(String actionId, TextWriter errorStream)
    2010-05-03 12:07:49 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
    2010-05-03 12:07:49 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
    2010-05-03 12:07:49 Slp:    --- End of inner exception stack trace ---
    2010-05-03 12:07:49 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
    2010-05-03 12:07:49 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()Error: Action "MsiTimingAction" threw an exception during execution.
    2010-05-03 12:07:49 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Dieser Vorgang ist nur für Produkte gültig, die zurzeit installiert sind.
    2010-05-03 12:07:49 Slp:  ---> System.ComponentModel.Win32Exception: Dieser Vorgang ist nur für Produkte gültig, die zurzeit installiert sind.
    2010-05-03 12:07:49 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.MsiNativeMethodHelpers.GetInstalledSummaryInformationStringProperty(ServiceContainer context, String productCode, SummaryInformationStreamPropertySet propertyId)
    2010-05-03 12:07:49 Slp:    at Microsoft.SqlServer.Configuration.SetupExtension.MsiInstallEngineActionBehavior.ModifyAction(String installedProductCode, String installedProductVersion, String pathOfPackageOnMedia, InstallAction pkgAction)
    2010-05-03 12:07:49 Slp:    at Microsoft.SqlServer.Configuration.SetupExtension.MSIInstallerEngine.InstallPackage(PackageId pkg, InstallAction pkgAction)
    2010-05-03 12:07:49 Slp:    at Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallAction.Execute(String actionId, TextWriter errorStream)
    2010-05-03 12:07:49 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
    2010-05-03 12:07:49 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
    2010-05-03 12:07:49 Slp:    --- End of inner exception stack trace ---
    2010-05-03 12:07:49 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
    2010-05-03 12:07:50 Slp: Received request to add the following file to Watson reporting: C:\Dokumente und Einstellungen\helfer_h\Lokale Einstellungen\Temp\tmpDB.tmp
    2010-05-03 12:07:50 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
    2010-05-03 12:07:50 Slp: Inner exceptions are being indented
    2010-05-03 12:07:50 Slp:
    2010-05-03 12:07:50 Slp: Exception type: System.ComponentModel.Win32Exception
    2010-05-03 12:07:50 Slp:     Message:
    2010-05-03 12:07:50 Slp:         Dieser Vorgang ist nur für Produkte gültig, die zurzeit installiert sind.
    2010-05-03 12:07:50 Slp:        
    2010-05-03 12:07:50 Slp:     Stack:
    2010-05-03 12:07:50 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.MsiNativeMethodHelpers.GetInstalledSummaryInformationStringProperty(ServiceContainer context, String productCode, SummaryInformationStreamPropertySet propertyId)
    2010-05-03 12:07:50 Slp:         at Microsoft.SqlServer.Configuration.SetupExtension.MsiInstallEngineActionBehavior.ModifyAction(String installedProductCode, String installedProductVersion, String pathOfPackageOnMedia, InstallAction pkgAction)
    2010-05-03 12:07:50 Slp:         at Microsoft.SqlServer.Configuration.SetupExtension.MSIInstallerEngine.InstallPackage(PackageId pkg, InstallAction pkgAction)
    2010-05-03 12:07:50 Slp:         at Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallAction.Execute(String actionId, TextWriter errorStream)
    2010-05-03 12:07:50 Slp:         at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
    2010-05-03 12:07:50 Slp:         at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
    2010-05-03 12:07:52 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Programme\Microsoft SQL Server\100\Setup Bootstrap\Log\20100503_120650\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
    2010-05-03 12:07:52 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Programme\Microsoft SQL Server\100\Setup Bootstrap\Log\20100503_120650\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
    2010-05-03 12:07:52 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Programme\Microsoft SQL Server\100\Setup Bootstrap\Log\20100503_120650\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
    2010-05-03 12:07:54 Slp: Dieser Vorgang ist nur für Produkte gültig, die zurzeit installiert sind.

    2010-05-03 12:07:55 Slp: Watson bucket for exception based failure has been created
    2010-05-03 12:07:55 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
    2010-05-03 12:07:55 Slp: Sco: Attempting to open registry subkey
    2010-05-03 12:07:55 Slp: Sco: Attempting to open registry subkey Software\Microsoft\PCHealth\ErrorReporting\DW\Installed
    2010-05-03 12:07:55 Slp: Sco: Attempting to get registry value DW0200
    2010-05-03 12:09:04 Slp: Submitted 1 of 1 failures to the Watson data repository
    2010-05-03 12:09:04 Slp:
    2010-05-03 12:09:04 Slp: ----------------------------------------------------------------------
    2010-05-03 12:09:04 Slp:
    2010-05-03 12:09:04 Slp: Error result: 1570409569
    2010-05-03 12:09:04 Slp: Result facility code: 1434
    2010-05-03 12:09:04 Slp: Result error code: 35937

    Monday, May 03, 2010 10:31 AM
  • 1. Did you installed in a local disk on the machine? Did you logon windows as local admin?

    2. If you're installing throught winzip [zipped file] this may occur. First extract the zip file and do the installation.

     

    Tuesday, May 04, 2010 10:57 AM
  • Hi,

    thanks for your reply.

    1. Yes, I installed on the local machine and I have administrator rights.

    2. No, the files are extracted. I also tried a mounted .iso file. I even tried to start setup from command prompt, but got the same error.

    The weird thing is, that I got quite far when I tried it the first time. In the end, I got the error about Visual Studio not being up to date. I couldn't apply SP1 to Visual Studio, so I uninstalled Visual Studio. My guess is, that during this uninstall process something went wrong: some component may have been deleted but still be registered in Windows. So, the SQL setup routine may think the component is still there but then can't find it and crashes.

    At least that's my interpretation of "This action is only valid for products that are currently installed. "

    The big question now is: which component could that be? Is this mentioned in the log-file? What does the Log-file say? I can't quite "decode" it into human language ...

    Best regards

     

    Tuesday, May 04, 2010 3:30 PM
  • It seams that the VSTO runtime has not been uninstalled correctly and if you check the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\vsto runtime Setup\v9.0.21022 you will find that the installed value is set to 1. To fix this issue change the value to zero and try to install the add-in again. re install the visual studio again it should work.
    Wednesday, May 05, 2010 10:25 AM
  • Hi Sekhara,

    thanks a lot for your reply! Unfortunatelty, I was a bit too quick uninstalling Visual Studio, which made everything worse:

     

    SQL Server refuses to install with a new error message:

    MsiGetProductInfo failed to retrieve ProductVersion for package with Product Code = '{53F5C3EE-05ED-4830-994B-50B2F0D50FCE}'. Error code: 1605..

     

    And, the worst thing, I can't even reinstall Visual Studio:

    "A problem has been encountered while loading the setup components. Canceling setup."

    Great ... :( I really wish there was something like a "forced installation" option, which just installs the missing components instead of throwing error messages ... I mean, that's what a setup routine is supposed to do, right?

     

    Wednesday, May 05, 2010 10:39 AM
  • 1) check in the registry for 
     GUID key

    2) for example

    "2243F21A-E132-44F7-BA13-024D0845C815" and used the first part of it 2243F21A,
     then reversed that to be A12F3422 and searched within the registry key
      HKCR\Installer\UpgradeCodes for matches

    3) delete the matched one

    4) start installation

    Wednesday, May 05, 2010 11:44 AM
  • It seemed the said product code was from SQL Server 2005, which is also installed on my machine. Apparently, uninstalling all traces of SQL Server 2008 and Visual Studio 2008 damaged the installation information of SQL 2005. It still run, but the installer could not properly detect it.

    This could be fixed by reinstalling service pack 2 and 3. The installer now correctly detects, again (and it's still running, lucky me).

    When I tried for the 100th time to install SQL server 2008, the above error message ( ...failed to retrieve ProductVersion for package with Product Code = '{53F ...) disappeared, but unfortunately the old error message was back (This action is only valid for products that are currently installed.).

    I then tried your suggestion to set "vsto runtime Setup\v9.0.21022  ..." to 0, but to no avail, setup still crashes. I did the same to

    "vsto runtime Setup\v2.0.50727 ..." and also "VSTA Runtime Setup\v9.0.21022". Still no luck, and Visual Studio won't install, neither, oh man ... :(

    But thanks very much for trying to help me! Also the hint on reversing the GUID key might be very valuable for future problems, I didn't know about that.

    Regards

     

    Wednesday, May 05, 2010 3:19 PM