Applies to:

Siebel System Software - Version 8.0.0.1 [20408] to 8.2.2.2 SIA[23016] [Release V8]
Information in this document applies to any platform.
Product Release: V8 (Enterprise)
Version: 8.0 [20405]
Database: Oracle 10.1.0.4
Application Server OS: Red Hat Linux 4.0
Database Server OS: Sun Solaris 9

This document was previously published as Siebel SR 38-3467659813.

Symptoms

Hi, we're trying to setup a PoC of Siebel 8.0 on Linux Redhat 4.0 and had encountered issue while trying to config LDAP authentication and an error had ocurred in the OM log file. IBM LDAP 6.0 Client is installed and is using OID 10.1.2 as the LDAP Server.

We have repreatedly verified LDAPparameters many times and believed we have setup the right parmeters.

We got the following error in the log file:

SBL-SEC-00102 An error occurred loading the security adapter library. Please contact your system administrator for assistance.

SBL-DAT-00562 An error occurred loading the security adapter library. Please contact your system administrator for assistance


Btw, logfile and siebns are attached for your reference..

Cause

Change Request 12-1LDF7SJ

Solution

Message 1

Please assign this SR as soon as possible. This is becoming critical for the customer .

Many Thanks

Message 2

For the benefit of other readers

The customer was implementing LDAP authentication with Siebel 8.0 on Red Hat Linux 4.0 with Oracle Internet Directory.

After configuring the LDAP Adapter and restarting the Siebel Server the Object Manager startup would fail with the following errors:

GenericLog GenericError 1 0000000646fb2542:0 2007-09-27 20:38:39 (secmgr.cpp (2407) err=4587622 sys=0) SBL-SEC-00102: An error occurred loading the security adapter library. Please contact your system administrator for assistance.
ObjMgrSessionLog Error 1 0000000646fb2542:0 2007-09-27 20:38:39 (physmod.cpp (9244)) SBL-DAT-00562: An error occurred loading the security adapter library. Please contact your system administrator for assistance.
ObjMgrSessionLog Error 1 0000000646fb2542:0 2007-09-27 20:38:39 (model.cpp (5867)) SBL-DAT-00562: An error occurred loading the security adapter library. Please contact your system administrator for assistance.
ObjMgrCTLog Error 1 0000000646fb2542:0 2007-09-27 20:38:39 (ctxtmgr.cpp (4492)) SBL-SVC-00208: Please login first.

The customer confirmed that the IBM LDAP Client 6.0 was already installed. After further investigation it was found that the LDAP Client libraries needed to be added to the LD_LIBRARY_PATH set in /siebsrvr/siebenv.sh. siebenv.sh was modified as follows:

[....]

Message 3

[....]

if [ a${LD_LIBRARY_PATH} = ${LD_LIBRARY_PATH}a ] then LD_LIBRARY_PATH=${SIEBEL_ROOT}/lib:${SIEBEL_ROOT}/lib/odbc/merant:/opt/ibm/ldap/V6.0/lib:${MWHOME}/lib:${SQLANY}/lib:/usr/lib
else LD_LIBRARY_PATH=${SIEBEL_ROOT}/lib:${SIEBEL_ROOT}/lib/odbc/merant:/opt/ibm/ldap/V6.0/lib:${MWHOME}/lib:${SQLANY}/lib:/usr/lib:${LD_LIBRARY_PATH}
Fi

After making this change LDAP Authentication worked correctly. Change Request 12-1LDF7SJ was logged for a documentation defect.

Applies to:

Siebel CRM - Version 7.5.3.4 [16180] and later
Information in this document applies to any platform.
*** Checked for relevance on 29-JAN-2013 ***

Symptoms

Customer is trying to implement the LDAP security adapter (LDAPSecAdpt) for use with the Siebel application.  The application object manager is failing to bring up a login screen and the following error is appearing in the log file:

SBL-SEC-00102: Error loading the security adapter library. Please contact your system administrator.

The desired behavior is that the security adapter library should load successfully and a login page be presented to the user.

Cause

This behavior occurred because the server had to be physically rebooted after the installation of the IBM LDAP Client and/or GSKit software.

Solution

After some investigation, we determined that it is necessary to physically reboot the server after the installation of the IBM LDAP Client or GSKit software. Once this was done, everything worked correctly.

This requirement is not documented in the Siebel Bookshelf documentation.
Document Enhancement Request Bug:10575898/ 12-1UX6R4P to update the Security Guide with this information.

Applies to:

Siebel Financial Services CRM - Version 8.0.0.1 [20408] to 8.1.1.2[21215] [Release V8]
Information in this document applies to any platform.
***Checked for relevance on 03-Jan-2011***
***Checked for relevance on 23-Nov-2012***

Symptoms

We are trying to implement a Custom Security Adapter to perform application login authentication. We have downloaded the sample SDK from support web, compiled and deployed to our testing environment. We have also configured one of the AOM to test out the compiled security adapter. Unfortunately, we are unable to load the application login page. Based on the attached log file, the error message is as below:

"SBL-SEC-00102: An error occurred loading the security adapter library. Please contact your system administrator for assistance."

Cause

Incorrect setup/configuration on the custom security adapter named subsystem and configuration file or security adapter library compilation issue.

Solution

Verify the following is correct.
- Parameter setting in custom security adapter named subsystem
- Setting in the configuration file reference in ConfigFileName parameter in custom security adapter named subsystem
- LIBPATH environment variable setting

Setup the sdk custom adapter authentication and configuration in-house and successfully reproduce the issue when using the same compiler (g++) and makefile as customer.
Further research on these and found the issue on the sdk compilation. The makefile from customer is like this.

libsampsdk.so: secsamp.o secutil.o
g++ secutil.o secsamp.o -o libsampsdk.so

secsamp.o: secsamp.cpp secutil.h ssecurity.h
g++ -c secsamp.cpp

secutil.o: secutil.cpp secutil.h ssecurity.h
g++ -c secutil.cpp

Note that after compiling the secsamp.cpp and secutil.cpp with g++ -c swtich and option, it will create the .o file. Once this dependencies (secsamp.o and secutil.o) for the shared object secsamp.so have been created, there is need to invoke the linker using additional switch and option to create a dynamic library. So modify the makefile as below and recompile the sample code.

libsampsdk.so: secsamp.o secutil.o
g++ -fPIC -shared secutil.o secsamp.o -o libsampsdk.so

secsamp.o: secsamp.cpp secutil.h ssecurity.h
g++ -c secsamp.cpp

secutil.o: secutil.cpp secutil.h ssecurity.h
g++ -c secutil.cpp

Using this newly compiled library file, object manager and application succesfully loaded and login works fine.

pplies to:

Siebel Communications Service - Version 8.0.0.2 [20412] to 8.1.1.8 SIA [23012] [Release V8]
Information in this document applies to any platform.

Symptoms

Siebel version 8.0 application does not start when the LDAP security adaptor is configured at enterprise level, although the mandatory IBM LDAP client version 6.0 has been installed. The following error messages are logged as a result,
a) SBL-SEC-00102: An error occurred loading the security adapter library. Please contact your system administrator for assistance.
b) SBL-DAT-00562: An error occurred loading the security adapter library. Please contact your system administrator for assistance.

Cause

The Siebel security adaptor library aka. libsscfldap.so could not be loaded because of the installation and configuration (LD_LIBRARY_PATH) of the 64bit libraries that are part of the IBM LDAP client software.

Solution

Ensure that the LD_LIBRARY_PATH in the siebenv.sh shell script only references the 32-bit libraries of the IBM LDAP Client version 6.0 because this ensures that the Siebel modules, which are based on 32-bit processing - do not conflict with the 64-bit library versions of the IBM LDAP Client software - as documented in Siebel Bookshelf version 8.0 > Siebel Security Guide > Security Adapter Authentication > Installing LDAP Client Software > Configuring the siebenv.csh and siebenv.sh Scripts for the LDAP Client - where it states, "Siebel supports only the IBM 32-bit LDAP Client so you can use only the 32-bit LDAP Client libraries with your Siebel applications."

Please follow the following steps, also outlined in the Siebel Bookshelf reference,
1) Navigate to the Siebel server root installation directory
2) Open a text editor on your UNIX system e.g. vi
3) For both the shell script files; SIEBENV.SH and SIEBENV.CSH edit them and ensure that ONLY the location to the IBM LDAP Client 32bit libraries are referenced.

NOTE: The 64-bit libraries can be explicitly identified from the directory path naming convention - that is,
32-bit  =  /opt/IBM/ldap/V6.0/lib
64-bit  =  /optIBM/ldap/V6.0/lib64

Applies to:

Siebel CRM - Version 8.0.0.1 SIA [20408] and later
Information in this document applies to any platform.

Symptoms

Siebel Login Page fails to display

ERRORS
1) The server you are trying to access is either busy or experiencing difficulties. Please close the Web browser, open a new browser window, and try logging in again.[08:22:46]
2) SBL-SEC-00102: An error occurred loading the security adapter library. Please contact your system administrator for assistance.

Cause

The IBM LDAP Client installation on UNIX defaults to /opt/ibm/ldap/V6.0.
The environment variables in the SIEBENV.SH referenced the wrong directory for the IBM LDAP libraries - namely /opt/ibm/ldap/v6.0/lib as opposed to /opt/ibm/ldap/V6.0/lib.
Because the resolution of filename paths on UNIX systems is case sensitive the difference between v6.0 and V6.0 caused the error.
Bug 14651929 has been logged requesting that the Security Guide be updated accordingly under Security Adapter Authentication > Process of Installing and Configuring LDAP Client Software > Configuring the siebenv.csh and siebenv.sh Scripts for the LDAP Client.

Solution

Modify the SIEBENV.SH to reference /V6.0/lib as opposed to /v6.0/lib

Applies to:

Siebel CRM Call Center - Version: 8.1.1.5 [21229] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

=== ODM Issue Clarification ===
This is in relation to a 8.1.1.5 siebel enterprise environment deployed on a RHEL 5.5 linux platform (64-bit).


When accessing the EAIObjMgr_enu component fails when using an external Java based command line utility, which is accessing the EAI component via EAI_enu SWSE web server.

Looking at the EAIObjMgr component we can see mainly authentication errors like the following error messages:
"An error occurred loading the security adapter library. Please contact your system administrator for assistance.(SBL-DAT-00562)" and before this error ".....err=4587622....SBL-SEC-00102..."

Cause

=== ODM Cause Determination ===

Executed: strace against start_server and EAI OM PID. There was no evidence that <custom adapter>.so lib was loaded.

Executed: file <custom adapter>.so
This showed: ELF 64-bit LSB shared object, AMD x86-64, version 1 (SYSV), not stripped

Executed: ldd -v <custom adpater>.so
This showed:
>>>
      libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00002b536dd51000)
      libm.so.6 => /lib64/libm.so.6 (0x00002b536e051000)
      libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00002b536e2d4000)
      libc.so.6 => /lib64/libc.so.6 (0x00002b536e4e3000)
      /lib64/ld-linux-x86-64.so.2 (0x0000003d04c00000)

      Version information:
      ./cdetsnopassword.so:
              libc.so.6 (GLIBC_2.2.5) => /lib64/libc.so.6
...
<<<

=== ODM Cause Justification ===

Looking at the file and ldd output, we can see that 64-bit libraries are used:

Siebel product is only 32-bit and will only work with 32-bit libraries.

Solution

=== ODM Solution / Action Plan ===

Compile the custom security adapter as per SDK documented compile commands.
Also ensure that modifications are implemented as per published article: 1062497.1 - Changes to Siebel Custom Security Adapter SDK in Siebel 8.1.1
Also, if on a 64-bit operation system,  ensure to modify the compiler instructions to compile in 32-bit mode. There could be different ways this can be done pending on the OS vendor. For any clarification please consult with the OS vendor support.

In this specific case the following compiler instructions helped to resolve the issue.
g++ -m32 -c -fPIC secsamp.cpp
g++ -m32 -c -fPIC secutil.cpp
g++ -m32 -fPIC -shared secutil.o secsamp.o -o <custom security adapter>.so
Please note, Oracle  is providing the SDK and compiler instructions solely as a convenience to our customers and
Oracle  makes no warranties or representations of any kind regarding the
results customers may achieve by using the SDK. Siebel is not responsible
for any failure of any security adapter written using the SDK.

Check with file and ldd command (library dependency check on Linux) to ensure no 64-bit library is being used.
For example in this case the output after compiling in 32-bit mode confirmed that there was no 64-bit library involved.
$ ldd <custom security adapter>.so
linux-gate.so.1 =>  (0xffffe000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xf7e82000)
libm.so.6 => /lib/libm.so.6 (0xf7e5b000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xf7e4f000)
libc.so.6 => /lib/libc.so.6 (0xf7d09000)
/lib/ld-linux.so.2 (0x00473000)

Stop the siebel application server service.
Replaced this on the siebsrvr/lib
Start the siebel application server service

Test the siebel application authentication process.

Applies to:

Siebel Reports - Version: 8.1.1 [21112] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

Customer migrated some BI Publisher reports to another environment, these reports worked on the original environment without issues, but when they migrated to the new system one of them stopped working.

When the report is submitted an "Asynchronous Server Requests" windows appears with following text:



When checking the report execution in "My BI Publisher Reports" this reports status is displayed as "Error".

Cause

Analyzing XMLPReportServer log files displayed the following entries:



After some researching in the BI Publisher logs we could find the root cause for this issue in the following entries:




Most relevant entry of the aforementioned error are the following entries:




This clearly states that this report is not being generated since this getCanonicalDate function is missing from the XSLFunctions library.

Note 764191.1 includes a technical note about an updated XSLFunctions library that includes this new method. Following there is an excerpt from this document detailing this new function:


Therefore this error might trigger when a report containing a reference to this getCanonicalFunction is developed in or migrated to an environment that does not have this updated library.

Solution

Note 764191.1 includes an updated version of this XSLFunctions library in the link "Standard function library including canonical date function" that includes this new getCanonicalDate function as well as other new functions, this new library must replace the old XSLFunctions.jar file in BI Publisher deployment under ORACLE_HOME/oc4j_bi/j2ee/home/applications/xmlpserver/xmlpserver/WEB-INF/lib.

Following steps are necessary in order to replace this library:

- Shutdown BI Publisher server.
- Download this new library from Note 764191.1 in <ORACLE_HOME>/oc4j_bi/j2ee/home/applications/xmlpserver/xmlpserver/WEB-INF/lib replacing the old library.
- Start your BI Publisher server.
- Test the report.

References

NOTE:1051319.1 - Troubleshooting problems with the Siebel BI Publisher integration
NOTE:764191.1 - Siebel Reports 7 Migration Guide for Reports Developers

Applies to:

Siebel CRM - Version: 8.1.1 SIA [21111] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

When clicking the custom report from the reports menu on the Mobile Client, message is displayed: "BI Publisher engine failed to generate report (SBL-RPT-50524)".

siebel.log shows following errors:
XMLPReportLog XMLPReportError 1 000000024b180b84:0 2009-12-04 10:29:53 Error in generating xsl file C:\Siebel\81\Client_1/xmlp/templates/QuoteHeader.xsl in the XMLP Engine

ObjMgrBusServiceLog Error 1 000000024b180b84:0 2009-12-04 10:29:53 (xmlpadaptersvc.cpp (518)) SBL-RPT-50524: BI Publisher engine failed to generate report.

XMLPReportLog XMLPReportError 1 000000024b180b84:0 2009-12-04 11:40:13 Report Output file C:\Siebel\81\Client_1/xmlp/reports/Quote_1J-C2.PDF is having zero bytes.

Cause

Generating xsl file was failed in the XMLP Engine and this lead to the "SBL-RPT-50524: BI Publisher engine failed to generate report." error.

Solution

In Administration - BIP Reports > Report Template Registration > select Report Name and click "Generate Xliff" button on the Mobile Client.

This operation is only needed on the Disconnected mode.

For more details, please refer to the "Siebel Reports Guide Version 8.1, Rev. A August 2009 > Creating Reports > Process of Creating Custom Reports"

Applies to:

Siebel Reports - Version: 7.7.2.12 SIA[18393] to 7.7.2.12 SIA[18393] - Release: V7 to V7
Information in this document applies to any platform.

Symptoms

When running a report under Siebel 7.7.2.12 which is based on a dataset of over 100 records the resulting report generation will fail with an error :


A review of the contents of the BI Publisher console will show the following errors :

Cause

This behavior is caused because the use of over 100 records results in the XMLPReportServer using the uploadChunk webservice call which uploads blocks of XML data to the BI Publisher. This is then combined to provide the full set of data for the report which is then processed.

In the scenario being described under Siebel 7.7.2.12 each of the chunks which is uploaded shows its own xml header which when merged results in an invalid set of xml data. A review of the xxx_fo_data_nn.xml file in the BI Publisher logging directory will show evidence of this as can be seen below :

xdo_051410_055152937_fo_data_12.xml


When BI Publisher parses the uploaded data it encounters these nested xml headers and reports an error in the console for each one encountered :


and following on from this the aforementioned java stack will be reported.

Solution

A Change Request #12-1Y6LL71 "BI Publisher generates an error when a report includes over 100 records under 7.7.2.12" has been raised for this behavior. This request will be reviewed, analyzed, and prioritized for possible inclusion in a future release of the application.

In order to avoid this behavior reports should be restricted to less than 100 records.

Applies to:

Siebel Reports - Version 8.1 [21039] and later
Information in this document applies to any platform.

Symptoms

When running a BI Publisher report from the Siebel web client and having selected an output format for the report an error message is returned :
 If you then navigate into the Site Map > BIP Reports Server > My Reports and try to drilldown on the generated report a different error is returned :

Cause

Having increased the logging levels on the XMLP Report Server component, restarted it, and then re-tested the behavior it was evident from a review of the log file that the timeout errors were occurring because the XMLP Report Server component was unable to connect to the BI Publisher Server within the Timeout period. Evidence of this can be seen in the log file excerpt below :



The following additional error message may also be reported in some scenarios :

Solution

As the connectivity to the BI Publisher Server had previously been tested and confirmed as working correctly it was recommended to add some additional code to ensure that the last connection had been cleaned up correctly.
The following actions were performed :
1. In Siebel Tools modify the vanilla 'EAI HTTP Transport' business service.
2. Right click on the name of the business service and select 'Edit Server Scripts'.
3. Copy paste the following script in the 'PreInvokeMethod' event:


4. Compile the modified business service and deploy the SRF to your application server. If you have multiple Siebel Application servers then deploy the SRF to all the servers.

5. Test running the BIP reports.
The piece of code provided initiates a connection closure BEFORE calling the 'SendReceive' method and in this way it ensures that there are no stale or dead connections. The code has been written in the 'PreInvokeMethod' method which therefore gets executed before the actual 'SendReceive method is called.
ALTERNATE SOLUTION
1. Create a new 'System Preference' by navigating to Site Map > Administration Application > System Preferences view

System Preference Name	System Preference Value
BIPServer	http://[BIPServerHostname:9704]/xmlpserver/services/PublicReportService_v11

2. Create a new field in the following Business Component:

Business Component Name	Personalization Profile
Field Name	BIP Server
Calc Flg	Y
Calc Value	SystemPreference("BIPServer")

 3. Add the code in EAI HTTP Transport business service:
 

pplies to:

Siebel Reports - Version 8.0.0.10 SIA [20436] and later
Information in this document applies to any platform.

Symptoms

When attempting to run BI Publisher Report,
the following error occurs:

In XMLP Report Server log the following error is shown:


xdo.log shows the following error:
---------------------------------

Cause

The issue is caused because of the incorrect references to the Integration Component Fields in rtf template.

rtf template ->field Properties -> show the code = "<?ref:xdo0008?>"

So the report generation failed and xdo.log shows the error "<Line 34, Column 86>: XML-22008: (Error) Namespace prefix 'ref' used but not declared."

Solution

1) Open the rtf template using BI Publisher Desktop
2) Load Sample XML
3) Click on 'Add Ins' Menu > Tools > Field Browser
4) Here, we can see all the fields and their codes.
5) Check for any entries similar to <?ref:xdo0007?>
6) Here, it was observed that the field (ssAccount) -> Right Click -> BI Publisher -> Properties -> had the entry -> (<?ref:xdo0007?>).
7) This is an invalid reference.
8) Correct the invalid references (to exact field name) in rtf template
9) Re-upload the report from Siebel and generate the report.

Applies to:

Siebel Reports - Version: 7.5.3 [16157] and later   [Release: V7 and later ]
Information in this document applies to any platform.
Error Message Area:Reports - RPT
Version:Siebel 7.5.3

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-RPT-00134: Could not connect to the Report Server. Please contact your administrator. Status : %1

Scope

This document is informational and intended for any user.

SBL-RPT-00134: Could not connect to the Report Server. Please contact your administrator. Status : %1

Explanation

1. When using the Siebel Web client, the Siebel Server cannot access the Actuate e.Reporting Server machine using the host name or port specified.

2. The Actuate e.Reporting Server service is not running.

3. When attempting to synchronize a user from the Siebel application to the Actuate e.Reporting Server, the error displays. Sometimes, this is a symptom of another root cause; for example, if the Actuate Server Report Server Host parameter is not set correctly and you attempt to synchronize user(s), the error displays.

4. The EnableReportServer configuration parameter is not set correctly.

5. The local environmental variable does not have the appropriate locale with the appropriate character encoding set. NOTE: This is specific to UNIX platforms.

Corrective Action

1. Verify the Actuate Server Report Server Host parameter. Navigate to the component parameters of the appropriate object manager. For example, in Siebel application version 7.7, navigate to Administration - Server Configuration > Servers > (select server) > Components > (select object manager) > Parameters. Locate the Actuate Server Report Server Host parameter and verify the value.

You may also try to ping the machine to verify connection.

NOTE: The case (capitalization) of some parameters related to Actuate could affect the connection from Siebel to the Actuate e.Reporting Sever.

For more information, refer to:
- Siebel Bookshelf version 7.7 > Siebel Installation Guide for (select Microsoft Windows or UNIX): Servers, Mobile Web Clients, Tools > Installing the Siebel Reports Server > Postinstallation Tasks for the Siebel Reports Server > Enabling the Siebel Reports Server with the Siebel Web Client.

- Siebel Bookshelf version 7.5.3 > Siebel Reports Administration Guide > Installing the Siebel Reports Server for (select Microsoft Windows or UNIX) > Postinstallation Tasks for the Siebel Reports Server > Enabling the Siebel Reports Server with the Web Client

2. Verify that the Actuate Process Management Daemon service is started correctly. In Actuate Management Console, log in to System Administration with user name Administrator and the password defined during the installation. Click System and verify that the system is currently online. In some cases, the system is not online even though the service is up and running. In this case, re-enter the license key into the startup parameter and start the service.

3. Re-synchronize the users by navigating to Site Map > Reports Server > User Administration, select the user and click Synchronize One. Supply the user name and password.

You may also try to delete the user on the Reports Server, re-create the user, and then attempt to synchronize the user in the Siebel application.

For more information, refer to:
-Siebel Bookshelf version 7.7 > Siebel Installation Guide for (select Microsoft Windows or UNIX): Servers, Mobile Web Clients, Tools > Installing the Siebel Reports Server > Postinstallation Tasks for the Siebel Reports Server > Synchronizing Siebel Users to the Reports Server.

-Siebel Bookshelf version 7.5.3 > Siebel Reports Administration Guide > Installing the Siebel Reports Server for (select Microsoft Windows or UNIX) > Postinstallation Tasks for the Siebel Reports Server > Synchronizing Reports Server Users.

4. Verify the configuration parameter, EnableReportServer, is set to True in the appropriate configuration file.

For more information, refer to:
-Siebel Bookshelf version 7.7 > Siebel Installation Guide for (select Microsoft Windows or UNIX): Servers, Mobile Web Clients, Tools > Installing the Siebel Reports Server > Postinstallation Tasks for the Siebel Reports Server > Enabling the Siebel Reports Server with the Siebel Dedicated Web Client.

-Siebel Bookshelf version 7.5.3 > Siebel Reports Administration Guide > Installing the Siebel Reports Server for (select Microsoft Windows or UNIX) > Postinstallation Tasks for the Siebel Reports Server > Enabling the Siebel Reports Server with the Dedicated Web Client.

5. Verify the local environmental variable is set with the appropriate character encoding.
Here are two examples of setting the locale on UNIX platforms.

Example 1:
$ export LANG=en_US
$ export LC_ALL=en_US

Example 2:
$ export LANG=fr_FR.UTF-8
$ export LC_ALL=fr_FR.UTF-8

Applies to:

Siebel Reports - Version: 7.5.3 [16157] and later   [Release: V7 and later ]
IBM AIX on POWER Systems (64-bit)
Product Release: V7 (Enterprise)
Version: 7.5.3 [16157] ESN
Database: Oracle 9.2.0.4
Application Server OS: IBM AIX 5L 5.1
Database Server OS: IBM AIX 5L 5.1

This document was previously published as Siebel SR 38-1311489706.

Symptoms

SBL-RPT-00134We still have problems trying to run reports from Web Client (but it works from Dedicated Client). We get the errror: Could not connect to the Report Server. Please contact your administrator. Status:<?> SBL-RPT-00134

We have seen SR 38-1087004561 where it says that the problem was due to a Locale issue, Could you tell us the correct settings for locales?do we need to change (or export) some parameter on AIX where Report Server is running?

Thanks in advance.

Cause

Configuration/ Setup

Solution

Message 1

For the benefit of other readers.

Customer found on SupportWeb SR 38-1087004561 where it says that the problem was due to local environmental variables that were not set correctly on their Sun Solaris environment and wanted to know if this also apply to AIX environment.

It was found that the error message was also due to the same behavior on AIX where the Local variables were not set correctly on the two machines used.

One machine was hosting the Siebel Server and the other one was hosting the Report Server.

The behavior was resolved after installing UTF filesets on both machines and establishing LANG and LC_ALL variables to ES_ES.UTF-8

Thank you and regards,

Applies to:

Siebel Reports - Version: 7.5.2.7 [15058] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.2.7 [15058]
Database: Microsoft SQL Server 2000 SP 2
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: Microsoft Windows 2000 Server SP 3

This document was previously published as Siebel SR 38-958790951.

Symptoms

SBL-RPT-00134We just upgraded this development environment to version 7.5.2.200 and installed Actuate 6.0 SP1. I am trying to synchronize the Reports Administrator, but am getting connection errors as described in the attached document.

Cause

Configuration/ Setup

Solution

Message 1

For benefit of other readers:

Customer tried to synchronize the Reports Administrator, but he received the following error message:
“Could not connect to the Report Server. Please contact your administrator. Status: ERROR_UNKNOWN_ERROR”

Reviewing his Object Manager parameters related to Report Server it was found that the Actuate Server Report Server Host was not set correctly according to Bookshelf > Siebel Reports Administration Guide > Installing the Siebel Reports Server for Microsoft Windows > Postinstallation Tasks for the Siebel Reports Server.

It was set as followed:
Actuate Server Report Server Host = DEV-SRS.qa.uone.shippers.com:8000 whereas it should be set
Actuate Server Report Server Host = DEV-SRS:8000
as the.qa.uone.shippers.com is the domain name from Actuate Report Cast Domain parameter.

In some testing it was also found that the case of some parameters (related to Actuate) could affect the capability to connect from Siebel to the Report Sever.

From customer’s files, the installation had in some places capital letters (Actuate Report Server Host for example) and lower case in some others (volume name or FQDN in eapps.cfg)

Changing the installation to have consistent case enabled customer to resolve the behavior.

Thank you,
Siebel Technical Support

Message 2

Search Keywords: Synchronize One, Actuate connection, Report Administrator

Applies to:

Siebel Reports - Version: 7.7.2 [18325] and later   [Release: V7 and later ]
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Enterprise)
Version: 7.7.2 [18325]
Database: Oracle 9.2
Application Server OS: Sun Solaris 8
Database Server OS: HP-UX 11i

This document was previously published as Siebel SR 38-2051097151.

Symptoms

SBL-RPT-00134Error message in the UI is as follows



The following error messages are being generated from the Actuate Server logs:


We believe this may be related to changes that were made to the HTTP Protocol Business Service over the weekend. Please refer to SR#38-2010964841 under our account.

Solution

For benefit of other Users:

To close the EAI HTTP Transport connection after every usage, customer wrote a script on the PreInvokeMethod of 'EAI HTTP Transport' business service by setting HDR.Connection= "close" as an input property.

This caused the Actuate reports to fail with the message as :

For reports we invoke "EAI HTTP Transport" each time we sent a SOAP message to Actuate. So it is suggested that changes not be made in the "EAI HTTP Transport" business service.

Customer removed the script changes in the "EAI HTTP Transport" business service and reports worked fine after that.

Applies to:

Siebel Reports - Version: 7.7.1 [18306] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.7.1 [18306]
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2000 Server SP 4
Database Server OS: Microsoft Windows 2000 Server SP 4

This document was previously published as Siebel SR 38-1371599141.

Symptoms

SBL-RPT-00134Hello,

I am facing some serious problems with our Actuate deployment here.

We are running a multilingual system. Installed LEPs are ENU and DEU.
If I try to synchronize users with actuate in the DEU Client. I get an error message.

Error code: SBL-RPT-00134
Which states that a connection to the report server was not possible.

When I tried the sync in the ENU client everything works well.
After the users are synchronized with Actuate I can create reports in the ENU client but not in the DEU Client (Same Error Message). I face the same behaviour on our merged development system too

I searched knowledgebase for this error and got 2 hits. Both articles where about localisation issues. But unfortunately on Unix based servers.

Here is a detailed description of the Server configuration. I will also attache log files shortly.

OS: Win2k Srvr Sp4 ENU
Regional Setting: English(US)
Time Zone: GMT+1 Berlin

Siebel Vanilla installation with both LEPs on all Components (GTWY;DBSRVR,SRVR;RPRTSRVR)
Imported Sample Database over ODBC

Default language for actuate: german
Time zone: GMT+1

Please understand that this configuration will be pretty much the same on the production servers. The application will be hosted in germany. Most users will be german speaking. its mandatory to have a english operation system for security reasons. All parts of the application inclusive reports have to be available in german and english.

Further more the actuate HTTP service did not start after I patched the reportserver. I managed to get it running again after i deployed a backuped server.xml file in the apache/tomact conf folder.

Any suggestions?
Please provide me with a general aproach on how to configure reportserver in such an environment.

I am looking forward to your answer and advice

Cause

Configuration/ Setup

Solution

For the benefit of other users:

Customer was running Siebel environment with two languages English and German.
Also customer was trying to execute reports through Actuate Server.

Reports were successfully executed every time on English object manager but when run through German object manager following error would appear in the object manager log file:

ObjMgrLog    Error    1    0    2004-07-22 15:43:34    (port.cpp (107)) SBL-EAI-04297: Protocol '' for port 'ActuateSoapPort' is not supported.
ObjMgrLog    Error    1    0    2004-07-22 15:43:34    (wservice.cpp (146)) SBL-EAI-04307: No ports were initialized for Web Service named 'ActuateAPI' having namespace value 'http://schemas.actuate.com/actuate7/wsdl'.

After executing following SQL statement :

SELECT *
   FROM
       S_LST_OF_VAL T1
   WHERE
      T1.NAME LIKE 'SOAP_DOC_LITERAL'
   ORDER BY
      T1.TYPE, T1.ORDER_BY, T1.VAL
It was discovered that German seed data was missing from the database. After importing German seed data, reports could be executed from both object managers.

Thank you,

Applies to:

Siebel Reports - Version: 7.7.2.2 SIA [18356] and later   [Release: V7 and later ]
IBM AIX on POWER Systems (64-bit)
Product Release: V7 (Enterprise)
Version: 7.7.2.2 [18356] FRA Travel
Database: Oracle 9.2.0.6
Application Server OS: IBM AIX 5L 5.2
Database Server OS: IBM AIX 5L 5.2

This document was previously published as Siebel SR 38-2449311421.

Symptoms

We have finished to install and configure our Siebel Report Server but we have the following error when we try to synchronize our reports users :

In spite of this error, it's possible to connect to the Actuate Management Console.
After some research on My Oracle Support, we have found some solutions for this problem but they are not applicable in our case.

Could you help me to solve our problem?

Below, we can find some information about our environment configuration:
    * Actuate Server host name (with component Actuate Active Portal, Actuate Server and Actuate Management Console) : xxxxxxxx
    * Actuate Volume name : xxxxxxxx
    * We can find on the ActuateParameters_for_LoyObjMgr_FRA.xls file the Actuate parameter defined on our object manager
    * We can find on the SymbolicURL_Host.xls file the definition on our host in our environment
   
Best regards.

Solution

For the benefit of other readers:

This customer reported that they received the following errors when trying to synchronize Siebel Users on the Actuate Report Server: -

On further investigation, the following errors where found in the Object Manager Log file: -

This indicated that the Web Services were not activated for Actuate.

We asked the customer to complete the following steps: -

1) Login into Siebel and navigate to Site Map >> Administration - Web Services >> Outbound Web Services
2) In the “Namespace” column query for “'http://schemas.actuate.com/actuate7/wsdl” and check if the status is “Active”.
3) If not, set the Status to Active and then try and synchronize the user.The customer found that the Outbound Web Service for Actuate was not active and when this was enabled the Siebel Users synchronized as expected.

Further information on Outbound Web Services can be found in the section 'Outbound Web Services' of Chapter 'Web Services' of the 'Integration Platform Technologies: Siebel eBusiness Application Integration Volume II' document in Bookshelf.

Applies to:

Siebel Reports - Version: 7.7.2.3 SIA [18361] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.7.2.3 [18361] NLD Fin Svcs
Database: Oracle 8.1.7.4
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: HP-UX 11.0

This document was previously published as Siebel SR 38-2519044691.

Symptoms

SBL-RPT-00134, SBL-EAI-04005Dear support,

After installing the report server, I cannot synch the users.

Tried it from both dedicated and web client.

Attached the log file of our FINS NLD object manager.

Please advice.

Best regards,

Solution

For the benefit of other users:

Error message in English is :

To troubleshoot this issue, further information was required as follows:

1) Could customer login to the Report Volume named 'ZL9B' (in this case) via Actuate Management Console?
2) Had customer restarted the Siebel Server after setting parameters to enable the Report Server in Web Clients?
3) Can customer attach all Actuate logs located at Actuate7\Server\log directory as well as an export of the Object Manager parameters of which Actuate parameters have been set?

After checking this information: we recommended
1) Customer to only use CAPITALS for report server parameter values like:

2) to make sure the error occurs when attempting to synchronize a user, by conducting the following test:

a) Stop Actuate Services and move all Actuate logs to another directory.
b) Start Actuate Services and take a look at encycsrvr7* logs if the above error is logged.
c) Login to a Web Client and try to synchronize a user to the Report Server and then check encycsrvr7* logs again for the error.

3) To check if the host name ' ZL9B ' is recognizable in network, please do ping test with the host name only from the Siebel Server machine as follows:

ping ZL9B

If the ping test fails, I would like to suggest consulting your network administrator for the host name in DNS configuration.

By looking at the log file the following error message was also found:

We request customer to try the following: -

1) Login into Siebel and navigate to Site Map >> Administration - Web Services >> Outbound Web Services
2) In the “Namespace” column query for “'http://schemas.actuate.com/actuate7/wsdl” and check if the status is “Active”.
3) If not, set the Status to Active and then try and synchronize the user.


But in fact the test that helps resolving the issue was to test synchronization in the dedicated client using the standard srf, as in this case it works.

Later on customer removed some custom script and it resolved the issue

Applies to:

Siebel Reports - Version: 7.7.2 [18325] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Professional)
Version: 7.7.2 [18325]
Database: Oracle 9i
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: HP-UX 11i

This document was previously published as Siebel SR 38-1594415341.

Symptoms

SBL-RPT-00107, SBL-EAI-04308We have a workflow that runs in the WfProcMgr which calls the Reports Business Service to run and download a report to the server. We have set the Actuate parameters for the WfProcMgr correctly to use the FinsObjMgr for report generation through the connect string parameter. When we initially deploy the solution, everything worked correctly. However after time we started getting the following error:

I have logged into the thin client as sadmin (who the WfProcMgr runs as) and I can run the report with no problem by selecting it from the reports drop down so I know the report is there and that the privileges are set correctly.  The communication between the WfProcMgr and Actuate stops working and does not start working again until we restart the Siebel Server that is running the WfProcMgr component.

Solution

It was found that the error was because the Actuate "Authid" is expiring after 24 hours. After bouncing Workflow Process Manager this behavior disappeared.

Through investigation by enabling the workflow and EAI logging level, we can see the similar error error in the workflow log file:-

Also we can see the "login session has expired. Please login again" message with error 6035 code, indicating that that Actuate authid has expired.

Instead of calling the Workflow Process Manager to invoke the report business service, the workaround will be as follows :

1) Continue to use the workflow process manager by setting the AuthIdExpires to a large value and recycle the process when the limit is reached. The value is controlled by ""AuthIdExpires"" parameter in the \Server\etc\acmetadescription.xml file which has a default value of 24.

2) The second more elegant solution is to use the users session within an OM to execute and run the report business service. This will ensure that as long as the user session is active in the Siebel application they will be able to run reports

The behavior was eventually resolved by  :
1. running the Reports Business Services in the FINS Object Manager downloading that file and then creating an attachment record tied to an activity record with this report file.
2. Then call the WPM to run a workflow passing it the row id of the action record.
3. Then WF then queries for the action record and downloads the attachment to the WPM server.
4. Then creates the email with this file as an attachment.

Thank you.

Applies to:

Siebel Reports - Version: 7.7.2 SIA [18325] and later   [Release: V7 and later ]
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Enterprise)
Version: 7.7.2 [18325] Com/Med
Database: Oracle 9.2.0.4
Application Server OS: Sun Solaris 9
Database Server OS: Sun Solaris 9

This document was previously published as Siebel SR 38-1813637701.

Symptoms

SBL-RPT-00107HI,

We are currently not able to get a specific set of automatic Reports generated on the Production Environment.
The Reports need to be demonstrated and need to be working on the Production Environment.
There are 2 Report categories namely KCI2 & KCI345 which are trigerred using a Workflow Process.
The expected functionality is as follows:-

1) Create an Order with a specific set of Field values populated.

2) Order gets stamped with specific Product Cell values based on the transition of certain fields.

3) A Report is triggered in the Background using a Workflow Process & the Report PDF file should be created & stored in the File system on the Server.

4) An activity should be created for that Order to indicate success or failure for created Report.

5) Report should be attached to Activity.

6) Activity also involves sending E-mail to a particular email id with status of the Report Creation & the report attachment in case of success.

Solution

When running Actuate report from Workflow Process Manager (WPM) through Report Business Service after one day of running reports following error would show up in the WPM log files:

After this error reports could not be executed until WPM server component or Actuate services would be restarted.

After some research it was established that cause of this behavior is the “AuthIdExpires" parameter in acmetadescription.xml on the actuate server. Default value for this parameter is 24 (hours).
To resolve this behavior please set “AuthIdExpires" in acmetadescription.xml on the actuate server to high number (for example 6 months 180x24hours).

Also change request number 12-VS3X2J has been logged to address this behavior.

Applies to:

Siebel Reports - Version: 7.7.2.4 SIA [18365] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.7.2.4 [18365] FRA Pub Sect
Database: Microsoft SQL Server 2000 SP3
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: Microsoft Windows 2003 Server SP1

This document was previously published as Siebel SR 38-2729911481.

Symptoms

Hi

We have a particular error with our Workflow Process Batch Manager. It seems that the WfProcBatchMgr stops communicating with the report server. We get the following errors in the error logs :


To resolve this problem, we shutdown and restart the WfProcBatchMgr

Solution

The behavior that you are experiencing is being caused because the Actuate authid has expired after 24 hours. After getting the error, the user won't be able to run a report through the Workflow Process Batch Manager. The report can only be run again once a restart  of the Workflow Process Batch Manager or Siebel Server has been performed. A Change Request #12-VS3X2J has been raised for this behavior.

This authid expiration is controlled by a parameter called “AuthIdExpires" parameter in acmetadescription.xml on the Actuate server. Default value for this parameter is 24 (hours). To resolve this, please set “AuthIdExpires" in acmetadescription.xml on the actuate server to high number (for example 6 months 180x24hours

Applies to:

Siebel Reports - Version: 7.8.2 [19213] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Professional)
Version: 7.8.2.3 [19221] DEU
Database: Microsoft SQL Server 2000
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: Microsoft Windows 2003 Server SP1

This document was previously published as Siebel SR 38-3099876411.

Symptoms

We have the problem, that some reports work and some not.

If I call a report in the activities, it is well created.

If I call a Contact list report I only get a gray window an find the following error in the Object manager log file:

Solution

For the benefit of other readers,

The customer has installed a non-ENU environment (DEU) and the default setting for the report parameters under user preferences was set to ENU. After changing the appropriate parameters to DEU the report generation works fine.

Enhancement request 12-1FEVOP6 was filed to set the parameters to the installed language (in case there is only one installed).