Troubleshooting

Browsium Client fails to report data

There are a few reasons Browsium Client may fail to report usage data to the Proton server:

• Check to ensure the Browsium Client browser extensions are enabled

• Check to ensure the Proton Server URL is reachable from the PC running the Browsium Client

When the Browsium Client is unable to contact the server, data will be stored for a period until connectivity is restored. If the connection is disrupted for an extended period, older Proton data will be overwritten in order to limit the cache size. This value is stored in the registry the value MaxClientCacheSizeInMegabytes and the default is 128.

{width=“5.976380139982502in” height=“1.1882524059492563in”}

Browsium Client Management Server appears to fail installation

The BCMS installer is designed to report reasons for an installation failure, but if an existing IIS Site with a duplicate name was present during BCMS Manager setup, the IIS portion of the BCMS environment will fail to install correctly.

Proton not working with Microsoft Edge

Microsoft Egde must be run on a domain joined machine, under a domain user account and side loading of extensions enabled. See section 5.2.4 for more information.

Proton reports not displaying properly

Browsium Client Manager does not fully support Internet Explorer versions 10 or earlier. Use at your own risk.

Proton Server showing certificate warnings

BCMS can be installed using a self-signed certificate so browsers may display a certificate warning when accessing the Browsium Client Manager. To remove the warnings, add the self-signed certificate to the store on the client machine.

Some certificate warnings may be related to mismatched server names when compared to the information on the SSL certificate. Check to ensure the ‘server url to connect to’ value in the Browsium Client Manager login screen exactly matches the name in SSL certificate.