Table 19. Network Issues
Symptom
|
Reason
|
Solution
|
Unable to communicate with Siebel Universal Queuing.
|
The machine where Siebel Universal Queuing is installed may not be accessible on the network.
|
Ping the machine by its name and by its IP address. If the machine does not respond to the ping, contact network administrators.
|
The UQ connector process may not be running on the Siebel Universal Queuing machine.
|
Use netstat to check if the port (set during installation) is already in use. If the port is in use, try the following steps:
- Reinstall the product with a port that is not in use.
- Check if ORB servers (qntorbsvr, dssrv, armsrv, alertsrv) are running. If not, contact support.
- Check if correct database instance was set during installation.
|
Unable to send events to EAI Object Manager.
|
The machine where EAI Object Manager is installed may not be accessible.
|
Ping the machine by its name and by its IP address. If the machine does not respond to the ping, contact network administrators.
|
EAI Object Manager itself may not be running.
|
Try starting the server.
|
Siebel Communications Server may not have sent valid configuration information for setting up connection with EAI Object Manager.
|
Make sure Siebel Communications Server is sending valid configuration information (for example, IP address, port, username or password) to Siebel Universal Queuing.
Check Siebel Universal Queuing configuration for valid information.
|
UQ connector process may not be running on the Siebel Universal Queuing machine.
|
Use netstat to check if the port (set during installation) is already in use. If the port is in use, try the following steps:
- Reinstall the product with a port that is not in use.
- Check if ORB servers (qntorbsvr, dssrv, armsrv, alertsrv) are running. If not, contact support.
- Check if correct database instance was set during installation.
|
Web server is not receiving stat events.
|
Secondary connection may not be set up.
|
Make sure Siebel Communications Server has set up secondary connection for statistics.
|
Configuration information sent may be wrong.
|
Make sure Siebel Communications Server is sending valid configuration information (for example, IP address, port, username or password) for the secondary connection to Siebel Universal Queuing.
Check Siebel Universal Queuing configuration for valid information.
|
