SBL-DAT-00569: The password you have entered is not correct. Please enter your password again.

Applies to:

Siebel Reports Server - Version: 8.0.0.6 SIA [20423] - Release: V8
Information in this document applies to any platform.
The password you have entered is not correct. Please enter your password again. (SBL-DAT-00569) (SSEP).

Goal

The following errors message is being reported in an environment where the Actuate Report generation is being performed through a Siebel Object Manager/Siebel Server which has Siebel Strong Encryption enabled :

Dispatched job to resource group : DefaultAsync...
Starting...
Generating rotp:/SADMIN/ACLIST_ENU_ENU.roi;1 ...
The password you have entered is not correct. Please enter your password again (SBL-DAT-00569)
User error.
Status No: 1 :
Basic Error: 1000
Module: ssReport%Start
Line: 96
User error.

The above error can be seen reported in the Status tab of the Job in the Actuate Management Console.

Solution

The behavior is caused because the Actuate Report Server is unable to encrypt/decrypt the password appropriately in order to provide it in the correct form to allow for a logon to the Siebel Object Manager.

In order to resolve this behavior it is necessary to copy across the encryption .dll from the Siebel Server to the Actuate Server so that the appropriate calls can be made for encryption/decryption as detailed below :

1. Shutdown the Actuate Services.
2. Copy the Siebel Strong Encryption Pack library from the Siebel Server in Windows (sslcrsa128.dll)
3. Place a copy of the .dll in the <%Actuate_Root%>\Actuate8\Server).
4. Restart all Actuate processes.
5. Resynchronize the users with the Actuate Server.
6. Retry the Report Generation.

Applies to:

Siebel Email Marketing, SPE - Version: 8.0.0.9 SIA[20433] and later   [Release: V8 and later ]
Information in this document applies to any platform.
Email Marketing Daemons were originally installed using the siebel.user.name parameter set to SMUSER. After changing this parameter to MKTUSER and restarting the daemons, started to receive the following errors in the logs:

ObjMgrSessionLog Error 1 000567e84c4e1738:0 2010-08-13 09:11:27 (physmod.cpp (9244)) SBL-DAT-00569: The password you have entered is not correct. Please enter your password again.

Symptoms

Email Marketing Daemons were originally installed using the siebel.user.name parameter set to SMUSER. After changing this parameter to MKTUSER and restarting the daemons, started to receive the following errors in the logs:

ObjMgrLicense    Load    5    000567e84c4e1738:0    2010-08-13 09:11:26    End: LoadLicenseManager
GenericLog    GenericError    1    000567e84c4e1738:0    2010-08-13 09:11:27    (secmgr.cpp (2542) err=4597527 sys=0) SBL-SEC-10007: The password you have entered is not correct. Please enter your password again.
ObjMgrSessionLog    Error    1    000567e84c4e1738:0    2010-08-13 09:11:27    (physmod.cpp (9244)) SBL-DAT-00569: The password you have entered is not correct. Please enter your password again.
ObjMgrSessionLog    Error    1    000567e84c4e1738:0    2010-08-13 09:11:27    (model.cpp (5974)) SBL-DAT-00569: The password you have entered is not correct. Please enter your password again.
ObjMgrSessionLog    ObjMgrLogin    3    000567e84c4e1738:0    2010-08-13 09:11:27    Login failed for Login name : MKTSEC

Changes

none

Cause

Email Marketing Server daemons use Siebel COM or Siebel Java Data Beans interface to connect to the SMObjMgr_enu. But your SMObjMgr_enu is configured to use SSO

Based on CR# 12-1HTEWCX and also "Getting error SBL-SEC-10007 (invalid password) when trying to use COM Data Control with SSO (Doc ID 558151.1)" on Support Web this type of interface does not support SSO.

Solution

Customer resolved this issue by changing the Security Adapter Mode on one OM server to 'dbsecadpt' to allow authentication to their MKTUSER user.

Additional information can be found in the Siebel Bookshelf > Security Guide for Siebel Business Applications > Security Adapter Authentication > Configuring Database Authentication.

References

BUG:12-1HTEWCX - ABILITY TO CONNTECT OM TO CTD, BHD AND ESD WHEN SSO IS ENABLED

Applies to:

Siebel CRM - Version: 8.1.1.1 SIA [21211] and later   [Release: V8 and later ]
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> reconfig compdef <compdef name>
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-10018: You have entered an invalid set of logon parameters. Please type in your logon parameters again (SBL-DAT-00446).
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 Email Marketing Server
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V8 (Professional)
Version: 8.0 [20405]
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-3418282265.

Symptoms

For the ESD, the service starts without any problem. However, in the log file I do not find that it connects successfully. The following error is found in the log file (which I will also attach to the SR):

<Exception>
<Major No.>256</Major No.><Minor No.>7668281</Minor No.><Message>The password you have entered is not correct. Please enter your password again.(SBL-DAT-00569)</Message><DetailedMessage>Unknown<DetailedMessage>
</Exception>

Cause

an extra space character appears to follow the username SADMIN.

Please edit the siebel.properties file again removing this extra space character.

Solution

Message 1

We have noticed that in your siebel.properties file for the ESD in the section

# ----------------------
# Siebel Connection info
# ----------------------
siebel.connection.string=siebel.TCPIP.None.None://akdev01:2321/DEV_ES/SMObjMgr_enu
siebel.user.name=SADMIN    
siebel.user.password=SADMIN33


That for the value

siebel.user.name

an extra space character appears to follow the username SADMIN.

Please edit the siebel.properties file again removing this extra space character.

and then Stop and Restart the ESD service again.


Jim Roberts
Oracle: Siebel Application Technical Support

Applies to:

Area(s):Security/Authentication
Release(s):V8 (Enterprise), V8 (Professional)
Database(s):All Supported Databases
App Server OS(s):All Supported Platforms
Latest release tested against:V8 (Enterprise)
Keywords:LDAP, ADSI, Custom, enterprise level, database authentication

This document was previously published as Siebel Alert 1313.

Description

After running the Siebel Enterprise Configuration Wizard (Enterprise Security Authentication Default option) to configure the security adapter, LDAP/ADSI/Custom adapter authentication is enabled at the Enterprise Level. This in turn means that many components will start to use security adapter authentication instead of database authentication. The likely impact of this is that all components will error out as described below under the Possible Symptoms section.

 

Bug 12-1IL24OE has been logged to address this product defect.

Likelihood of Occurrence

This behavior occurs when customers configure LDAP, ADSI or Custom security adapter authentication using the Siebel Enterprise Configuration wizard (Enterprise Security Authentication Default option).

Possible Symptoms

Below are different symptoms that may be reported if you are encountering this behavior:

 

• The browser displays the error message for new users trying to login:

 

SBL-SWP-00121: 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.

 

• When attempting to connect to a server using srvrmgr the following error is displayed:

 

Failed to connect server SRVR1: Handshake failed

 

• The following error appears when attempting to access the Server Administration views using a Dedicated Web Client:

 

SBL-ADM-02049: There is no connected server targeted for that command.

 

• If the SADMIN database password is different to the LDAP/Active Directory password or SADMIN does not exist in LDAP/Active Directory, then some Object Manager logs will show the following errors:

 

ObjMgrSessionLog     Error 1     00000004461b025c:0      2007-04-10 07:25:08   (physmod.cpp (9244)) SBL-DAT-00569: The password you have entered is not correct. Please enter your password again.

Workaround or Resolution

The workaround is to reset the enterprise level authentication to use database authentication using the steps below:

 

1. Log into srvrmgr as follows:

 

srvrmgr /g gateway_server_name /e enterprise_name /u sadmin /p <password>

 

2. Now run the following command to reset the enterprise parameters:

 

srvrmgr > change ent param SecAdptMode=DB

srvrmgr > change ent param SecAdptName=DBSecAdpt

 

3. Now restart the Siebel Server. Once the Siebel Server has started, connect to the relevant Siebel Server using srvrmgr:

 

srvrmgr /g gateway_server_name /e enterprise_name /s siebel_server /u sadmin /p <password>

 

4. At this point you can manually configure an individual object manager or component to use security adapter authentication. For example, for the Call Center authenticating against LDAP perform the following:

 

srvrmgr > change param SecAdptMode=LDAP for comp SCCObjMgr_enu

srvrmgr > change param SecAdptName=LDAPSecAdpt for comp SCCObjMgr_enu

 

5. Now restart the Siebel Server or individual component.

Maintenance Release Number

Please click on the link below to view the current status of the Change Request and associated Fix Requests:

 

Bug 12-1IL24OE