What are the possible causes for the authentication failure in CA Business Intelligence when using Enterprise as authentication method?

Products

• CA IT Asset Manager
• CA Software Asset Manager (CA SAM)
• ASSET PORTFOLIO MGMT- SERVER
• SUPPORT AUTOMATION- SERVER
• CA Service Desk Manager - Unified Self Service
• CA Service Desk Manager
• CA Service Management - Asset Portfolio Management
• CA Service Management - Service Desk Manager

Issue/Introduction

Description:

This document provides a list of possible causes for authentication problems in CA Business Intelligence.

Solution:

The following are common causes for authentication problems in CA Business Intelligence.

1. The Central Management Server Service is not started: The CMS is responsible for authenticating users and groups, and keeping track of the availability of the other BusinessObjects Enterprise services. It also maintains the BusinessObjects Enterprise system database, which includes information about users, groups, security levels,
   
   Note: All servers communicate with the CMS when they start up
   
   
2. Database Unavailable: The users will not be able to authenticate if the BOXI database (CMS database) is either unavailable or not present. This will write the following error in the ca-install.log
   
   "Authenticating user [ Administrator ] on XXXXXXX:6400 using authType [secEnterprise] Exception caught: Unable to initialize session: Server XXXXXX not found or server may be down Tuesday 0X/XX/09 15:27:43 DBG -- Leave BIEK_ChangeBoAdminPassword. Return value = 16027
   
   Please make sure the database for BOXI is created and the database services are started.
   
   
3. BOXI user not created: Installation of CA Business Intelligence requires a user to be created on the database server. Refer "Custom Install of CA Business Intelligence (Windows) in Implementation guide of ServiceDesk R12 for steps"
   
   
4. Default database not set for the CMS user: The BOXI user created on the database server should have CMS as the default database and have db_accessadmin, db_owner, and db_securityadmin as owned schemas and role members.
   
   
5. System DSN not present: A system DSN should be created for the CMS database using the credentials of the BO User. The Enterprise authentication uses the System DSN.
   
   
6. Invalid Username/Password combination: Make sure the username and password combination is correct. Make a note of the Administrator's Username and Password at the time of installation which will help to reset the other user's passwords if forgotten.

Environment

Release:
Component: ARGIS