Body
On Windows:
- Open File Explorer.
- Navigate to 'C:\Program Files(x86)'
- Ensure the directory SafeConnect exists.
- Ensure there is a file in the directory called SCClient.exe. If not, re-install the policy key and restart the device.
On Mac:
- Open Finder and choose Applications.
- Check if an application exists called SafeConnect.
- Right click the application and select "Show Package Contents".
- Ensure that under Contents > MacOS, there exists a file called scClient and scManagerD If not, re-install the policy key and restart the device.
On Windows:
- Open the Task Manager and navigate to the Processes tab.
- Check the box “Show processes from all users” at the bottom left.
- Click on the “Name” column heading to sort.
- Look for SafeConnectClient.exe and scManager.sys, both should be present.
On Mac:
- Open Activity Monitor (Finder > Applications > Utilities > Activity Monitor).
- Choose “Show All Processes” under the "View" menu Click on the “ProcessName” column heading to sort.
- Look for two services named "SafeConnect", one ran by the Admin user and one by the root user. Both should be present.
- If you have only recently installed the Macintosh Policy Key, both processes may be called SafeConnect.
If the above is resolved or working as it should and the issue is still happening, follow the steps below.
- Run an Anti-Virus scan using a known Anti-Virus
- Run an Anti-Malware scan (Malwarebytes is an option for this)
- Ensure no Malware is found
Do you see a certificate error or connection error when navigating to the Policy Key Download Page during the time the device is failing policy (Not in open access)? A certificate error is shown:
- This may indicate that the endpoint does not have the "Go Daddy Class 2 Certification Authority Root Certificate" installed. Please ensure you have the latest OS updates applied to your system.
- You can download and install this certificate from godaddy's website: Godaddy Root Certificate
- A connection error occurs
- This may indicate that the endpoint does not have a proper route to the SafeConnect appliance or an alternate network connection issue is occurring.
- In this case, please submit a ticket to OPSWAT Support with a Policy Key log at level 5, as shown below and please provide OPSWAT
Support the error shown when attempting to reach the Policy Key download page, preferably in a screenshot: my.opswat.com
-
To collect a policy key log
-
If you are requested to enable further debugging (Log Level 5) for the Policy Key by OPSWAT Support
- Update the config.xml file with the following values:
<LoggingLevel>5</LoggingLevel><LoggingLimit>50240</LoggingLimit>
- Wait for the issue to occur again
- Wait a few minutes after the issue occurs and save
LogFile.txt
to upload to support ticket at The Support Portal
-
If you do not see a LogFile.txt in that directory after 5-10 minutes
- Try re-downloading the Policy Key from your SafeConnect appliance and/or rebooting the machine. Then, you will need to set the logging level again.
If this article was unable to solve your problem, please submit a support ticket at Troy Helpdesk with the policy key log attached.