Evergreen

  1. Bug #1756084
  2. Comment #12

Comment 12 for bug 1756084

Revision history for this message
Bill Erickson (berick) wrote :

Thanks for the details, Lynn.

There's a bit of configuration that allows Chrome to talk to the Java app. It consists of a file and a Windows registry key, telling Chrome where to find the file.

Can you confirm this file exists and that your user account can view the contents of the file?

C:\Program Files (x86)\Hatch\extension\host\org.evergreen_ils.hatch.json

Can you confirm one of these commands run within the Windows command line returns a value that references the above files?

reg query HKLM\SOFTWARE\Google\Chrome\NativeMessagingHosts /s
reg query HKLM\SOFTWARE\WOW6432Node\Google\Chrome\NativeMessagingHosts /s
reg query HKCU\SOFTWARE\Google\Chrome\NativeMessagingHosts /s
reg query HKCU\SOFTWARE\WOW6432Node\Google\Chrome\NativeMessagingHosts /s

For me, the 2nd command returns:

reg query HKLM\SOFTWARE\WOW6432Node\Google\Chrome\NativeMessagingHosts /s
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Google\Chrome\NativeMessagingHosts\org.evergreen_ils.hatch
    (Default) REG_SZ C:\Program Files (x86)\Hatch\extension\host\org.evergreen_ils.hatch.json