GEN-05009: Unable to connect to gateway server
Symptom or Error MessageSBL-GEN-05009: Unable to connect to gateway server
Cause1. Refer to item 1 in this section as the same causes apply.
2. Siebel Server incorrectly specified in the .cfg file or the incorrectly set ConnectString in the .cfg file.
Diagnostic Steps
1. Check that the Gateway is online and running.
2. Check whether the Web Server can ping the Siebel Gateway.
3. Review ”FAQ 1773: What are the steps to troubleshoot the error message: ’The server you are accessing is either busy or experiencing difficulties……’ in a Siebel 7 Web client user browser?”
Solution
Accurately post the correct Siebel Server parameters, etc. in the .cfg files.
Display Help
Symptom or Error Message
Display Help for clicked on buttons, menus and windows Help. The error occurs when trying to launch the Call Center Icon.
Cause
Applicable when running a new instance of Microsoft Internet Explorer.
Diagnostic Steps
1. Check Microsoft operating system Service Pack levels.
2. Check Microsoft Critical Updates and Security Updates.
3. Check custom level security settings.
4. Check system requirements and versions of Microsoft Virtual Machine, ActiveX Controls and Plug-Ins.
Make sure the Internet browser complies with the system requirements documented in the System Requirements and Supported Platforms document found on SupportWeb.
Solution
Resolve by restoring the original settings for IE in Tools > Internet Options > Advanced Tab and click on the Restore Defaults button.
The Siebel Server [xxx] service terminated with service-specific error
Symptom or Error Message
In the Windows NT Event Viewer, the error message is displayed: ” The Siebel Server [xxx] service terminated with service-specific error.”
Cause1. Installing a new NIC may cause IP configuration mismatch or incorrect binding orders.
2. Resonate is not installed properly on the node. Install all Resonate components as documented in Siebel Bookshelf. Missing CDAction.exe can cause this behavior.
Diagnostic Steps
1. Use ODBCSQL to check database connectivity. Re-install MDAC.
2. Check User Rights: ’Log on as a Service’ and ’Act as Part of Operating System’ must be set. The Siebel Server installation guide explains this in detail.
Solution
See above.
The type of user agent is not found
Symptom or Error Message
”The type of user agent is not found”. This error may occur on the Mobile Web Client or from the browser via the Web Server after typing in the User Name and Password.
Cause1. Most likely the invalid entry of License Keys; the base key was not installed first.
2. Correct login missing from S_USER table.
3. Compiling a java script or running genbscript with invalid code
4. Compilation of a custom .srf file
Diagnostic Steps
1. Check the Configuration Context from Tools. From the ”Target Browser Config”, ensure the supported version of IE is selected and that there is a value for User-Agent set in the capability names section.
2. Check that all license keys are inserted and working properly.
3. Check whether the user is logging into the Local, Sample or Server data source; using the standard SRF or customized; and using Call Center or CTI.
Solution
In most of cases, clearing Internet Explorer cache on the Mobile Client and ensuring enough free disk space will resolve the behavior.
54008 Error on DB2
Symptom or Error Message
54008:[IBM][CLI Driver][DB2/6000] SQL20075 The index or index extension ”S_DD_HIERATRVAL_M2” cannot be created or altered because the length of ”PCODE” is more than 255 bytes.
Cause
DB2 parameters and sizing are not set correctly for index length and table space
Diagnostic Steps
1. Verify that the Db2set environment parameter DB2_INDEX_2BYTEVARLEN (also known as a DB2 Registry variable) has been set to ’ON’.
2. Ensure proper table space sizing before running a new installation.
3. Check the ddl_ctl.log and dataimp.log files for errors regarding space problems.
Solution
1. Review the proper sizing parameters.
2. Make sure that the database version complies with system requirements documented in the System Requirements and Supported Platforms document.
[SWSE] Login failed. SVR-03005: No server connect string for Siebel Component
Symptom or Error Message
[SWSE] Login failed. SBL-SVR-03005: No server connect string for Siebel Component %3 in Siebel Enterprise %1, Siebel Server %2
Cause1. Usually occurs on the Client browser when logging into application and caused by an Object Manager component not being ”enabled”. This occurs most frequently with the eService ObjMgr which should be automatically enabled when launching the Call Center ObjMgr.
2. In a UNIX environment, incorrect file permissions could disable communications between the Web and Siebel Servers.
Diagnostic Steps
1. Review the SWEApp log files generated from the Web Server: the Gateway Name Server may not be enabled or may not have the proper parameters for the Siebel Server, Object Manager.
2. As a post-installation step, make sure to execute the ”Synchronization” button in the Batch Component Admin Screen.
3. Run the srvrmgr utility to see if all server components are running properly.
Solution
1. Make sure the Siebel Server components are enabled.
2. Make sure the Web Server has proper file permissions in a UNIX environment.
REPIMEXP-ERR-1124
Symptom or Error Message
REPIMEXP-ERR-1124: Unable to import table \”%s\” (%s).A common server error that occurs when using dev2prod.
Cause1. Due to some Data Model changes in column names, table names, etc. from version 6.x to v7.x, new data imports may fail.
2. Running a Full Get for a local database could cause similar errors.
3. In UNIX, limits to memory allocation segment space may cause the upgrade or install to fail and generate similar errors.
Diagnostic Steps
1. Check the log files generated by the dev2prod process.
2. Check the dataimp logs for a new database installation or the upgrep logs generated during an upgrade.
3. The REPIMEXP-ERR-1124 error is usually posted in conjunction with ”Invalid Column or Table name” errors.
Solution
Review log files to identify the columns or tables in question and make corrections to sizing and length. Follow System Requirements and Supported Platforms Guide.
No comments :