QE-DEF-0285 The logon failed.

by ·0 Comments

Product:
Cognos TM1 10.2 64 bit
Cognos TM1 Architect 10.2 32 bit
Cognos TM1 package connector 10.1.1 32 bit
Microsoft Windows 2008 R2 server 64 bit
Oracle database server

Symptom:
Error when connecting from TM1 Architect to Oracle source through Cognos BI via TM1 Package Connector.
You have installed TM1 Package Connector on your TM1 server, and on your Terminal Server where you have installed TM1 Architect and Cognos Framework Manager.

You get a Data Source Sign on when you inside TM1 Architect are trying to Query the data with the IBM Cognos Package. This is because the client computer where TM1 Architect are trying to connect direct to the Oracle data source. You need to install Oracle 32 bit Drivers on the computer where TM1 Architect are installed. Also you need to update the tnsnames.ora file with the values needed for the database you try to connect to.

Error Message:
Error: MetaData procedure line (0): CCognosPackage::BuildDataSource Exception: (TR0324) Invalid logon.
– QE-DEF-0285 The logon failed.
– QE-DEF-0325 The logon failed for the following reason:
– RQP-DEF-0068 Unable to connect to at least one database during a multi-database attach to 1 database(s) in:
– CNSDW
–
– UDA-SQL-0432 Unable to locate the gateway “cogudaor”.
or
Error: MetaData procedure line (0): CCognosPackage::BuildDataSource Exception: (TR0324) Invalid logon.
– QE-DEF-0285 The logon failed.
– QE-DEF-0323 The DSN(ODBC)/ServiceName is invalid. Either the DSN is missing or the host is inaccessible.
– RQP-DEF-0068 Unable to connect to at least one database during a multi-database attach to 1 database(s) in:
– CNSDW
–
– UDA-SQL-0031 Unable to access the “CNSDW” database. Check that the connection parameters to the database are configured correctly. For example, ensure that the data source connection contains the signon information, such as a password, to connect to the database.
– UDA-SQL-0532 Data Source is not accessible: “data.test.domain.com”.
– ORA-12154: TNS:could not resolve the connect identifier specified

Solution:
Install the Oracle 32 bit drivers on the terminal server where TM1 architect and TM1 Package Connector are installed.
Update the tnsnames.ora file in folder \network\admin to include your data source.

Install the Oracle 32 bit drivers on the Windows server where TM1 Application and TM1 Package Connector are installed. This is the TM1 server where you have your TM1 data folder and you TM1 application.
Update the tnsnames.ora file in folder \network\admin to include your data source.

To get ODBC connections to work in TM1 Architect you need to also install the Oracle 64 bit drivers (in its own directory) on the Windows server where TM1 Application or TM1 Architect are installed. The ODBC connection is using the 64 bit parts of TM1 applications.
You need to start the ODBC Admin (odbcad32) and configure your odbc connection before start of TM1 Architect.

You must restart the TM1 application server, to make it be aware of your new installation of Oracle Drivers.

The Windows Path variable must include the path to the BIN folder of both the Oracle drivers installed.

More information:
Error:UDA-SQL-0432 Unable to locate the gateway “cogudaor”.
= missing 32 bit driver on TM1 server

Error: ORA-12154: TNS:could not resolve the connect identifier specified
= missing TNSNAMES.ORA file on the TM1 server

The TM1 server 64 bit version is using 32 bit drivers when access to data is made though the TM1 Package Connector (who is a 32 bit application). The TM1 architect also need direct connection to the Oracle datasource when developing, so you need 32 bit drivers on the TM1 Architect computer when using the TM1 package connector software.

The TM1 server 64 bit version is using 64 bit drivers when access to data is made through the ODBC connection on the server, here is the same on the terminal server where you have installed TM1 Architect. You must install the 64 bit database drivers on the TM1 servers and TM1 Architect clients.