How to stop Norton AntiVirus from blocking CDM+ processes

eA May 2025 update to Norton Antivirus is not compatible with CDM+. This article will outline the steps needed to workaround this issue.

Binding Omnis Server socket spins indefinitely or fails

The first issue occurs upon launching the CDM+ Desktop application. Expected behavior is that CDM+ launches and then prompts for a login for the database you have selected. The actual behavior being experienced is that CDM+ launches and a popup window appears with the text “Binding Omnis Server socket…” and spins indefinitely. If you hit cancel on this popup the process will fail and a trace log will appear and you will then be prompted to login as normal.

Norton Quarantines a valid file and CDM+ locks up

The second issue occurs during several processes including some updates and reports. Expected behavior is that you will go generate a report or run an update and Norton will popup alerting that a file has been quarantined. CDM+ will then freeze and must be force quit.

How to resolve these issues

Both issues can be resolved with the following workaround:

1. Open a Windows File Explorer window

2. Click in the navigation bar at the top and type %TEMP%

   

3. Press Enter and note the value between Users and AppData. This is your username which you will need it for a later step. In the example the username is alex. You can close this window once you’ve noted the username

   

4. Open Norton, then on the sidebar click the Security and then Advanced Security

   

5. Within the Advanced Security window click the Antivirus tab

   

6. From here navigate to Exclusions and click Add to add a new exclusion record

   

7. One at a time add the following file paths to the exclusions list replacing [your user] with the username you identified earlier

   1. C:\Program Files\Suran\

   2. C:\Users\[your user]\AppData\Local\Temp\suran\

Replace [your user] with your user name. For example, if your user name is alex you would enter the following exclusion:

• C:\Users\alex\AppData\Local\Temp\suran\

File path a. will resolve the Binding Omnis Server socket issue, and file path b. will resolve the issue with Norton quarantining valid files

5. Once these file paths are added your exclusions list should look something like this

   

6. You should now be able to launch and operate within CDM+ as normal