Console Setup Validation Rules

When installing Identity Finder Console, validation rules are executed to ensure the installation will succeed.  If the test for a rule fails, use the information below to change the affected server or application configuration.

The text of the Error Message(s) as display below is shown when clicking on the word Failed to the right of the failed validation rule.

Validation Rules

• Validate database authentication method

  Purpose: To identify the use of Windows Authentication and ensure that Windows Authentication is only used for remote SQL servers when both systems are joined to a domain.
  Error Message(s):
  You cannot use Windows Authentication for the application database connection because the SQL server is on a separate machine and this machine is not joined to a domain.
  You are using Windows Authentication for the application database, but this SQL Server is on a separate machine and this machine is not joined to a domain. It requires additional configuration to work.
  Possible Resolution: In order to use Windows Authentication with a remote SQL server, both servers must be joined to the same domain.  If using a domain is not possible, additional configuration steps are required to use Windows Authentication.  Specifically, both the application server and remote SQL server must be using the same username and password for access (e.g., the user account running the installer on the application server must be identical and have an identical password to a user with appropriate permissions on the remote SQL server).  In some cases an explicit trusted connection must exist before the installation can continue.  This can be done by issuing a "net use" command.  The following is an example of the format of the "net use" command and should be run from an administrative command prompt prior to installation:
  net use \\REMOTE-SQLSERVER-COMPUTERNAME /u:"USERNAME" PASSWORD
  If the above "net use" command works, it will print out "The command completed successfully."  If Windows Authentication is not working on two machines not joined to a domain, SQL Authentication can be configured for the SQL server and used accordingly.  Use the back button to return to the Database Connection page of the installer and choose the appropriate authentication method.  For advanced database configurations, it may be necessary to consult a qualified database administrator (DBA).

• Validate database connection

  Purpose: To test the connection to an existing database.
  Error Message(s):
  Failed to connect to the database. [SQL SERVER DB ERROR]
  Unable to verify connection to the database.
  Possible Resolution: Ensure that the database connection string is appropriate, that network connectivity is available, that passwords are correct, and that database user has appropriate permissions.  In most cases this error indicates an invalid or improperly formatted server name in the server name field. For further information on the database connection information, please review the Database Connection step in the Deployment Guide or consult an experienced database administrator (DBA) tasked with managing the database server.  Once the specific connection details are obtained, use the back button to return to the Database Connection page of the installer and enter the appropriate database connection information.

• Validate database schema

  Purpose: To review the database schema to ensure that the database creation or update routines were properly applied by the SQL server.
  Error Message(s):
  [SQL SERVER DB ERRORS]
  Possible Resolution: Review the error messages and contact support by opening a new ticket.  In the ticket, please include the exact text of the error message(s), the version of console being installed, and identify the issue as a failed console installation or upgrade, as appropriate.

• Validate Database Exists

  Purpose: To ensure that the database exists when attempting to access an existing database or ensure that the selected database name can be used to create a new database.
  Error Message(s):
  Unable to obtain a list of existing databases: [SQL SERVER DB ERRORS]
  Database does not exist.
  You have chosen to use an existing database, but the database does not exist.
  You have chosen to create a new database, but the database already exists.
  You have chosen to use an existing database, but the database has not been initialized.
  Possible Resolution: When performing an upgrade, if the database does not exist, use the back button to return to the Database Connection page of the installer and input the correct name of the database.  Additionally when upgrading the database being upgraded must first be initialized.  The initialization process occurs when you first log in to the console web application after an installation occurs.  If a database is not initialized simply log in to the console web application and then attempt the upgrade again.  If the database does exist and cannot be accessed, database errors will be reported.  When performing a new installation, if the a database with the specified name already exists, use the back button to return to the Database Connection page of the installer and input a new database name or click back again to perform an upgrade rather than a new installation.  If there are database errors, contact support by opening a new ticket.  In the ticket, please include the exact text of the error message(s), the version of console being installed, and identify the issue as a failed console installation or upgrade, as appropriate.

• Validate database exists after deployment

  Same as Validate Database Exists above.

• Validate existing database version

  Purpose: To ensure that the installer is not older than the currently installed version.
  Error Message(s):
  Unable to determine the current database version. The query returned a null or empty value for the current version, which indicates that you should create a new database instead of using an existing database.
  You have chosen to use an existing database, but the database does not meet the minimum requirements.  The database must be at least version 4.1.2 and the selected database is at version [Your db VERSION].
  You have chosen to use an existing database, but the database does not meet the minimum requirements. The database must be at most version [Your INSTALLERVERSION] and the selected database is at version [Your db VERSION].
  Possible Resolution: Determine the necessary upgrade path and execute the required steps. If the currently installed version is newer than the installer, the installer will not run since a downgrade is not possible.  In this case close the installer and download the newest installer from the product updates page.

• Validate database encryption passphrase

  Purpose: To ensure that when doing a re-install or server move, the database encryption passphrase is the same one used when the original installation occurred.  Without the same passphrase it would not be possible to view match data in the database after installation.
  Error Message(s):
  Failed to validate database encryption passphrase. [SQL SERVER DB ERROR]
  The database encryption passphrase is incorrect. Please use the passphrase from the initial installation.
  Possible Resolution: Use the same passphrase that was used when the original installation occurred and the database encryption was first configured.  Once the original passphrase is obtained, use the back button to return to the Application Passwords page of the installer and enter the appropriate passphrase.

• Validate database multiple user mode

  Purpose: To ensure that a database being upgraded is in MULTI_USER mode.  If the database is not in the correct mode, the installation will fail.
  Error Message(s):
  Unable to determine the current database user mode. The query returned a null or empty value for the current database, which indicates that the database server was unable to determine the mode of the database.
  The currently selected database is not in Multi-User mode.  The current mode is [CURRENT_MODE].  Please configure the database for Multi-User mode or select a new database.
  Possible Resolution: Consult a qualified database administrator (DBA) to change the selected database to MULTI_USER mode.

• Validate database permissions

  Purpose: To ensure that the permissions on the database during an upgrade are sufficient for the installer to complete the upgrade process.
  Error Message(s):
  Unable to obtain user permissions information.
  Unable to determine the user database permissions.
  The current user does not have adequate database permissions.  The specific permissions error is: CREATE DATABASE permission required in 'master' database to create a new database (required for new installations only)
  The current user does not have adequate database permissions.  The specific permissions error is: CREATE ANY DATABASE permission required to create a new database (required for new installations only)
  The current user does not have adequate database permissions.  The specific permissions error is: ALTER ANY CONNECTION permission required to use the KILL command when upgrading the database (optional for upgrades only - when missing, the installer will not try to kill existing connections.  In most cases the database upgrade will succeed, as the current version of Microsoft Tools used to perform database changes should be able to work around requiring this permission.)
  The current user does not have adequate database permissions.  The specific permissions error is: ALTER DATABASE permission required to configure the database when upgrading (required for upgrades only)
  The current user does not have adequate database permissions.  The specific permissions error is: ALTER ANY LOGIN privileges are required to install or upgrade the database
  (optional for upgrades only - when missing, the installer will not try to create a db user if one is missing.  This can cause failure if the NT AUTHORITY\NETWORK SERVICE account requires permissions and is not properly granted access to the database.)
  The current user does not have adequate database permissions.  The specific permissions error is: EXECUTE sp_fulltext_database stored procedure permission is required to install or upgrade the database (optional for new installations or upgrade and only required when the Full-Text Search service is installed.)
  The current user does not have adequate database permissions.  The specific permissions error is: ALTER permissions on the upgrade database are required
  The current user does not have adequate database permissions.  The specific permissions error is: ALTER ANY USER privileges are required to upgrade the database
  (optional for upgrades only - when missing, the installer will not try to create a db user if one is missing.  This can cause failure if the NT AUTHORITY\NETWORK SERVICE account requires permissions and is not properly granted access to the database.)
  The current user does not have adequate database permissions.  The specific permissions error is: User must be able to create tables in the tempdb databases
  The current user does not have adequate database permissions.  The specific permissions error is: User must be able to select data from tables in tempdb database
  Possible Resolution: Review the specific error message and consult a Database Administrator (DBA) to ensure that the user account connecting to the database has the necessary permissions.  If the installer is unable to determine the current user or database permissions, ensure that the database connection is working and the user account has access to the database.
  
  

• Validate database recovery model

  Purpose: To warn about possible performance degradation during an upgrade.
  Error Message(s):
  The database recovery model is not set to Simple, that may affect the performance of the upgrade. (Warning)
  Unable to obtain the current database recovery model. Exception: [EXCEPTION TEXT]
  Possible Resolution: Review the specific error message and consult a Database Administrator (DBA) to ensure that the user account connecting to the database has the necessary permissions.  If the installer is unable to determine the current user or database permissions, ensure that the database connection is working and the user account has access to the database.
  
  

• Validate FILESTREAM Setting

  Purpose: To validate that the FILESTREAM setting for the database is configured for file I/O access when the "Store uploads in the database" option is selected in the installer.
  Error Message(s):
  The FILESTREAM feature of SQL Server needs to be configured for file I/O access.
  Unable to obtain the FILESTREAM access level of the database.
  Possible Resolution: Ensure that the FILESTREAM access level for the database is less than 2.  If the FILESTREAM access level cannot be obtained consult a DBA about why accessing this information is failing for the user running the installation.
  
  

• Validate database mirroring mode

  Purpose: To ensure database mirroring is disabled for the installation/upgrade.
  Error Message(s):
  Unable to obtain the mirroring mode of the database.
  Unable to determine the current database mirroring mode. The query returned a null or empty value for the current database, which indicates that the database server was unable to determine the mirroring mode of the database.
  The currently selected database is configured for mirroring.  Please disable mirroring for the selected database.
  Possible Resolution: Contact a DBA to disable database mirroring for the duration of the installation/upgrade.
  
  

• Validate database server max memory setting

  Purpose: To test that the max server memory setting for SQL Server is not set to the default setting.
  Warning Message(s):
  Database max server memory is configured to the default value which is very large. It is recommended that this value is changed.
  Possible Resolution: This warning message only needs to be addressed when the SQL Server resides on the same system as the IIS server hosting the Console software. If a dedicated SQL Server is being used then this warning can be ignored. If the SQL Server is on the same system as IIS hosting the Console software, then the max SQL Server memory should be set to a value that is at least 5% less than the avialable memory for the entire system. Failure to do so may cause the SQL Server to use so much memory that it starves the Windows OS and IIS of memory, which causes the Console software to fail.
  
  

• Check for SQL Server Service Broker queues

  Purpose: To attempt to identify and remove SQL Server Service Broker queues from the database to prevent them from interfering with the database upgrade process.
  Error Message(s):
  There are still SQL Server Service Broker queues present in the database. This may cause database upgrade failure. Please try restarting SQL Server and re-run the validators.
  Unable to check for the existence of SQL Server Service Broker queues. Error: [EXCEPTION TEXT]
  Possible Resolution: Re-run the validators a few times, as each time they will attempt to remove the SQL Server Service Brokers associated with the Identity Finder database. This should eventually work, however, if it does not, contact a DBA and have them take the Identity Finder database offline for a minute and then put it back online, or restart the SQL Server Service (only if the SQL Server is not shared and doing so will not affect other applications). Once the database is taken offline and put back online, or the SQL Server Service is restarted, try running the validators again.
  
  

• Validate database server version

  Purpose: To validate that the SQL server and it's underlying OS are supported versions.
  Error Message(s):
  Unable to obtain the current database server product version.
  The selected database server does not meet the minimum requirements. The database server must be at least version [MINIMUM REQUIRED DB SERVER VERSION] and must not be an equal or greater version than [MAXIMUM SUPPORTED DB SERVER VERSION]. The selected database server is at version [CURRENT DB SERVER VERSION].
  Failed to connect to the database. [SQL SERVER DB ERROR]
  Unable to obtain the current compatibility level for the master database.
  Unable to obtain the current database server's host OS version information.
  The master database does not meet the minimum requirements. The master database server must be at least at compatibility version 100 (SQL 2008 or higher) and the selected master database server is at compatibility version [CURRENT DB COMPATIBILITY LEVEL]
  The selected database server's host OS does not meet the minimum requirements. The database server's host OS must be at least version [MINIMUM SUPPORTED DB SERVER HOST OS VERSION] and the selected database server's host OS is version [CURRENT DB SERVER HOST OS VERSION]
  Possible Resolution: Install the Identity Finder Enterprise Console on a supported version of SQL Server and make sure the SQL Server is running on a supported host OS version.
  
  

• Validate free space

  Purpose: To ensure that the drives where the database log files reside have sufficient free space for the upgrade to succeed.
  Error Message(s):
  The free space on the disk that contains the database log file may be insufficient for the upgrade.
  Possible Resolution: In order for database upgrades to complete, data often needs to be migrated from an old format to a newer format. This process requires space in the log database. First we calculate the size of the database, then we calculate the size of the database logs. In order for an upgrade to succeed free space for the logs needs to be about twice the size of the size of the database. For example, if the database is 5GB, then the database logs (regardless of their current size) require approximately 10GB of free space to grow during the installation. In this case we check the location of the log file and if there is less than 10GB free space, we issue this warning. In the case where log files reside on multiple drives, each drive must have twice the free space of the entire size of the database. For this example if log files are on multiple drives each of those drives requires 10GB of free space. Consult your SQL DBA to either free the required space on the drive or drives where the log file or files reside, or have the DBA move the log files to a new location with adequate free space and run the installation again.
  NOTE: This warning can be ignored, but in doing so if the installation fails the target environment will be in an unusable and unsupported state.
  
  

• Validate SQL Server 2012 Packages

  Purpose: To ensure that appropriate prerequisite packages are installed for Console version 7.5 and above.  Starting with version 7.5, the Console applications require certain SQL Server 2012 packages (but not the SQL Server itself) to be installed in order to communicate with any SQL Server database.  SQL Server does not need to be installed on the application server, and SQL Server 2008 can be used for the database.  These packages are simply used for connectivity between the application and SQL server only.
  Error Message(s):
  Microsoft SQL Server 2012 Native Client version 11.0.2100 or later is required.
  SQL Server 2012 System CLR Types version 11.0.2100 or later is required.
  SQL Server 2012 Shared Management Objects version 11.0.2100 or later is required.
  Possible Resolution: Download and install the missing packages from Microsoft at this download link: http://www.microsoft.com/en-us/download/details.aspx?id=35580
  The following packages are required:

  • Windows 2008 32 bit:
    • ENU\x86\sqlncli.msi
    • ENU\x86\SQLSysClrTypes.msi
    • ENU\x86\SharedManagementObjects.msi
  • Windows 2008 64 bit, Windows 2008 R2+:
    • ENU\x64\sqlncli.msi
    • ENU\x64\SQLSysClrTypes.msi
    • ENU\x64\SharedManagementObjects.msi

• Validate Installed Packages

  Purpose: To ensure required prerequisite packages are installed.  Starting with version 7.5, the Console applications require certain prerequisite software to connect to the SQL Server database.
  Error Message(s):
  The following packages need to be installed:
     Visual C++ 2005 SP1 ATL Security Update Redistributable
  Possible Resolution: Download and install the Visual C++ 2005 SP1 ATL Security Update Redistributable from Microsoft at this link: http://www.microsoft.com/en-us/download/details.aspx?id=14431
  For Windows 2008 32 bit download and install "vcredist_x86.exe", and for all other supported operating systems download and install "vcredist_x64.exe".
  
  

• Validate Existing Active Directory Settings

  Purpose: To ensure Active Directory settings, if used, are valid and can be upgraded.
  Error Message(s):
  The AD configuration is invalid. The AD data upgrade process will not be able to complete.
  Possible Resolution: Check the AD settings in the Console Administrator Tool (CAT) and refer to the online documentation to make sure the settings are valid before upgrading.
  
  

• Validate IIS is installed

  Purpose: To ensure that IIS is installed and configured.
  Error Message(s):
  IIS is not installed. IIS must be installed before the setup wizard can continue.
  Possible Resolution: Install IIS using the server manager or Programs control panel.  For further information please contact a qualified Windows system administrator.

• IIS configured for 64-bit mode

  Purpose: To ensure that 32-bit IIS mode is not being used on a 64-bit operating system.
  Error Message(s):
  IIS is configured for 32-bit, but the operating system is 64-bit. You must configure IIS to run 64-bit applications.
  Possible Resolution: Either disable 32-bit mode to ensure that IIS runs in 64-bit mode (the same as the OS) or use a different server that is running IIS under the same architecture as the OS.  For further information please contact a qualified Windows system administrator.

• IIS 5.0 isolation mode is not enabled

  Purpose: To ensure that IIS 5 isolation mode is not enabled.
  Error Message(s):
  IIS is configured for IIS 5 Isolation Mode. This configuration is unsupported.
  Possible Resolution: Either disable IIS 5 Isolation Mode or use a different server that is not using IIS 5 Isolation Mode.  For further information please contact a qualified Windows system administrator.
  
  

• Validate IIS Bindings

  Purpose: To ensure that HTTPS can only be configured if IIS has HTTPS bindings.
  Error Message(s):
  The HTTPS bindings are not configured in IIS. You need to configure the bindings or select HTTP Only in CAT.
  Cancel the current installation, open the CAT, select HTTP Only for Enabled Protocols in the Web Applications tab. Once that is done, retry the installation.