Troubleshooting errors Binding Omnis Server Socket and issues rendering logos, tabs, or find interfaces

The most common cause for the message Binding Omnis Server Socket is documented under Error Binding Omnis Server socket appears when opening CDM+.

This is an advanced troubleshooting article for resolving deeper networking issues.

Explanation

CDM+ uses local TCP/IP network communication for various functions:

Rendering HTML-based controls, such as:
- Logos on the Login, About, and Setup Assistant windows
- Tab bars on record windows
- Field lists on simple and advanced finds
Debugging tools

If this traffic is blocked the following operations may not behave properly.

The communication can exist between the following processes:

CDM+
Node

This traffic is restrict to local loopback addresses over IPv4 and IPv6:

0.0.0.0
::1
127.0.0.1

If this traffic is blocked or redirected ensure you do not have a firewall or security software blocking it. Some VPN software can also redirect this traffic to a remote host and cause issues.

Troubleshooting

Windows

Use the netstat command in a shell with administrative privileges to review open CDM+ sockets and ports:

CODE

netstat -a -o -n -b

Review the results for the cdm+.exe and node.exe processes.

Here is an example of activity from CDM+ 12.1.0 on Windows 11 open to a login window. This activity has been annotated.

CODE

#######################################################
##### THIS IS THE CONNECTION TO THE DATABASE      #####
##### CONNECTING TO A PUBLIC IP OVER THE INTERNET #####
#######################################################

  TCP    192.168.230.128:64076  172.104.11.248:443     TIME_WAIT       0
  TCP    192.168.230.128:64078  207.254.16.153:9566    ESTABLISHED     9400
 [CDM+.exe]

  TCP    192.168.230.128:64087  207.254.16.153:9566    ESTABLISHED     9400
 [CDM+.exe] 

###################################################
##### THIS IS THE LOCAL NODE.EXE PROCESS THAT #####
##### CDM+ CONNECTS TO FOR VARIOUS OPERATIONS #####
###################################################

##
## THE FOLLOWING PORTS MAY BE DYNAMIC
## ALL CONNECTIONS ARE LOCAL TO THE MACHINE
## THE NEED TO BE ALLOWED 
## NOTE BOTH IPV4 AND IPV6 ARE USED
##

##
## PORT 6102
## PORT FOR ESTABLISHING A NEW CONNECTION
##

  TCP    0.0.0.0:6102           0.0.0.0:0              LISTENING       5828
 [node.exe]

  TCP    [::]:6102              [::]:0                 LISTENING       5828
 [node.exe]

##
## PORT 64072 AND 64075
## CONNECTION BETWEEN CDM+ AND NODE
##

  TCP    0.0.0.0:64072          0.0.0.0:0              LISTENING       3352
 [node.exe]

  TCP    [::]:64072             [::]:0                 LISTENING       3352
 [node.exe]

  TCP    127.0.0.1:64075        127.0.0.1:64072        CLOSE_WAIT      9400
 [CDM+.exe]

  TCP    127.0.0.1:64072        127.0.0.1:64075        FIN_WAIT_2      3352
 [node.exe]

##
## PORT 64070 AND 64068
## CONNECTION BETWEEN CDM+ AND NODE
##

  TCP    127.0.0.1:64070        127.0.0.1:64068        ESTABLISHED     5828
 [node.exe]

  TCP    127.0.0.1:64068        127.0.0.1:64070        ESTABLISHED     9400
 [CDM+.exe]

  TCP    127.0.0.1:64068        0.0.0.0:0              LISTENING       9400
 [CDM+.exe]


######################################################
##### THIS IS THE CDM+ PROCESS ITSELF            #####
##### CDM+ CONNECTS TO ITSELF VARIOUS OPERATIONS #####
######################################################


##
## PORT 5989 IS AVAILABLE FOR DEBUGGING (NOT USED)
##

  TCP    127.0.0.1:5989         0.0.0.0:0              LISTENING       9400
 [CDM+.exe]

##
## PORT 31775 64071 64079 64073 64074
## INTERNAL CDM+ COMMUNICATION
##

  TCP    0.0.0.0:31775          0.0.0.0:0              LISTENING       9400
 [CDM+.exe]

  TCP    0.0.0.0:64071          0.0.0.0:0              LISTENING       9400
 [CDM+.exe]

  TCP    127.0.0.1:64071        127.0.0.1:64079        ESTABLISHED     9400
 [CDM+.exe]

  TCP    127.0.0.1:64079        127.0.0.1:64071        ESTABLISHED     4716
 [CDM+.exe]

  TCP    127.0.0.1:64073        127.0.0.1:64074        ESTABLISHED     9400
 [CDM+.exe]

  TCP    127.0.0.1:64074        127.0.0.1:64073        ESTABLISHED     9400
 [CDM+.exe]

macOS

Use the lsof command to locate open CDM+ sockets and ports:

CODE

sudo lsof -i 4tcp | grep -i -E 'omnis|node'

This command requires administrative privileges and filters to the CDM+ process (omnis) and node.

Here is an example of activity from CDM+ 12.1.0 on macOS 13 open to a login window

CODE

COMMAND     PID   USER   FD   TYPE             DEVICE SIZE/OFF NODE NAME
Omnis      5960  aclay   38u  IPv4 0x72ee9b3c59631b6f      0t0  TCP *:16765 (LISTEN)
Omnis      5960  aclay   39u  IPv6 0x72ee9b3c52ba15e7      0t0  TCP *:16765 (LISTEN)
Omnis      5960  aclay   67u  IPv4 0x72ee9b3c595db18f      0t0  TCP localhost:53356 (LISTEN)
Omnis      5960  aclay   95u  IPv4 0x72ee9b3c595ae67f      0t0  TCP *:53357 (LISTEN)
Omnis      5960  aclay  112u  IPv4 0x72ee9b3c585ab18f      0t0  TCP localhost:53359->localhost:53358 (CLOSED)
Omnis      5960  aclay  113u  IPv4 0x72ee9b3c585ad2bf      0t0  TCP 10.3.200.3:53363->nnn.suran.com:9566 (ESTABLISHED)
Omnis      5960  aclay  117u  IPv4 0x72ee9b3c59635dcf      0t0  TCP 10.3.200.3:53369->nnn.suran.com:9566 (ESTABLISHED)
Omnis      5960  aclay  118u  IPv4 0x72ee9b3c5963318f      0t0  TCP localhost:53357->localhost:53364 (ESTABLISHED)
node       5992  aclay   21u  IPv6 0x72ee9b3c52ba2c67      0t0  TCP *:53358 (LISTEN)
node       5992  aclay   95u  IPv4 0x72ee9b3c595ae67f      0t0  TCP *:53357 (LISTEN)