SAP Knowledge Base Article

Symptom

l From LifeCycle Manager, logging into the destination CMS when creating a job is successful. When attempting to promote a job using Windows Active directory authentication, an error is thrown.

l Commit Status=Commit attempted and failed, Promotion Status=Failure: Logon failure to Destination CMS:..<system>:6400

Environment

SAP Business Objects Enterprise (BOE) XI3.1 All Patch Levels SAP Business Objects Business Intelligence Platform (BI) 4.0 All Patch Levels Life Cycle Management (LCM)

Reproducing the Issue

1. Install and configure SAP Business Objects server products with an Active Directory domain on 2 servers 2. For BOE 3.1, you may have to additionally Install LCM on one of the servers (For BI4.0 and above, LCM is deployed with BOE webapp) 3. Create a user on AD that has local Administrative privileges on both servers 4. Map the AD usergroup and user over to both servers 5. Add this AD user to the Administrators group in each of the BusinessObjects Servers installed. 6. Explicitly grant Full Control rights to this user on the Root Folder of Enterprise. 7. Explicitly grant Full Control to LCM from with in CMC > Applications to user from above steps. 8. to Test: Create an .lcmbiar file using LCM on one of the Servers and try importing it on the other server while logging in to Destination as the AD user and using

Active Directory Authentication as the authentication method.

Resolution

To resolve the issue

1. For Windows AD Authentication: the Job server responsible for LCM job processing must be started with an additional argument in the server command line.The Job server responsible for LCM job processing is: for BOE XI3.1: LCM Job Server for BI 4.0 and above: Adaptive Job Server    

2. Go to Central Management Console (CMC)> Servers> LCM Job Server > Properties> Command Line Parameters and add the following -javaArgs "Djava.security.auth.login.config=C:/WinAD/bscLogin.conf,Djava.security.krb5.conf=C:/WinAD/krb5.ini" NOTE:  If the server command-line already contains -javaArgs argument, then append to its existing value as shown in bold below: -javaargs "Djava.awt.headless=true,Dcom.businessobjects.mds.cs.ImplementationID=csEX,XX:MaxPermSize=192m,Dbusinessobjects.connectivity.directory=C:/Program Files (x86)/SAP BusinessObjects/SAP BusinessObjects Enterprise XI 4.0//dataAccess/connectionServer,Djava.security.auth.login.config=C:/WinAD/bscLogin.conf,Djava.security.krb5.conf=C:/WinAD/krb5.ini where C:\WinAD is the location of these files. This location needs to be modified to suite your server location   

3. Restart the Job Server

 

Keywords

LCM winAD AD Authentication failure lcmbiar cannot import

Header Data

Product

    1385980 - Logging into LCM using Windows AD authentication throws an error: Commit Status=Commit attempted and failed, Promotion Status=Failure: Logon failure to Destination CMS:

Version   4     Validity: 10.07.2012 - active   Language   English

Released On 10.07.2012 21:38:03

Release Status Released to Customer

Component BI-BIP-LCM Lifecycle Management Console - Promotion mgmt, Version mgmt

BI-BIP-DEP SBOP Web Application Deployment, Wdeploy

Priority Normal

Category How To

Other Components

Product Product Version

SAP BusinessObjects Business Intelligence platform SAP BusinessObjects Business Intelligence platform 4.0

SAP BusinessObjects Enterprise XI 3.1