5 posts / 0 new
Last post
MMX
COM Class Registration
Hello there! Working on integrating the SDK right now and am running into the COM Class registration.  The users who are encountering this issue are running the Runtime SDK MSI installer and still encountering the issue.  Does the installer not actually...register the items its installing? Or am I missing a step?   What should the course of action be for end-user deployment? I'd rather not have to chain MSIs.   Also, is there a way that you can include a Nupkg file with the SDK so this whole situation and integration is a little easier in the future?

lcollins
Hi, You need to install at least 2 of the 3 MSIs provided with the SDK to enable COM API, namely: SpokesSDKNativeRuntime.msi and SpokesSDKRuntime.msi. You don't need SpokesSDKStartup.msi unless you are using REST API. More details here: https://developer.plantronics.com/article/plantronics-sdk-3x-deployment-options As an alternative, require your users to install the full Hub from: https://www.poly.com/software Thanks, Lewis.

MMX
What's the process for situations where both MSIs are still installed and the software is still throwing COM errors? User in question has the Hub, the Native Runtime AND the normal runtime installed.

lcollins
Hi, What are the specific COM errors? Which Hub API(s) have you used, and which deployment option are you recommending? Thanks, Lewis.

MMX
Retrieving the COM class factory for component with CLSID {750B4A16-1338-4DB0-85BB-C6C89E4CB9AC} failed due to the following error: 80080005 Server execution failed (Exception from HRESULT: 0x80080005 (CO_E_SERVER_EXEC_FAILURE)). I'm simply using the headset buttons in my implementation. The user's headset is also not transmitting audio so this could be a physical hardware issue but I have no way of digging into this further. This doesn't seem to be an error generated from unregistered DLLs. But I'd love insight into this issue.

Add new comment