Symptom:
All iConsole reviewers see an error message similar to the examples below when they try to run a BusinessObjects report for CA Data Protection.
If you see this message, go to Solution 1:
CS:COM Provider CLSID not specified or erroneous
Note: You may also see this message in BOXI Designer when using a Universe connection.
If see messages such as these, go to Solution 2:
Login failed for user 'WGNREPORTING'. Database username or password is incorrect.
SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. Server name may be incorrect
Database 'wgn' does not exist. Make sure that the name is entered correctly. Database name may be incorrect
TCP Provider: No connection could be made because the target machine actively refused it. Database may be down
If you see this message and a WIS 10901 error number, go to Solution 1:
DBDriver failed to load: <BusinessObjectsInstallationFolder>\win32_x86\dataAccess\connectionServer \dbd_oci.dl (%1 is not a valid Win32 application.)
Note: You may also see this message in BOXI Designer when using a Universe connection.
If see messages such as these, go to Solution 2:
ORA-01017: invalid username/password; logon denied. Database username or password is incorrect.
ORA-12154: TNS:could not resolve the connect identifier specified. DB Service name may be incorrect
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor. Database may be down
Solution 1
Users cannot connect to a reporting database because the necessary database native client software to connect to that database type has not been installed on the BusinessObjects server.
Verify that the correct native client software (such as Oracle Net Client) is installed. The native client software enables the BusinessObjects CMS server (or any BOXI node servers) can communicate with the CA Data Protection database where the data warehouse is located.
If a user sees these messages while using BOXI Designer, verify that the native client software is installed on the BOXI Designer host computer.
We recommend that you use the latest stable service pack version for both your database and your native client software.
When you install the latest native client software, choose the x86 (32-bit) or x64 (64-bit) native client version as appropriate, depending on the hardware of the host computer.
Install the native client software as part of Management Studio or as part of the Microsoft 'Feature Pack’ download.
Note: The SQL Server 2008 R2 native client does support SQL Server 2008. But the SQL Server 2008 native client does not support SQL Server 2008 R2.
Solution 2
These error messages indicate a failure to connect to the database or a failure to authenticate.
The BusinessObjects Universe connection that defines how to connect to the reporting database may be configured incorrectly. This happens if there a data entry error occurred when running InstallUniverse.bat.
Verify the Universe connection configuration details:
If you cannot connect to the Universe successfully, use a database native client to verify independently that you can access the database using the correct address and login credentials of a BusinessObjects user account.
Note: If your BusinessObjects deployment uses an Oracle databases, verify that tnsnames.ora includes an entry for the CA Data Protection CMS database. For details, see Add the CA Data Protection CMS to Tnsnames.ora.
Copyright © 2015 CA Technologies.
All rights reserved.
|
|