Installation error remote DSM connecting to MDB that runs on a separate server. Error: (WorldView Repository) The selected Database instance has not been configured for use by Unicenter.

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

Description

This issue happens when you install NSM 11.1 from a Patched Master Image while the MDB was installed without any patches, such as the GA version. You may see an error message during the installation process at the "Database Selection and Configuration" screen. If you try to connect to an MDB that was created by a NSM 11.1 unpatched image on SQL 2005, you may see the error message at the "Validate Logon" page.

Error: (Worldview Repository) The selected Database instance has not been configured for use by Unicenter.

Error: (Enterprise Management Database) User "nsmadmin" does not have sufficient Management Database (MDB) administrator privileges. Please choose the user created by the product, consult documentation on requirements.

Solution

  1. If SQL 2005 server with NSM 11.1 unpatched version is installed, be sure to grant "VIEW SERVER STATE" permission to the user nsmadmin (the CA NSM Admin SQL user).

    You must run the following SQL Query to grant this permission:

    GRANT VIEW SERVER STATE to nsmadmin

    Note: For more information, refer to PIB QI84086 on support.ca.com.
  2. Verify that the user nsmadmin has permit access to the master database and mdb database:

    1. Go to Start -> Programs -> Microsoft SQL Server 2005 -> SQL Server Management Studio.

    2. Right-click master and mdb database, select Properties -> Permissions, and ensure that user nsmadmin has access to these databases.

      Figure 1

  3. Verify that the user nsmadmin has the following roles on the MDB database:


    db_owner, uniadmin, and regadmin:

    1. In the SQL Server Management Studio, expand Security -> Logins.

    2. Right-click on user nsmadmin, select Properties -> User Mapping.

    3. Select mdb in 'Users mapped to this login' screen, and ensure that the database role options db_owner, uniadmin, and regadmin have been selected.

  4. Make sure the user nsmadmin has the "sysadmin" server role:

    1. In the SQL Server Management Studio, expand Security -> Logins.

    2. Right-click nsmadmin, select Properties -> Server Roles, and ensure that 'sysadmin' server role option has been selected.

  5. Rerun the setup; and verify that the error does not appear.

Note: This solution applies to CA NSM 11.2 Version also.