SBL-SVR-01031: Invalid Parameter

Applies to:

Siebel Call Center - Version 8.0.0.7 [20426] to 8.1.1.3 SIA[21219] [Release V8]
Information in this document applies to any platform.
*** Checked for relevance on 05-Dec-2012 ***

Goal

What is the meaning of error "SBL-SVR-01031: Invalid Parameter" in the SRProc logs?

Fix

Log files of Server Request Processor (SRProc) show repeated 'SBL-SVR-01031: Invalid Parameter' error messages whenever a SQL statement has parameters bound to it.

This behavior was reported in BUG 10642871 -"SRProc: Repeated Error: SBL-SVR-01031: Invalid Parameter".

This error is benign and can be ignored.
This bug has been fixed in 8.1.1.4 fix pack.

Applies to:

Siebel System Software - Version: 8.0.0.8[20430] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

Customer has done fresh installation of  version 8.0 and applied patchset 8.0.0.10 on top of it.
After installation all servers and components were up and running.
Server manager does shows siebel server connected but webclient was not working giving server busy error message.

Changes

Fresh Installation.

Cause

After investigation it was found, there was incorrect host name entry for siebel server in siebns.dat file.

Eapps.cfg from webserver/bin showed below connect string:

siebel.TCPIP.None.None://<siebel_server>:2321/<enterprise_server>/<OM_alias_name>

Siebns.dat showed below value:
[/enterprises/<enterprise_server>/servers/<siebel_server>/parameters/Host]
Persistence=full
Type=string
Value="10.6.4.36" (<value is just for representational purpose only>)
Length=18

In connect string for OM from eapps.cfg, string 'siebel_server' should refer to machine name (hostname) where siebel server resides. And that is why, the request was never reaching to SCBroker (port 2321)

Solution

Updating Proper hostname (and not IP) for siebel server resolved the issue.

Applies to:

Siebel eCommunications - Version: 8.0.0.3 [20416] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

==== ODM Issue Clarification ====

On : 8.0.0.10 [20436] version, System Admin

When attempting to start siebel apps server after patching to 8.0.0.10,
the following error occurs.

ERROR
-----------------------
GenericLog GenericError 1 000092164eeab1a0:0 2011-12-15 20:36:11 (sccnmsys.cpp (1305) err=2883609 sys=0) SBL-SCC-00025: No value found in the Gateway. Default value in the repository is used.
ror 1 0000369c4eea7146:0 2011-12-15 20:54:48 (schedule.cpp (944) err=1376408 sys=0) SBL-SMI-00152: TIMEOUT Component initialization for priority level 2 timed out after 300 s.
GenericLog GenericFatal 0 0000369c4eea7146:0 2011-12-15 20:54:48 (schedule.cpp (955) err=1376407 sys=0) SBL-SMI-00151: System component initialization timed out. System will shut down.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Patch from 8.0.0.3 to 8.0.0.10FP
2. Start enterprise
3. Not starting the enterprise

Cause

After further investigation, it was found that home directory for the siebel user was pointing to a wrong directory path other than the directory having the siebel server installed

Solution

Resolution steps :

1. Home directory for the siebel user must point to same directory where siebel installed
2. Once point to correct directory restart the enterprise