Error: A connection to the database could not be established. Contact your system administrator to rectify the problem.

Document ID : KB000025828
Last Modified Date : 14/02/2018
Show Technical Document Details

Issue:

Error: A connection to the database could not be established. Contact your system administrator to rectify the problem. Unable to start UAPM.

Resolution:

Try the following steps; testing to see if you are able to connect after each one.

  1. Clear the IE browser cache.
    Close all open browser windows and open a new one, then try connecting to UAPM again.

  2. Use the ConnectTest.exe utility provided with UAPM to verify that the account specified in the Configurator is able to successfully connect to UAPM.

    Open Configurator from Start Menu, All Programs, CA, Unicenter Asset Portfolio Management, Configurator.
    Select Asset Portfolio Management from the Configurator home page.
    Check that the items circled in the picture below are correct.

    Server Name: this must point to your MDB server name
    APM DB Login ID: should be "uapmadmin"
    APM DB Password: should contain the password you assigned to the uapmadmin account during installation.
    Confirm APM Password: should contain the password you assigned to the uapmadmin account during installation.

    If you make any changes, click "Update" at the bottom of the Configurator page, then OK in the confirmation dialog box you will receive. Select "Cancel" to return to the Configurator home page.

    Figure 1

    Repeat these steps for the Asset Portfolio Management Web Services tab from the Configurator home page.

    Figure 2

    Exit the Configurator.

    Use Windows Explorer to navigate to:

    C:\Program Files\CA\SharedComponents\APM Common Services

    Double-click ConnectTest.exe to start the ConnectTest program.

    Select your MDB database type (SQL Server or Oracle) and supply the connection information obtained from the Configurator.

    Figure 3

    Click Test.
    When ConnectTest has completed, scroll to the bottom of the output window and be sure the final connection test was successful. If this test fails, UAPM will not be able to connect to the MDB database, and will not be able to start even if all the other tests were successful.

    If you have verified that your connection parameters are correct, but ConnectTest still fails, then If the MDB is located on a remote server from the UAPM application, be sure you have installed the SQL Server or Oracle client tools. For SQL Server 2005, this means you must have SQL Server Management Studio installed on the UAPM application server. For SQL Server 2000, you must have Query Analyzer installed. For Oracle, you must have Oracle Management Tools installed locally.

    Test your connection to the MDB by attempting to login to SQL Server or Oracle from the UAPM application server using the local copy of the corresponding client tools. If you are unable to connect using the client tool corresponding to your database application, please consult your database administrator.

    Note that for SQL Server, you must have the set of client tools installed which corresponds with the version of SQL Server which is hosting the MDB database. For example, if your MDB is located on a SQL Server 2005 instance, you must have the SQL Server 2005 client tools installed on the UAPM application server. Do not install both versions (2000 and 2005) of the client tools on the UAPM application server. You may have one version of SQL Server client tools plus the Oracle client tools installed on the UAPM application server as the Oracle tools and the SQL Server tools do not conflict.

  3. If you are still receiving the error "UAPM is unable to connect to the database", then ask the UAPM administrator to confirm that the account you are using is assigned to a Role in UAPM. You will not be able to open UAPM if the account you use is not assigned to a UAPM Role.

    If you do not receive a login prompt when attempting to start UAPM, this indicates that UAPM is using Windows Integrated Security. With Windows Integrated Security, UAPM verifies that the userid you are logged in to Windows with is assigned to a Role in the MDB database. If your Windows login account is not assigned to a Role, you will not be allowed to start UAPM. In this situation, please ask your UAPM administrator to add a contact record for you in UAPM and assign it to a UAPM Role.

    During a new installation of UAPM where no data exists in the MDB database, or only sample data is loaded into the MDB database, a contact record is created for the account you were logged into Windows with to perform the installation. This user account will be the only one you can use for starting UAPM until you have added Contact records for additional users, and then added those Contacts to a UAPM Role. The installer's userid will automatically be assigned to the Administrator Role in UAPM, and will have administrative access to all functionality of UAPM.