Skip to end of metadata
Go to start of metadata

You have already:

Problem

Having issues with Chrome OS devices communicating with FileWave Admin.

Solution

Verify Chrome extension is installed in the policy

Verify FileWave extension has registered with FCM/GCM by looking at the log



View the device policy

  1. Open a Google Chrome window
  2. Browse to the URL: chrome://policy
  3. Scroll down to ExtensionInstallForcelist and select show more
  4. Look for the ID of the FileWave Inventory Extension ( ldhgnmkjehdokljjhcpkbhcmhoficdio  Figure 1.1 )
  5. If you see it there, scroll to the very bottom
  6. There will be a whole section for the FileWave Inventory Extension
  7. Verify all the policy fields are there ( Figure 1.2 )


Figure 1.1 - Chrome Policy Force List

Figure 1.2 - Chrome Policy for FileWave

View the Extension Console Log

  1. Open a Google Chrome window
  2. Browse to the URL: chrome://extensions
  3. Be sure Developer mode is enabled
  4. Click Details (Figure 2.1)
  5. Open the Background page (Figure 2.2)
  6. Select the Console tab to view the log 
  7. Verify the log contains "FCM Registration" (Figure 2.3)
    1. The is the messaging system FileWave uses to talk to the device, if it does not register then we can not communicate.
    2. If it failed or is empty. make sure the JSON used in the extension configuration contained FCM information
  8. Verify the log contains "... Report sent successfully"
    1. This confirms that the device is able to talk to your FileWave server
    2. if it is unable to send reports, then verify your JSON contains your server name and an inventory token

Figure 2.1 - Chrome Extensions

Figure 2.2 - Chrome Extension Details
Figure 2.3 - Extension log


ErrorDetailsSolution
GCM failed to registerThe device(s) are unable to use the information they received to contact Google's GCM/Firebase servicesBe sure you have GCM registered properly (Google Cloud Messaging (GCM/Firebase) Setup) in your admin preferences BEFORE you exported the settings for upload into Google Suite. You can always export it again.
Failed to load resource: net : : ERR_INSECURE_RESPONSEThe device(s) is unable to connect to your server with a secure connections
Error: failed to gather Geolocation data: All attempts exhaustedThe FileWave client on the device was unable to receive location information from the devices' OS
  • Verify in the devices security preferences the app has admin rights to location information
Failed to send inventory dataThe device was unable to contact the inventory port on the server
  • Verify the ports between devices and server are open (see: Default TCP and UDP Port Usage )
  • Verify you have all your settings in preferences BEFORE you exported the settings for upload into Google Suite. You can always export it again.
GET https://server.name:20445/inv/api/v1/client/settings/asdasdasd net : : ERR_NAME_RESOLUTION_FAILEDThere was a problem looking up the same of your server from the information received during enrollment
  • Verify you have all your settings in preferences BEFORE you exported the settings for upload into Google Suite. You can always export it again.
Uncaught (in Promise) TypeError: Cannot read property 'state' of undefined at ...Device was unable to contact the FileWave server OR the device was able to contact the FileWave server but the state of the device could not be read.
  • Attempt to change the state FileWave Admin and update the mode. Wait for the device to verify or force a verify of the device.
  • If the problem persists contact FileWave support.