Chat now with support
Chat with Support

Identity Manager 8.0 - Installation Guide

About this Guide One Identity Manager Overview Installation Prerequisites Installing the One Identity Manager Installing and Configuring the One Identity Manager Service Updating the One Identity Manager Installing and Updating a One Identity Manager Application Server Installing, Configuring and Maintaining the Web Portal Installing the Operations Support Web Portal Installing and Updating the Manager Web Application Logging into One Identity Manager Tools Troubleshooting Appendix: One Identity Manager Authentication Modules Appendix: Creating a One Identity Manager Database for a Test or Development Environment from a Database Backup Appendix: Manager Web Application Extended Configuration Appendix: Machine Roles and Installation Packages Appendix: Settings for a New SQL Server Database

Displaying the Transport History and Testing the One Identity Manager Version

Displaying the Transport History and Testing the One Identity Manager Version

When a schema is installed with the Configuration Wizard, migration date and migration revision are recorded in the database's transport history.

When you import a transport package with the Database Transporter, the import date and description, the database version and the transport package name are recorded in the transport history of the target database.

To display transport history

  • Start the Designer and select the menu item Help | Transport history.

To obtain an overview of the system configuration

  • Start the Designer or the Manager and select the menu item Help | Info.

    The System information tab gives you an overview of your system configuration. Have this information available when you contact support.

    NOTE: This report is sent once a month to One Identity after you have enabled vendor notification.
Related Topics

Handling Errors and Warnings during System Compilation

Handling Errors and Warnings during System Compilation

NOTE: Any compiler errors and warnings are recorded during compilation. You can view compiler errors and warnings after compilation is complete.

  • Use Save log to file... in the context menu to save the compilation log.
  • Correct the error after compilation is finished.

  • Compile the database again after correcting the errors. To do this, start compilation in Designer using Database | Compile database....

To display messaging during compilation and saving

  • Select Display to display a message. This opens an error message window.

    In addition, a more detailed description of the error is displayed. Configure the amount of information to be displayed using the options in the error message window. Open the configuration with the button and enable or disable the options you want.

    Table 52: Options for Displaying Error Messages
    Option Meaning

    Show previous errors

    Specifies whether all previous errors that lead to the current error, should also be shown.

    Show One Identity error numbers

    Specifies whether internal error numbers are shown.

    Show error positions

    Specifies whether error position are also shown in the program code.

    Wrap long lines

    Specifies whether long error messages are wrapped.

    Show only user relevant

    Specifies whether all error messages or only message classified as "user relevant" are shown.

    Show asynchronous calls Specifies whether error messages in asynchronous method calls are shown.
    Show crash report Specifies whether error messages from the crash recorder are shown.

    NOTE: The button Send as mail creates a new email message in the default mail program and copies over the error text.

  • To save all the messages in a file, select the entry and select Save log to file... from the context menu.
  • To add a message to the clipboard, select the entry and user CTRL + C.

If errors occur, these are shown immediately in a separate log window during compilation.

  • If you double click on the error message with the mouse you jump to the corresponding line in the source code view (upper part of the window). You can only view the source code you cannot edit it.
  • Use the Save button to save the error messages to file.
  • Use the Close button to close the error log. Then the compilation continues.

Figure 10: Error Message Log

Checking data consistency

Checking Data Consistency

The consistency check provides different tests for analyzing data objects and to ascertain the current state of their data. You can use your own tests as well as the predefined one and repair the data if necessary.

NOTE: You should run a consistency check at regular intervals or after major changes to the system configuration.

You can run consistency checks in the Manager and in the Designer. Database tests are run in their entirety in the Manager and the Designer. In the case of table tests and object tests in the Manager, the application model is tested and in the Designer, the system model is tested.

NOTE: It is recommended to run consistency checks with an administrative system user.

Consistency checks of type "Object test" are always run in user context. If the user does not have any permissions for a certain object, errors may not be identified or repairing errors may fail.

To run a consistency check

  1. Start the Consistency Editor in the Designer or Manager using the menu item Database | Check data consistency.....

    During start up, One Identity Manager schema table definitions are loaded and database objects are made available for testing.

  2. Specify the test options.
  3. Start the consistency check. The following test procedures are available in the Consistency Editor for this:
    • Check all test objects

      NOTE: To exclude individual test objects from the test, select them in the Consistency Editor list view and label them using Disable in the context menu before starting the test.

    • Test single objects

      Select the test object you want to test in the list view and start the test from the context menu item Verify.

      TIP: Use SHIFT + SELECT or CTRL + SELECT to multi-select test objects for testing.

  4. Verify error output.
  5. Repair errors if necessary.

DBQueue Processor does not Process Tasks

DBQueue Processor does not process tasks

After restoring a One Identity Manager database from a database backup, no more DBQueue Processor tasks are handled.

If the SQL Server in running on a virtual machine and the virtual machine is suspended, it is possible that no more DBQueue Processor tasks are handled after restarting the virtual machine.

You will get the following message in the Configuration Wizard when updating One Identity Manager:

Cannot enable broker because of other users are active.

Probable reason

The SQL Server Service Broker may not be reacting because of initializing the DBQueue Processor. The Service Broker is implemented for DBQueue Processor communications.

Solution

Execute the following steps in the database using a suitable query tool.

  1. Stop all DBQueue Processor components.

    exec QBM_PWatchDogPrepare 1

    go

    exec QBM_PDBQueuePrepare 1

    go

  2. Check whether other database sessions are active.

    select *

    from sys.sysprocesses p

    where dbid = DB_ID()

    and spid <> @@SPID

    If there are still sessions active, they must be closed first.

  3. Create a new ServiceBroker ID and enable message delivery.

    alter database <database name> set NEW_BROKER

    go

    alter database <database name> set enable_broker

    go

  4. Initializing the DBQueue Processor.

    exec QBM_PDBQueuePrepare 0,1

    go

    exec QBM_PWatchDogPrepare

    go

NOTE: If you restore a test or development database from a backup of another One Identity Manager database, these steps are executed by the Database Compiler. Manual execution of the steps is not necessary in this case. For more information, see Appendix: Creating a One Identity Manager Database for a Test or Development Environment from a Database Backup.

Related Documents