Error when connecting to a repository using Rational ProjectConsole Maintenance Tool: Login failed for user

The full error message is as follows:

Connect to an existing warehouse
Initializing database access...
Loading database parameters...
Unlocking the schema repository ...
Unlocking the data warehouse ...
Connecting to the schema repository ...
Checking if the source database needs repair...
Exception caught: com.rational.dashboard.utilities.CoreException: Exception raised on login by user dashboardsystem for database TstD1: Caught a CQException at the JNI Boundary:
../cqsession.cpp: line 255-Unable to logon to the SQL_SERVER database "<Warehouse_Database>".
The vendor error message was:

SQLDriverConnect: RETCODE=-1, State=28000, Native Error=18456
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user '<Database_User>'.
Exception caught while updating time dimension tables: Exception raised on login by user dashboardsystem for database TstD1: Caught a CQException at the JNI Boundary:
../cqsession.cpp: line 255-Unable to logon to the SQL_SERVER database "<Warehouse_Database>".
The vendor error message was:

SQLDriverConnect: RETCODE=-1, State=28000, Native Error=18456
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user '<Database_User>'.
Applying all required schema upgrades...
Exception caught: Caught a CQException at the JNI Boundary:
../cqsession.cpp: line 255-Unable to logon to the SQL_SERVER database "<Warehouse_Database>".
The vendor error message was:

SQLDriverConnect: RETCODE=-1, State=28000, Native Error=18456
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user '<Database_User>'.
Exception caught in UpdateDataWarehouse::checkOutSchema(): com.rational.dashboard.utilities.CoreException: Exception raised on login by user dashboardsystem for database TstD1: Caught a CQException at the JNI Boundary:
../cqsession.cpp: line 255-Unable to logon to the SQL_SERVER database "<Warehouse_Database>".
The vendor error message was:

SQLDriverConnect: RETCODE=-1, State=28000, Native Error=18456
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user '<Database_User>'.
Stopping the DB Server...
Reconfiguring the Web server...
Starting the DB server...
Starting the DB Server, URL = http:/ /localhost:80/projectconsole/main?USE_CASE=restartdbserver&ACTION=start
writing to: C:\Program Files\Rational\ProjectConsole\DataRepository\<Data Repository>\properties.xml
Operation complete.


The logon used is incorrect.

Use the ClearQuest tools to verify the connection to the warehouse and schema databases. If the ClearQuest tools can connect, ProjectConsole will be able to as well. To verify that you can connect using the ClearQuest tools follow the steps below. Make sure these steps are performed on the ProjectConsole server.

Check the connection to the schema database:

1. Launch the ClearQuest Maintenance Tool
2. Select the Dashboard connection and go to Schema Repository > Update > Selected Connection.
3. Make sure the property values for the Dashboard connection are OK. Verify the database user and re-enter the password to make sure it is correct. And click Next.
4. Enter dashboardsystem/dashboardsystem for user/password when prompted for Super User privileges.
5. Click Next and make sure the connection is successfully updated.
   

Check the connection to the warehouse database:

1. Launch the ClearQuest Designer.
2. Select the Dashboard connection and click Next.
3. Enter dasboardsystem/dashboardsystem for user/password when prompted for a login.
4. Select the option to view the schema and then go to Database > Update User Database Properties.
5. Select the TstD1 Logical Database Name. Click on properties and verify the database user and re-enter the password to make sure it is correct. Select Update.

Verify

Verify that you now can successfully connect to the ProjectConsole repository.

1. Launch the ClearQuest client and connect to the Dashboard connection using dasboardsystem/dashboardsystem for user/password. If you can successfully connect, then the next step is to try the maintenance tool. If not, repeat the steps above making sure that you have a valid login for both the schema and warehouse databases.
2. Launch the ProjectConsole Maintenance tool and connect to the repository.