Siebel Installation Guide for Microsoft Windows > Verifying and Troubleshooting Your Installation >

Troubleshooting Installation and Configuration for Siebel Enterprise Server


This topic presents troubleshooting information related to installation and configuration of Siebel Enterprise Server components.

Related Topics

Starting the Siebel Gateway Name Server

Starting the Siebel Server Service

Verifying Installation for the Siebel Enterprise Server

Verifying That the Siebel Gateway Name Server Has Started

Troubleshooting Installation and Configuration for the Siebel Gateway Name Server

This topic describes potential errors that can result from a faulty installation or configuration of Siebel Gateway Name Server. Such problems can have any of several causes, the most common of which are listed in Table 16.

NOTE:  If you cannot start the Siebel Gateway Name Server, then you will not be able to configure a Siebel Enterprise or configure and start a Siebel Server.

Table 16. Troubleshooting Siebel Gateway Name Server Installation and Configuration
Problem
Cause
Solution

The Siebel Gateway Name Server does not start.

You might not have privileges as the Siebel service owner.

Review the instructions in Creating the Siebel Service Owner Account.

You cannot start the Siebel Gateway Name Server service on \\COMPUTER_NAME.

Error XXX: The service did not start due to logon failure.

Login failure

  1. Navigate to Control Panel, Administrative Tools, and then Services.
  2. Select the Siebel Gateway Name Server.
  3. Right-click, then choose Properties.
  4. In the Log On tab, specify the user name and password to use for this service.

You receive an error at system startup that a driver is missing.

This problem can occur if you uninstall earlier Siebel Business Applications versions without first stopping the Siebel Server.

Stop the Siebel Server before uninstalling Siebel Business Applications.

If the services are no longer visible within the Services menu, then contact Oracle Global Customer Support for instructions.

Troubleshooting Installation and Configuration for the Siebel Server

This topic describes potential errors that can result from a faulty installation or configuration of Siebel Server. Such problems can have any of several causes, the most common of which are listed in Table 17.

Table 17. Troubleshooting Siebel Server Installation and Configuration
Problem
Cause
Solution

The Siebel Server cannot be installed.

Insufficient user privileges

For information about setting up appropriate administrative user privileges to install, see Creating the Siebel Service Owner Account.

Trying to install or configure the Siebel Server out of sequence

For the required installation and configuration sequence, see Overview of Installing Siebel Business Applications.

Failure to install the required hardware or software

Installation errors related to software requirements are logged in the Siebel Enterprise Server installer log file. For requirements, see the Certifications tab on My Oracle Support.

The following error messages occur for a Siebel Enterprise supported by a Microsoft SQL Server database:

  • In the SVRsetup.log file:

    5000: Bad key name., exiting...

  • In Microsoft SQL Server DSN configuration (server field):

    completed with error(s):2000046

You used brackets in the name that you gave to one or more of your Siebel Servers or to your Siebel Enterprise Server.

Remove the applicable configurations and re-create them with new names. For more information, see Process of Removing Configuration Data.

The Siebel Server does not start after configuration.

Siebel Gateway Name Server not started

Verify that the Siebel Gateway Name Server was started. Start it if it was stopped.

Invalid input values during configuration

Verify that the input values during configuration were valid.

Insufficient system privileges

Verify that you have sufficient system privileges to start the service. For more information, see Creating the Siebel Service Owner Account.

Troubleshooting the ODBC Data Source Connection

This topic describes troubleshooting steps for your ODBC data source connection.

NOTE:  If your database is IBM DB2 for z/OS, then see Implementing Siebel Business Applications on DB2 for z/OS.

Troubleshooting Connection Problems on Oracle Database

Complete the following instructions to troubleshoot Oracle Database connection problems on Windows. See also Configuring Siebel Server Connectivity to the Siebel Database.

To troubleshoot a failed ODBC connection for Oracle Database

  1. Verify that the ODBC driver was correctly installed by reviewing the file structure under SIEBSRVR_ROOT/BIN.
  2. If the files have been correctly copied to the BIN subdirectory, then verify that the Oracle connect string that you entered during the Siebel Enterprise configuration was valid.
Troubleshooting Connection Problems on IBM DB2

Complete the following instructions to troubleshoot IBM DB2 connection problems. See also Configuring Siebel Server Connectivity to the Siebel Database.

To troubleshoot a failed ODBC connection for IBM DB2

  • Verify that the data source name (SiebelEnterpriseName_DSN) that you entered during the Siebel Server configuration was valid. Also verify that the required IBM DB2 client version is available on the machine and verify that the IBM DB2 catalog step has been completed correctly.
Troubleshooting Connection Problems on Microsoft SQL Server

Complete the following instructions to troubleshoot Microsoft SQL Server connection problems on Windows. See also Configuring Siebel Server Connectivity to the Siebel Database.

To troubleshoot a failed ODBC connection for Microsoft SQL Server

  • Verify that the data source name (SiebelEnterpriseName_DSN) that you entered during the Siebel Server configuration was valid. Also verify that the SQL Server database is up and running, and validate the ODBC connectivity.
Siebel Installation Guide for Microsoft Windows Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices.