Applies to:
Siebel Anywhere - Version: 7.5.3.5 [16183] and later [Release: V7 and later ]
Siebel Remote - Version: 7.5.3.5 [16183] and later [Release: V7 and later]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.3.5 [16183] ESN
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: HP-UX 11i
This document was previously published as Siebel SR 38-2958199017.
Symptoms
SBL-GEN-04031, SBL-GEN-09103, SBL-ADM-02537Good morning,
A new Siebel developer has arrived to our project, he needs to use Siebel
Tools.
This morning we created a new mobile user for him and after install Siebel Tools in his
PC, we tried to launch task "Generate New Database" , in order to create a local database for
him.
When we run server task "Generate New database" with following parameters:
SQL
Anywhere Database = sse_utf8.dbf
we got the following error:
(gennewdb.cpp 27(462)
err=4031 sys=0) SBL-GEN-04031: Error durante descodificación Base64.
(smisched.cpp 17(821)
err=4031 sys=0) SBL-GEN-04031: Error durante descodificación Base64.
I searched on
supportweb this error, but unfortunately I don't find the cause of it.
I attached task log
file.
I have tried to connect with Tools application in my PC, with the new user, to
development Server database, and I connected succesfully.
Could you help us,
please?
Many thanks and Best regards.
Cause
Configuration/ Setup
Solution
Message 1
For the benefit of other users:
Customer experienced problems when attempting to perform a "Generate New
Database" task. We found following errors in Generate New Database log
(GenNewDb*.log).
SBL-GEN-09103: No se ha definido el valor del parámetro (es decir, es nulo)
SBL-GEN-04031: Error durante descodificación Base64.
[SBL-GEN-04031: Internal: Error occurred during base64 decoding]
During the research we found that above error could encounter as a
result of having an unencrypted Password in the siebns.dat file. As in
version 7 the passwords at Enterprise, Server or Component level are
stored in an encrypted format, having an unencrypted value in the
siebns.dat could corrupt siebns.dat file and cause this error.
We reviewed customer’s siebns.dat file and did find ‘DbaPwd’ parameter
for GenNewDb component is set to unencrypted value “SQL” as follows.
[/enterprises/Ent_CRM_DES/component groups/Remote/components/GenNewDb/parameters/DbaPwd]
Persistence=full
Type=string
Value="SQL"
Length=3
The encrypted value for “SQL” is “QqKg”. We made the changes to the
siebns.dat file by setting it to the correct value “QqKg” and returned
the file to customer with following instructions.
1. Please replace the current siebns.dat file with fixed siebns.dat file.
2. Stop Siebel servers, then stop Gateway server.
3. Restart Gateway server then start Siebel servers.
3. Now perform a new Generate New Database (GenNewDb) task.
The issue was ...<Ctd>..
Message 2
...<Ctd>
The issue was resolved with the fixed siebns.dat file.
Please note that customers modifying the siebns.dat files themselves is not supported, as it may corrupt the file.
Keywords: Generate New Database, SBL-GEN-04031, password, encrypted, unencrypted, siebns.dat, GenNewDb, DbaPwd, SQL, QqKg.
Thank you.
Applies to:
Siebel System Software - Version: 7.7.2.4 [18365] and later [Release: V7 and later ]
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Enterprise)
Version: 7.7.2.4 [18365]
Database: Oracle 9.2.0.6
Application Server OS: Sun Solaris 5.8
Database Server OS: Sun Solaris 5.8
This document was previously published as Siebel SR 38-2958059261.
Symptoms
SBL-GEN-04031Hi,
For security purpose, we plan to change the default value of Generate Trigger
component so that the technical team wouldn't need to provide the parameters while running this
task.
We were successful in updating all the parameters but when we run the task, it exits
with the following error:
"SBL-GEN-04031: Internal: Error occurred during base64
decoding."
We saw Service Request #: 38-1025380931 on the similar issue.
The steps
we performed were to update the default password in the server configuration - enterprise
component parameter as well as server component parameter (with start configuration & commit
configuration) and then syncronised the components and bounced ther server.
Did we miss
something?
Is it possible to change the default password from the GUI as we did?
Why
doesn't siebel store the default password we provide it in the encrpted form?
Thanks in
advance.
Regards
Cause
Change Request #12-1D2BMPK
Solution
Message 1
For the benefits of other users:
After performing the following password changes steps, error
"SBL-GEN-04031: Internal: Error occurred during base64 decoding."
reported where the password is not being encrypted accordingly in
Gateway Name Server (siebns.dat).
1) Navigate to "Site Map > Administration - Server Configuration >
Enterprise" and on Component Definitions view, select Menu, Start
Reconfiguration
2) Query for component Generate Trigger on Component Definition view
3) On Parameter view at lower panel, query for Privileged User Password and set the password and save it (step off the record)
4) On Component Definitions view, select Menu, Commit Reconfiguration
5) Restart Siebel Server
When checking siebns.dat file, the password set for Privileged User Password is on plain text.
Change Request #12-1D2BMPK (Password changes on enterprise component
definition through UI not being encrypted) being logged to address this
behavior.
Solution:
Change the password using server manager command when Siebel Gateway and Siebel Server are up and running.
srvrmgr /g gateway /e enterprise /u username /p password
srvrmgr> change param PrivUserPass=Siebel for compdef GenTrig
After the above restart Siebel Server and Gateway services and the password should be set in encrypted format accordingly
Applies to:
Siebel Remote - Version: 8.1.1.2 and later [Release: V8 and later ]
Information in this document applies to any platform.
Customer facing errors when trying to generate new database task from Siebel remote Server
Symptoms
Everytime that customer try to run gennewdb (generate new database task) he received error message bellow:
SBL-GEN-04031: Internal: Error occurred during base64
Changes
No visible changes
Cause
1. Missing DBAPWD parameter into gennewdb parameters screen
2. Customer changed some siebel server folders to a different structure
Solution
A. Add DBAPWD password into gennewdb parameter screen
B. Customer found that the enu*.dbf file which is in the parameters
of the Generate New Database server task, had been moved to different
location. When copied back to correct location the task ran correctly
We
found that the \dbtempl folder had been moved to the \bin subdirectory.
After moving this directory back to \%siebel_root%\srvr DbXtract worked
without problems
Applies to:
Siebel System Software - Version: 7.7.2 [18325] to 8.0.0.5 [20420] - Release: V7 to V8
All 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:
Siebel CRM - Version: 7.7.2.8 SIA [18379] and later [Release: V7 and later ]
Information in this document applies to any platform.
Symptoms
This occurred on a Siebel enterprise deployment version 7.7.2.8 on windows platform.
SCBroker and SRProc that do not start on 1 of 7 application server after
application server startup, instead the components are staying with the
status 'unavailable' .
Cause
The following errors are reported for the 2x components:
File: SRProc_10249.log
----------------
>>>
...
RPQueryLogEvt SRPQuerySubevt 3 0 2010-09-10 17:22:11 Task waiting is 60
GenericLog GenericError 1 0 2010-09-10 17:22:11 (srpdb.cpp (569)
err=4031 sys=0) SBL-GEN-04031: Internal: Error occurred during base64
decoding.
GenericLog GenericError 1 0 2010-09-10 17:22:11 (srpsmech.cpp (57)
err=4031 sys=0) SBL-GEN-04031: Internal: Error occurred during base64
decoding.
GenericLog GenericError 1 0 2010-09-10 17:22:11 (srpmtsrv.cpp (90)
err=4031 sys=0) SBL-GEN-04031: Internal: Error occurred during base64
decoding.
SRPQueryLogEvt SRPTaskInfo 3 0 2010-09-10 17:22:11 Main Init failed
GenericLog GenericError 1 0 2010-09-10 17:22:11 (smimtsrv.cpp (1063)
err=4031 sys=0) SBL-GEN-04031: Internal: Error occurred during base64
decoding.
SmiLayerLog Error 1 0 2010-09-10 17:22:11 Terminate process due to unrecoverable error: 4031. (Main Thread)
<<<
File: SRBroker_10250.log
-----------------
>>>
...
GenericLog GenericError 1 0 2010-09-10 17:22:12 (srbthrd.cpp (3869)
err=4031 sys=0) SBL-GEN-04031: Internal: Error occurred during base64
decoding.
GenericLog GenericError 1 0 2010-09-10 17:22:12 (srbmtsrv.cpp (71)
err=4031 sys=0) SBL-GEN-04031: Internal: Error occurred during base64
decoding.
SrbLayerLog Error 1 0 2010-09-10 17:22:12 Main Init fails
GenericLog GenericError 1 0 2010-09-10 17:22:12 (smimtsrv.cpp (1063)
err=4031 sys=0) SBL-GEN-04031: Internal: Error occurred during base64
decoding.
SmiLayerLog Error 1 0 2010-09-10 17:22:12 Terminate process due to unrecoverable error: 4031. (Main Thread)
<<<
The above errors indicate the following:
1. A high number of
components being raised while your Siebel server is coming up. This can
lead to a high memory consumption and make the SrBroker and SrProc to go
down. Please review the number of components being used and make
offline the ones that are not being used.
2. A discrepancy on the password parameter for the components SRbroker and SRproc.
I can see that a Parameter Password has been set for SRBroker and SRProc cmponents at compnent definition level.
The password value I can see there is different to the one used for the
password parameter at enterprise level which is equally used for some
components at server level.
This could be confirmed by reviewing the password parameters at different levels.
File: siebns.dat
------------------
Password value at enterprise level: "xxxxxxxxxxxxxxx". The same password is set for some components at server level.
Password value at component definition level for SRBroker and SRProc: "yyyyyyyyyyyyyy"
Solution
Please try resetting the password a the highest level component
definition or reset the password for server "SVWSIEBP04" only by going
into Server Manager command line, set server SVWSIEBP04 and type:
srvrmgr> change param password=new_password for comp srproc
srvrmgr> change param password=new_password for comp srbroker
After doing the above and restarting the application server, the issue was resolved.
אין תגובות:
הוסף רשומת תגובה