Applies to:
Siebel CRM Call Center, SPE - Version: 8.1.1 [21112]Information in this document applies to any platform.
Symptoms
On : 8.1.1.2 [21215] version, Siebel EAIAfter installing fix pack 8.1.1.2 (8.1.1.2 [21215]) the error below occurs in the EAI Object Manager component when an Inbound Web Service is called.
Siebel configuration includes EAI Object Manager and Workflow Process Manager components set with DBSecAdpt (DB Security Adapter), while interactive Object Managers (e.g. Siebel Financials) are configured with LDAPSecAdpt (LDAP Security Adapter).
The issue is only affecting Inbound Web Services, and thus, the EAI Object Manager.
The issue is not observed in the Workflow Process Manager.
ERROR
-----------------------
"ObjMgrLog Error 1 0000186e4b981e30:0 2010-03-11 11:03:05 (oracon.cpp (3246)) SBL-DAT-00446: Você digitou um conjunto inválido de parâmetros de logon. Digite os parâmetros de logon novamente.
SQLParseAndExecute Execute 5 0000186e4b981e30:0 2010-03-11 11:03:05 ORA-01017: senha/nome do usuário inválido; logon negado"
Cause
After further tests in-house the issue was replicated and the cause was found in the setting of the parameter SingleSignOn=TRUE in the SWSE eapps.cfg configuration file.
The parameter SingleSignOn is actually defined for the Security Adapter being used in Siebel and thus, this parameter should be defined only for the Profile Named Subsystem used for the security adapter, in this case LDAPSecAdpt.
When this parameter is set in the SWSE eapps.cfg configuration file, this setting is affecting all the calls coming into Siebel through the Web Server and SWSE, including Web services invoking EAI Object Manager component. This is why the current configuration was affecting the Inbound Web Service calls to the EAI Object Manager.
Solution
In order to solve the issue consider these steps:a. Remove th line 'SingleSignOn=TRUE' from the eapps.cfg file.
b. In order to use Single Sign On for LDAP Security Adapter, set this parameter from a Siebel Client > Administration - Server Configuration > Profile Named Subsystem 'LDAPSecAdpt' > Parameters > Single Sign On.
NOTE: If this setting is required, consider to verify all the requirements for SingleSignOn in Bookshelf documentation > Security before applying the change, as this might affect login processes to Siebel applications if it is not correctly configured.
c. Restart Siebel Server and Siebel Gateway services.
d. Also restart IIS.
e. Repeat the validations by login into Siebel Financials and invoking the inbound web service.
Applies to:
Siebel System Software - Version: 7.7.2 [18325] to 8.0.0.7 [20426] - Release: V7 to V8All Platforms
This document was previously published as Siebel SR 38-1715068851.
Symptoms
We have configured password hashing as described in the Siebel Security Guide's section "Security Adapter Authentication: Configuring Password Hashing." After restarting the server and gateway, we were able to successfully login using a dedicated client with the clear-text password. However we are not able to connect using the web client and the following components were not running but had passed one or more of the errors listed below:
PDbXtract/DbXtract
SSEObjMgr_enu
WfProcBatchMgr
WfProcMgr
WfRecvMgr
SBL-DAT-00446, SBL-DCK-00164, SBL-GEN-04031, SBL-OMS-00102, SBL-OMS-00107, SBL-SEC-10018, SBL-SEC-10007, SBL-SVR-00040
Solution
Customer was implementing Password Hashing, and after changing parameter DSHashUserPwd in Server Data Source named subsystem to “TRUE” and restarting the Siebel environment, the following components did not start:
PDbXtract/DbXtract
SSEObjMgr_enu
WfProcBatchMgr
WfProcMgr
WfRecvMgr
WfRecvMgr, WfProcMgr, and WfProcBatchMgr had the following error messages:
SBL-SEC-10007: The password you have entered is not correct. Please enter your password again. (0x5a94))
SBL-SEC-10018: You have entered an invalid set of logon parameters. Please type in your logon parameters again.(SBL-DAT-00446)
SBL-SVR-00040: Internal: Informational, encrypted parameter. (0x5a8f))
SBL-OMS-00107: Object manager error: ([2] SBL-SVR-00040: Internal: Informational, encrypted parameter. (0x5a8f))
SBL-OMS-00107: Object manager error: ([1] SBL-SEC-10018: You have entered an invalid set of logon parameters. Please type in your logon parameters again.(SBL-DAT-00446)
ORA-01017: invalid username/password; logon denied
SBL-OMS-00107: Object manager error: ([0] SBL-SEC-10007: The password you have entered is not correct. Please enter your password again. (0x5a94))
SBL-OMS-00102: Error 23188 logging in to the application
SSEObjMgr had the following error messages:
SBL-DAT-00446: You have entered an invalid set of logon parameters. Please type in your logon parameters again.
SBL-SEC-10018: You have entered an invalid set of logon parameters. Please type in your logon parameters again.(SBL-DAT-00446)
ORA-01017: invalid username/password; logon denied
The above errors were resolved by setting the Password parameter for each component to the unhashed password for the SADMIN user and restarting the environment. Further information is available in the Siebel Bookshelf > Security Guide > Security Adapter Authentication > Configuring Password Hashing.
Components PDbXtract (during server startup) and DbXtract (at component task start) had the following error message:
SBL-GEN-04031: Internal: Error occurred during base64 decoding.
Error message SBL-GEN-04031 in PDbXtract and DbXtract log files occur because the password length is greater than 21 characters. If SADMIN password has more than 21 characters, PDbXtract and DbXtract components will fail with the error message.
The SADMIN password was hashed using the RSA SHA-1 encryption algorithm. When using SADMIN as password in test environment, the hashed password contained 28 characters. Since "SADMIN" is a fairly simple and short password, we would expect that most good passwords would result in RSA SHA-1 values that are too long.
Change Request 12-SQ798U has been opened to address this Product Defect.
The workaround is to change the Hashing algorithm to use Siebel Hash instead of RSA SHA-1. Siebel Hash will encrypt passwords with a length smaller than RSA SHA-1 algorithm. Please refer to the Security Guide for more information about how to change encryption algorithm.
Applies to:
Product Release: V7 (Enterprise)Version: 7.7.2 [18325]
Database: IBM DB2 7.1 FixPack 5se
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: IBM AIX 5L 5.2
This document was previously published as Siebel SR 38-1874173270.
Symptoms
SBL-DAT-00446, SBL-DAT-00468Hi,
I have successfully ran the Siebel 77 Db Install and found no errors in the log files,
but I can not access the application with the Siebel 77 client or Siebel 77 tools.
When I
start tools I get the error message:
-No records exist for the current
query.(SBL-DAT-00468)
The fat Client returns -. The user ID or password that you entered
is incorrect. Please check the spelling and try again.
I can connect fine using DB2 CAE or
WINSQL.
I will attach the Install logs ... when I get some time.
Solution
Message 1
For the benefit of others:Description:
New 7.7 database server was installed but neither Tools nor Dedicated Client can login.
Accessing Tools displays the message:
No records exist for the current query.(SBL-DAT-00468)
In the \web client\log\siebel.log we see the following errors:
7.7.2 [18325] ENU
GenericLog GenericError 1 0 2005-03-30 09:21:08 (secclnt.cpp (256) err=7010002 sys=0) SBL-SEC-10002: Cannot perform the requested operation due to an invalid security context. If you have already logged in, please try to log in again or contact your system administrator for assistance.
DBCLog DBCLogError 1 0 2005-03-30 09:21:08 SQLDriverConnect: DSN=kagpro, UID=sadmin
ObjMgrLog Error 1 0 2005-03-30 09:21:08 (clicon.cpp (3383)) SBL-DAT-00446: You have entered an invalid set of logon parameters. Please type in your logon parameters again.
DBCLog DBCLogError 1 0 2005-03-30 09:21:08 SQLError: sqlstate 08001: [IBM][CLI Driver] SQL30082N Attempt to establish connection failed with security reason "24" ("USERNAME AND/OR PASSWORD INVALID"). SQLSTATE=08001
GenericLog GenericError 1 0 2005-03-30 09:21:08 (secmgr.cpp (2265) err=7010018 sys=0) SBL-SEC-10018: You have entered an invalid set of logon parameters. Please type in your logon parameters again.(SBL-DAT-00446)
[IBM][CLI Driver] SQL30082N Attempt to establish connection failed with security reason "24" ("USERNAME AND/OR PASSWORD INVALID"). SQLSTATE=08001
(cont)
Message 2
(cont)Resolution:
Customer realized the pre-installation task of running GRANTUSR.SQL had not been run prior.
Applies to:
Siebel Remote - Version: 7.0.1 [10746-5] to 8.1.1 [21112] - Release: V7 to V8IBM AIX on POWER Systems (64-bit)
Product Release: V7 (Enterprise)
Version: 7.8.2.4 [19224] ARA Fin Svcs
Database: Oracle 10.2.0.2
Application Server OS: IBM AIX 5L 5.3
Database Server OS: IBM AIX 5L 5.3
Checked for Relevance on 22 Oct 2009
This document was previously published as Siebel SR 38-3245907661.
Symptoms
SBL-DAT-00446, SBL-SEC-10018, SBL-SEC-10007Dear sir,
I already populate the local database using the Siebel tools, but when I’m
trying to connect to the Siebel Financial Service – ENU connecting to the local database. It gave
me the error
The user Id or password that you entered is incorrect.
Please check the
spelling and try again.
Then the program crashes.
The same user ID and password I can
use with the Siebel tools and it works correctly
Another issue, when I try to use the
Siebel Financial Service – ENU as SADMIN to connect to the server database it gave me the same
error then the program crashes
Cause
- Corrupt Local Database in Siebel_Root\Client\Local directory- Wrong Database DLL and SQLStyle parameters in Server cfg file.
Solution
Message 1
For the benefit of other usersCustomer can connect fine from Tools to his local database and to the Server.
He cannot connect from his Application ("Fins") to either the local or the Server.
The log files have the error messages
"(SBL-DAT-00446) Invalid user ID or password"
"SBL-SEC-10007: The password you have entered is not correct"
"SBL-SEC-10018: Can't load sscddcli.dll"
1). We compared the sizes of the Tools local database and the Client local database, Tools local database is 700Mb and the Client Local database is only 70Mb.
I tried to log in locally to the Client database using DBISQLC. I could not login with the normal user name or DBA. I suspect that this database is corrupt and needs to be re-extracted.
Just to test the connection Customer copied the Tools database to the Client\local area and the fins client logged in correctly.
2). To resolve the connection issues with the Server Database we tested the Oracle Client connection. It works fine.
In the on the [ServerDataSrc] section of fins.cfg, we then changed the
DLL = sscddcli.dll
SqlStyle = DB2
to
DLL = sscdo90.dll
SqlStyle = Oracle
The Connection string from "SSD default instance" to the actual Oracle Service name and this resolved the issue there.
Thank You
Siebel Technical Support
Applies to:
Siebel Wireless - Version: 7.5.3.15 [16279] - Release: V7Siebel Handheld
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.3.15 [16279]
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2000 Advanced Server SP 3
Database Server OS: Microsoft Windows 2000 Advanced Server SP 2
This document was previously published as Siebel SR 38-3366649910.
Symptoms
Dear Siebel Suopport,One of our End Markets was using the 7.5.3.7 batchsync utlity with thin client version 7.5.3.13 SIA and HH version 7.5.3.13
Now EM has upgraded thin client version to 7.5.3.15 SIA and getting problem in running Batchsync utility with following error message:
12:03:58 U5301423 Filters sucessfully set.
12:03:58 U5301423 Beginning Database Extract
12:04:00 U5301423 End Database Extract :
<html><head><title>Message:</title></head>
<body>The server you are accessing is either busy or experiencing
difficulties. Please close the web browser, start a new one and try logging
in again. For further support, please copy and send the full message text
to your system administrator.[12:04:00]
<p>
12:04:00 U5301423
http://mxmydv02/cgce_enu/start.swe?SWEExtSource=siebelpda&SWEExtCmd=Logoff
12:04:01 U5301423 Logged out.
12:04:01 U5301423 Total Sync Time 16438 ms
Could you please let us know if this is happening because of version conflict of batch sync utility and thin client version.
If yes, Please let us know the compatible version of the batch sync utility for thin client version 7.5.3.15 SiA and how to download the same.
Warm Regards
Cause
Change Request# 12-17AVPKHSolution
Message 1
For the benefit of others:The customer has upgraded the server environment from 7.5.3.13 to 7.5.3.15 and ever since, the Batchsync TAM tool they used, started to return errors.
When the handheld synchronization with 'Full Sync' option runs fine in same environment, then it is strictly to be related to BatchSync and this was the case here.
This TAM tool is built along with each Siebel release (build), so from one version to another differences might occur. However, providing via TAM the correct one for build 7.5.3.15 [16279] did not help stopping the errors either.
Further investigating BatchSync settings, BatchRepository.ini file, CGCEObjMgr and SWSE log files with increased logging showed that:
1- in SWSE log (ss070607.log):
[6244] ERROR 6244: [SWSE] Error Child Messages : <0> You have entered an invalid set of logon parameters. Please type in your logon parameters again.(SBL-DAT-00446)<1> ORA-01017: invalid username/password; logon denied
[6244] ERROR 6244: [SWSE] HTTP Status 500 : Error The service request could not be processed. Please check that the user name and password are correct, and that the request format is correct.
2- BatchSync.070607164858.log:
set-cookie: _sn=EtRMxUCb-HEFNuGiRJpB8qJ5ddy9XFrBfPJMDkSOlQw_; Version=1; Path=/cgce_enu
16:48:59 PROS1 Initializing
...
16:49:00 PROS1 Error parsing Init XML stream. <SyncInfo> not found!
[Cont...]
Message 2
[... cont.]3- all the CGCE* logs when BatchSync was run show:
ObjMgrDataObjLog Logon 4 2007-06-07 16:49:00 DataBase Connection Object was created 12fa75b0; DB User: ''; Connection Id:
...
GenericLog GenericError 1 2007-06-07 16:49:00 You have entered an invalid set of logon parameters.
As opposite, the CGCE logs when the FullSync is used show: "DataBase Connection Object was created 130f1eb0; DB User: 'PROS1'; Connection Id: "...
It was found that a similar issue was originally detected in 7.7.2.x - and Change Request# 12-17AVPKH was logged for this.
Mainly, that was caused by the fact that formerly, cookies were sent out with a prefix of "Set-Cookie: ", but this has changed to all lower case, i.e. "set-cookie:". Batchsync.exe was changed to detect in the same way the cookies set.
The issue was fixed in 7.7.2.5 Fix Pack and 7.8.2.2 Fix Pack for those versions (7.7, 7.8).
Fix Request #12-1JSH9XD was logged to address the same in the next 7.5.3.x Fix Pack. For this customer a QuickFix was also made available.
Kind Regards,
Marius Milos
Oracle | Siebel Technical Support
Keywords: handheld, BatchSync, SBL-DAT-00446, Error parsing Init XML stream.
Applies to:
Siebel CRM - Version: 8.1.1.1 SIA [21211]Information in this document applies to any platform.
Symptoms
As per Note 531046.1 "Deploy SRF without shutting down the server">> the bellow srvrmgr commands are used to change the parameter of a component:
srvrmgr > change parameter <parameter>=<new value> for compdef <compdef name>
srvrmgr > commit reconfig compdef <compdef name>
On Siebel 8.x, after executing the above commands, the component becomes Unavailable after 3-4 minutes. Then, the only workaround is to restart Siebel and Gateway services.
The following errors are displayed in the log files:
SBL-SEC-10007: The password you have entered is not correct. Please enter your password again.
SBL-DAT-00569: The password you have entered is not correct. Please enter your password again.
SBL-OMS-00107: Object manager error: ([0] The password you have entered is not correct. Please enter your password again.(SBL-DAT-00569)
Note that the reconfig command works fine with Interactive Components, i.e: SCCObjMgr_enu and EAIObjMgr_enu. The components do not become Unavailable after the changes.
However, most of Batch components become Unavailable after the changes, i.e: WfProcBatchMgr,WfProcMgr, WfRecvMgr.
Cause
This behavior is reported in Bug 12-1SM2JS1 "Deploying new SRF with zero downtime on windows".Solution
Currently, there's no workaround for this behavior.If the value of any parameter of a component is changed, it's necessary to restart Siebel and Gateway services.
Applies to:
Siebel Remote - Version: 7.7.2.6 [18372] - Release: V7z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Professional)
Version: 7.7.2.6 [18372]
Database: Oracle 9.0.1.2
Application Server OS: Microsoft Windows 2000 Advanced Server SP 4
Database Server OS: HP-UX 11i
***Checked for relevance on 09-Oct-2009***
This document was previously published as Siebel SR 38-3405694171.
Symptoms
Hi,In production we have deployed Siebel remote. We have given a provision to the remote user to change the password.
Whenever remote user has changed the password, Auto sync is NOT working and system is throwing an error as "Password you have enter is incorrect" ( Please find the enclosed screen shot)
Please provide your inputs.
Cause
For the benefit of other readers,The customer reported that they encounter tricklesync errors after they change their password on the local database following the steps in 'Handling Forgotten SQL Anywhere Passwords (Siebel Remote Password Management) (Doc ID 475579.1)'.
The syncthrd logs contain the following errors:
SecAdptLog API Trace 4 0 2007-07-25 15:24:47 Security DB user connect to DB C:\PROGRA~1\Siebel\7.7\WEBCLI~1\local\sse_data.dbf -q -m -x NONE -gp 4096 -c32m -ch64m with username=N5226908 returns err 22110 and connection 16472f0.
..
SecAdptLog API Trace 4 0 2007-07-25 15:24:47 DB SecurityLogin exits with err=17.
GenericLog GenericError 1 0 2007-07-25 15:24:47 (secmgr.cpp (2288) err=7010018 sys=1736) SBL-SEC-10018: You have entered an invalid set of logon parameters. Please type in your logon parameters again.(SBL-DAT-00446) Invalid user ID or password
Solution
As Tricklesync works with a browser cookie to collect the credentials information, the customer was advised to regenerate the cookie by going to User Preferences > DB Synchronization view and click the Save button.
Siebel Technical Support
No comments:
Post a Comment