Siebel Administration >  ADM-02088: Connection to specified server not found

ADM-02088: Connection to specified server not found

- The error reported in %siebel_server%\log\%server%\Siebsrvr*trc was "SMI-00046" which indicates a port is already in use. After checking output from "srvredit /g /e /s /v GENERIC " the server parameter, PortNumber, was set to the same value of the port number assigned to the Synch manager component. The 'corruption' in siebns.dat appeared to happen after a NT system crash.

To resolve the problem issue the following on the Siebel Servers that are experiencing the problem: Please note that before making any modification to the siebns.dat file (with srvredit or by the Server Administration screen, you should make a backup of the GTWY_ROOT\admin folder)

Please see the Siebel System Administration Guide for additional information on srvredit command utility and syntax.

srvredit /g /e /s /r $Server.PortNumber=0 /f

4) Resonate configuration problem

- Error Messages from the Server Manager screen:

ADM-02044: No connection found to any active servers

ADM-02043: Connection to server 'null' not found

- Siebel doesn't find a Siebel Server but just gives a wrong IP address instead of the correct hostname in the Siebel Servers applet.

- The user had prepared the installation of Resonate's Central Dispatch, by configuring the virtual adaptor. This apparently affected the subsequent installation of Siebel. The user couldn't activate Central Dispatch because he didn't have the license key. When connecting to the server from a client Siebel by default picks the IP address of this virtual adaptor. So he could connect and navigate in the user Siebel UI but when viewing the Server Components/Tasks he got an error.

- By just removing the virtual adaptor the problem was solved.

5) Incorrect Network Configuration

- The errors in the srvrmgr*.trc file appeared as follows:

ADM-02044: No connections found to any active servers

ADM-02039: INTERNAL: SA_ERR_EOF

- The reason for these errors was incorrect reference to the machine name in the Network Neighborhood | Properties | TCP/IP | DNS.