Plantronics + Polycom. Now together as logo

Shopping Cart

Product Quantity Price Subtotal
Cart Subtotal

Spokes SDK Known Issue 18735: Installing Spokes SDK merge module or Spokes_RT installer on top of full Spokes software can cause errors

Article ID :
000009862
Known issue 18735: Installing Spokes SDK merge module or Spokes_RT installer on top of full Spokes Software can cause errors There is a known issue with Spokes SDK 2.6 merge module and Spokes_RT installers when installed on top of the full Spokes Software, particularly older versions of the full Spokes Software. Author: Lewis Collins
Date: 1st May 2012.
Internal ID: 18735
Impacted Spokes version: 2.6.54523.0 Issue summary Installing Spokes SDK merge module MSM or Spokes_RT installer on top of full Spokes Software can cause problems such as the Spokes Software components to stop working and/or give errors. In worst case: If Spokes 2.5 is upgraded with Merge Module 2.6 then Metrics Manager stops working, also PCP and Update Manager are unable to run and crash repeatedly. Workaround Recommendation: Always uninstall Spokes Software before installing an application that contains a Spokes SDK merge module or Spokes_RT installer. Alternatively if you are using the Wix installer system for your application you can add custom Wix code to your installer to check for previous versions of Spokes, and if found abort the installation of the Spokes merge module (for example). See below. Sample code You can check whether Spokes, Spokes SDK or Spokes RT is installed using Wix code that looks like this:     <Property Id="SPOKES_INSTALLED">
      <RegistrySearch Id="Spokes"     Root="HKLM" Key="SOFTWARE\Plantronics" Name="Spokes"     Type="raw"/>
      <RegistrySearch Id="Spokes_RT"  Root="HKLM" Key="SOFTWARE\Plantronics" Name="Spokes RT"  Type="raw"/>
      <RegistrySearch Id="Spokes_SDK" Root="HKLM" Key="SOFTWARE\Plantronics" Name="Spokes SDK" Type="raw"/>
    </Property> Since only one of these can be installed at any given time if the property is set at install time then you know you have one of them installed. Then add a custom action to the InstallUISequence and the InstallExecute sequence:     <InstallExecuteSequence>
      <!-- If the FileSearch indicates that PURE.exe has already been installed, abort the installation.       -->
      <Custom Action="NoSpokes" After="AppSearch">SPOKES_INSTALLED AND NOT (REMOVE="ALL")</Custom>
    </InstallExecuteSequence>

Here's the custom action:

    <CustomAction Id="NoSpokes" Error="This module may not be used to upgrade an existing Plantronics Spokes Software installation."/> Call it what you like.

< Previous 10 | Next 10 >()

Filter by