Skip to main content

Error installing Connector ID Key on Machine with browser Flexapps

Ryan Wilp
  • Created:
  • Updated:

Problem:

You may see the following error if you attempt to install Connector ID Key agent version 6.6.2 or prior agent on a machine that also has Firefox or Chrome Flexapps.  Version 6.7+ of the CID agent should not generate an install error if the registry key is missing, but may fail to gather browser metrics.

Possible Resolution:

Insert the location of the Connector ID's Native Messaging Host app into the virtual registry for the application (browser) in question.  There are a couple of approaches that you can take.

1. Put the values you need directly into the browser Flexapp packages using the Flexapp Package Editor.
2. Set the values on the system prior to the Flexapp packages being activated. This can also be done using a pre-playback script on the packages.

The relevant registry should be in one the following locations, depending on browser and bit version.

Chrome

registry path

 
HKEY_LOCAL_MACHINE\SOFTWARE\Google\Chrome\NativeMessagingHosts\com.lwl.chrome.monitor
-OR-
HKEY_LOCAL_MACHINE\WOW6432Node\SOFTWARE\Google\Chrome\NativeMessagingHosts\com.lwl.chrome.monitor

Firefox registry path

 
HKEY_LOCAL_MACHINE\SOFTWARE\Mozilla\NativeMessagingHosts\com.lwl.firefox.monitor

-OR-

HKEY_LOCAL_MACHINE\WOW6432Node\SOFTWARE\Mozilla\NativeMessagingHosts\com.lwl.firefox.monitor

 

The(Default) key at this location must be set to the to the string (REG_SZ) value of the full path of the lwl.{browser}.monitorwithin the Connector ID folder.

Taking the default Connector ID install path, the registry key value would be:

Chrome (Default) key value

 
C:\Program Files\Liquidware\Connector ID\lwl.chrome.monitor.json

-OR-

C:\Program Files (x86)\Liquidware Labs\Connector ID\lwl.chrome.monitor.json
Firefox (Default) key value 
C:\Program Files\Liquidware\Connector ID\lwl.firefox.monitor.json

-OR-

C:\Program Files (x86)\Liquidware Labs\Connector ID\lwl.firefox.monitor.json

 

Registry example for 64-bit Chrome, version 6.7 Connector ID:

Registry example for 32-bit Chrome, version 6.6.2 Connector ID:

 

Note: 

In certain cases, a 64-bit install of Windows may attempt to run the Liquidware Browser Extension from a 32-bit browser Flexapp. In these cases, the 32-bit browser should be able to access the registry key values described in this article; however, adding \WOW6432Node\ to the key's path in the registry may be required.

 

Product: Stratusphere FIT/UX

Product Version: All

Expires on: 365 days from publish date

Updated: December 15, 2023

Related articles