Some of the common error codes and how to do Troubleshooting.
Handshake failedSymptom or Error Message
Handshake failed.
Cause 1. The VIP assigned to the Central Dispatch site is in use by another machine.
2. Insufficient memory in application server.
3. ODBC Driver files inconsistency.
4. The sssasrm and sssasrp library files are inaccessible to the AIX user used to start the Siebel server.
5. Full disk drive.
6. The Siebel server is installed on an unsupported operating system.
Diagnostic Steps
1. Refer to Technical Note 419 on SupportWeb.
2. Confirm the OS is listed in the Siebel System Requirements and Supported Platforms guide.
3. Test the ODBC connectivity on all nodes. Refer to ”FAQ 1113: ’How do I test connectivity through ODBC data sources created by Siebel?’ ”
4. Ensure ”$SIEBEL_ROOT/lib” is specified in the path environment variables LIBPATH or LD_LIBRARY_PATH.
5. Ensure there is space on the disk drive.
6. Ensure the OS is supported.
Solution
1. Assign a unique IP address to the VIP.
2. Increase memory on the application server machine.
3. Reinstall the ODBC drivers.
4. Amend the siebenv.sh or siebenv.csh file (depending on the UNIX shell used) with the LIBPATH or LD_LIBRARY_PATH ”$SIEBEL_ROOT/lib” environment variables.
5. Allocate more space on the drive.
6. Install the application server on a supported operating system.
SVR-00026: Unable to allocate shared memory
Symptom or Error MessageSVR-00026: Unable to allocate shared memory
Cause
1. The shared memory file (default name: $.$.shm) may be present, preventing the server from creating a new version.
2. The Siebel server process may be unable to create a shared memory file because of permissions or lack of disk space.
3. The Max Tasks component parameter may be too large.
Diagnostic Steps
1. Inspect the enterprise.Siebel.log file for error messages.
2. Find out how the Siebel Server service ended the last time.
3. Inspect the component and Siebsrvr log files.
Solution
1. Delete or rename the .shm memory file (and kill processes which have a lock on the file) and restart the Siebel Server
2. Set the corrections permissions or free sufficient disk space
3. Back-up siebns.dat, copy an earlier siebns.dat.nnn files in the \admin directory to siebns.dat, then restart the Siebel Server.
REPIMEXP-ERR-1109
Symptom or Error MessageREPIMEXP-ERR-1109: Unable to read value from export file (%s)
Cause
1. Incorrect parameters in the imprep.ksh file (pre-Siebel 7.x)
2. Incorrect ODBC driver and driver manager versions
3. The mstrep.dat file may be corrupt.
Diagnostic Steps
1. Inspect the imprep_prim.log file.
2. Confirm the version of ODBC Driver installed.
Solution
1. Ensure imprep.ksh parameters are correct and change if necessary.
2. Ensure the ODBC version matches the System Requirements and Supported Platform guide.
3. Replace the mstrep.dat file.
start_ns or start_server is not working
Symptom or Error Message Siebel Gateway or Application servers can’t be started with the start_ns or start_server commands.
Cause
Siebel environment setup and UNIX setup needs to be analyzed and corrected.
Diagnostic Steps and Solution
Use the following steps to troubleshoot an issue when the client-server connection is not working:
1. Verify the environment variables PATH and LD_LIBRARY_PATH or LIBPATH (on AIX) or SHLIB_PATH (on HP_UX) and ensure that the Siebel root directory and Database client paths are correct, for example:
PATH=/usr/lib:/usr/bin:/usr/ucb:/etc:/export/home/oracle/ora817/bin:/
export/home/oracle/ora817/lib:/export/home/siebel/ie5/bin:/usr/local/
bin:/export/home/siebel/java1.3.1/j2sdk1_3_1/include:/usr/X/bin:.:/
export/home/siebel/siebel704/bin:/export/home/siebel/siebel704/mw/
bin:/export/home/siebel/siebel704/SYBSsa70/bin
LD_LIBRARY_PATH=/usr/lib:/export/home/siebel/siebel704/lib:/
export/home/siebel/siebel704/mw/lib:/export/home/oracle/ora817/
lib:/export/home/siebel/siebel704/SYBSsa70/lib:/export/home/
siebel/siebel704/lib/odbc/merant:/export/home/siebel/siebel704/lib/
odbc/merant
Verify database environment using odbcsql connect. Run queries against the database to ensure that tables have data.
2. Ensure network ports are not blocked:
• netstat –a | grep WAI
- Too many entries with TIME_WAIT and FIN_WAIT is not good.
- Wait for these ports to become free, or reboot the system to clear them
- Ensure gateway is up and the port is in LISTEN mode.
4. Check connectivity of all machines using ping.
5. Shared memory cleanup
• Ensure that Gateway and Siebel servers are stopped.
• Remove *.shm files in SIEBEL_ROOT/admin directory.
• Restart the servers.
6. Mainwin environment cleanup
Run $SIEBEL_ROOT/mwcleanup and delete files in /tmp.
Could not start the Siebel Server [xxxx] service on…; Error 2182: The requested service has already been started.
Symptom or Error Message
1. Could not start the Siebel Server [xxxx] service on …
2. Error 2182: The requested service has already been started.
Cause
The machine was not rebooted before re-installing the Siebel Server.
Diagnostic Steps And Solution
Reboot the machine and restart Siebel Server.
Received error 127 () looking up the specified Gateway Server
Symptom or Error Message
Received error 127 () looking up the specified Gateway Server. Please check your installation guide or contact your system administrator.
Cause
If the network connection is down or the Gateway service is not fully started while installing the Siebel server, the above error may appear.
Diagnostic Steps
1. Check the network connectivity.
2. Check the Gateway service status.
Solution
1. Ensure the network connection is not blocked or lagged and allows the Siebel Server to connect to the machine on which the Gateway is installed.
2. Make sure that Siebel Gateway service is up and running. On Windows servers, it may be necessary to create a script to manually start the services, allowing two minutes between Gateway and Server start-ups.
Unable to install Siebel enterprise server over Siebel enterprise server. Installed product has newer version
Symptom or Error Message
Customers receive the error message ”Unable to install Siebel enterprise server over Siebel enterprise server: installed product has newer version” when installing the Siebel Report Server or Siebel Database Server.
Cause
Users are installing another Siebel product under an existing Siebel Root directory that has already been patched. For example, users install the Siebel Report Server version 7.5.2 under the Siebel Root directory that has version 7.5.2.8 installed.
Diagnostic Steps
Under the Siebel Root directory\siebsrvr, look at the base.txt file and ensure it is the same version as the Siebel product that is being installed.
Solution
If the Siebel Server has already been patched, then do one of the following:
1. Install another environment with the Siebel Server and Database Server in a new directory.
2. Reinstall the whole environment again.
If the behavior is encountered while installing the Siebel Report Server, then run the Siebel installer, select a new instance and specify a different directory then the Siebel Root to install the Siebel Report Server. After installing the Siebel Report Server version 7.5.2 users will need to apply the patch to bring it up to 7.5.2.8.
Related Posts
No comments :