Sensitive Content Manager 2.2.2 - Installation Guide

NOTE: You must use the same version of the install media that was used in your deployment.

NOTES:

1.Third party components like Erlang and RabbitMQ must be manually uninstalled.

2.The SCM databases cannot be removed with the SCM windows installer. To remove the SCM databases you could delete the databases using Microsoft SQL Server tools.

3.In a standalone deployment, all SCM components except the SCM databases and certificates are removed.

4.In a distributed deployment:

a.Only the components from the computer are removed where the SCM windows installer is being used. For example, if the removal steps are followed on the SCM Server only the SCM components installed on the SCM Server are removed. If dedicated servers are used for other services, then these components must be removed separately from each of those servers.

b.The shared folder is not removed. This folder must be deleted manually to ensure that sensitive files are disposed carefully.

NOTE: Take a backup of the SCM databases if you plan to remove components.

Error Message

Resolution

License key <LicenseKey> has expired. Please contact your Quest sales representative.

Contact Quest Technical Support.

License key <LicenseKey> is invalid. Please contact your Quest sales representative.

Contact Quest Technical Support.

Please activate your license.

Click Activate License for online activation or click Activate Offline for offline activation. If the license activation is successful, a confirmation message opens.

The license key <LicenseKey> does not match the currently activated license key <activatedLicenseKey>. Please activate your license again.

Try reactivating the old license, and then activate the new license.

An error occurred while copying the activation string to the clipboard.

Try again. If the error persists, contact Quest Technical Support.

An error occurred while saving the file.

The folder may be read only or may not exist. Try saving to a different folder. If the error persists, contact Quest Technical Support.

An error occurred while reading the file.

The file may be corrupted. Try generating the file again by attempting an offline activation. If the error persists, contact Quest Technical Support.

Error Message

Resolution

The folder <folderpath> is invalid or does not exist.

The destination or temporary folder that was specified should exist. If you choose to keep the default settings, then the folder will be created by the installer.

The folder <folderpath> is read only.

Remove the read restriction on the destination or temporary folder.

An error occurred while creating the destination folder.

Ensure that the destination folder exists, and the account used for installing the product or service has permissions to create the destination folder.

An error occurred while validating the destination folder.

Ensure that the destination folder exists, and the account used for installing the product or service has permissions to write to the destination folder.

An error occurred while selecting the destination folder.

Ensure that the destination folder exists.

The folder must be a local folder.

The destination folder for installing the product or service cannot be a shared folder.

An error occurred while ensuring user <serviceIdentityUserName> permission on <targetPath>.

Ensure that the temporary folder exists, and the account used for installing the product or service has read/write permissions on the temporary folder.

An error occurred while validating the temporary storage folder.

Ensure that the temporary folder exists, and the account used for installing the product or service has read/write permissions on the temporary folder.

An error occurred while selecting the temporary storage folder.

Ensure that the temporary folder exists.

The folder <folderpath> must be a shared folder.

If a service instance is installed on a dedicated server for scalability, the temporary folder selected must be a shared folder.

Insufficient disk space detected for temporary folder <folderPath>. Select a folder on a larger drive or a dedicated UNC location.

The expected space requirement is approximately double the size of the physical RAM. For example, if you have 32GB of RAM then you must have 64GB of available space on the local drive. You can clear some unused files to recover the required space or select a folder on a larger drive or select a dedicated UNC location.

Error Message

Resolution

An error occurred while validating the user’s credentials.

Please check the windows log in credentials of the user that will run the Windows service or re-enter the correct credentials.

The specified account does not exist, or the user’s credentials are invalid.

Check the windows log in credentials of the user that will run the windows service, or re-enter the correct credentials. if the user is a domain user, please verify the user account in the domain active directory.

Access to the Service Connection Point is denied

Ensure that the domain user or LocalSystem account that is used to run the windows service has been added to the Service Connection Point of the SCM Server in the active directory and all permissions have been granted. For more information see Steps to grant permissions to the SCM Service account for the Service Connection Point.

Unable to reach the SCM services

1.Log in to the dedicated service server. Open a command window with Start > Run > cmd. At the command prompt run the command ping <SCM Server IP Address> and ensure that you get the responses to verify that SCM Server is reachable.

2.Log in to the SCM Server and verify that the ports are open. For more information see Steps to configure the inbound rules for the service ports on the SCM Server.

3.In the SCM Server open the Internet Information Services (IIS) Manager and verify that the Application Pools and Sites related to SCM are running.

An error occurred while checking for existing Service Connection Point.

Ensure that the domain user or LocalSystem account that is used to run the windows service has been added to the Service Connection Point of the SCM Server in the active directory and all permissions have been granted. For more information see Steps to grant permissions to the SCM Service account for the Service Connection Point

A Service Connection Point already exists for '<computerName>' but the Local System account ('<SCM_MACHINE_FRIENDLY_DOMAINNAME}\\{computerName>$') may not have write permissions.

Ensure that the domain user or LocalSystem account that is used to run the windows service has been added to the Service Connection Point of the SCM Server in the active directory and all permissions have been granted. For more information see Steps to grant permissions to the SCM Service account for the Service Connection Point.

Error Message

Resolution

Unable to connect to the SQL Server <sqlServerName> using service account <serviceIdentityUserName>.

Verify that the SQL Server is accessible to the logged in user. If a firewall is active, ensure that an inbound port rule on the SCM Server is created for port 1433.

The specified account does not have the required permissions on SQL Server. 

Verify that the user exists in the SQL Server with appropriate log in rights. This is usually the case with orphaned users.

The installation account <sqlUserName> must have the 'dbcreator' and 'securityadmin' roles assigned in <sqlServerName>.

The logged in user who is installing the SCM components must be granted the 'dbcreator' and 'securityadmin' roles in the SQL Server.

The service account <serviceIdentityUserName> must have the 'db_owner' role assigned in <sqlServerName> for database(s): <missingDbOwnerDatabaseNames>.

The SCM Service user account on a distributed node must be granted the 'db_owner' roles in the SQL Server. The SQL Server must be accessible to the SCM Service user. If a firewall is active, ensure that an inbound port rule on the SCM Server is created for port 1433.

Insufficient disk space detected on the SQL Server database drive.

The expected space requirement is approximately double the size of the physical RAM. For example, if you have 32GB of RAM then you must have 64GB of available space on the SQL Server database drive. You can clear some unused files to recover the required space or move your database default drive to a disk drive with the required disk space.

The ScanDetail table contains a large volume of data that impacts report generation. Please contact Quest Technical Support.

Additional configuration that is required is described in the topic Preparing for the upgrade or you may contact Quest Technical Support.

The Logs table contains a large volume of data that impacts the schema upgrade. Do you want to truncate the Logs table? If you click No, please contact Quest Technical Support.

If there are more than 40,000 records in the Logs table in the SCMLogs database, then the indexing process could take a while or may timeout and fail. If you select Yes, all records from the Logs table will be removed. If you select No, you must contact Quest Technical Support to index the table.  

Available disk space for database drive '{databaseDrive}' was not found. The SQL user does not have permissions to retrieve the free disk drive space.

The installer encountered a problem while checking for available disk space on the database drive. Please contact Quest Technical Support.

Error Message

Resolution

Please enter a port number between 1 and 65535.

Specify a port number that is within the bounds indicated.

Port number is already in use.

Specify a different port number that is within the bounds indicated.

An error occurred while validating the IIS web site information.

This is a generic error. If the error persists, contact your IT resource or contact Quest Technical Support.

An error occurred while creating the self-signed certificate <friendlyName>.

Try creating another self-signed certificate.

For the SCM Server, ensure that the self-signed certificates are kept in:

·Trusted Root Certification Authorities store, and

·Personal or Web certificate store

If you have a Verisign, Thawte or another commercial certificate then they do not need to be placed in the Trusted Root Certification Authorities store.

An error occurred while binding certificates.

Verify that the certificate is in the correct folder or regenerate the certificate as it may be corrupted and try again or contact Quest Technical Support.

An error occurred while validating the custom certificate .

Custom certificates are being used. Contact Quest Technical Support.

The certificate is either not valid or not trusted by this computer. Verify that the certificate listed in the Certification Path is both valid (not expired) and properly installed on this computer.

Verify that the certificate listed in the Certification Path is both valid (not expired) and properly installed on this computer.

The certificate with thumbprint '{thumbprint}' is no longer present in the certificate store.

Verify that the selected certificate exists in either the Personal or Web Hosting certificate stores.

The host name '{hostname}' must match one of the entries in the certificate's Subject Alternative Name ('{list of SANs}').

Ensure you use one of the entries in the Subject Alternative Name (SAN) in the certificate you have chosen.

To view the SAN:

1.Open Settings > Manage computer certificates.

2.Locate the certificate in either the Personal or Web Hosting stores.

3.Open the certificate and go to the Details tab.

4.View the values for the Subject Alternative Name field.

Security group <groupName> does not exist. 

or 

An error occurred while verifying security group <groupName>.

Verify that a valid security group exists in the domain active directory.

The computer must be joined to a domain.

The computer should be added to the domain. Start > Run > sysdm.cpl to open the System properties window. Add your computer to the domain from there.

The host name '{hostname}' cannot be resolved. Ensure the host name has a valid IP address.

Ensure the host name has a valid IP address.

Error Message

Resolution

Unable to connect to the RabbitMQ.

Check that RabbitMQ is accessible. Verify that the Rabbit.ClusterCertificate (if applicable) is in the certificate store. Verify that the connection string is valid. If the connection uses amqp then port 5672 must be open, or if connection uses amqps (secured) then port 5671 must be open.

RabbitMQ is already installed. Click 'OK' to remove the previous version or 'Cancel' to cancel this installation

A mismatch between the installed version of RabbitMQ and the required version was detected. Click OK to allow the installer to uninstall and install the required version of RabbitMQ.

An error occurred while validating the service bus connection string.

This is an unexpected error from the service bus. Check that RabbitMQ is accessible. Verify that the Rabbit.ClusterCertificate is in the certificate store. Verify that the connection string is valid. If the connection uses amqp then port 5672 must be open, or if connection uses amqps (secured) then port 5671 must be open or contact Quest Technical Support.

Insufficient disk space detected on the RabbitMQ drive.

The expected space requirement is approximately double the size of the physical RAM. For example, if you have 32GB of RAM then you must have 64GB of available space on the SQL Server database drive. You can clear some unused files to recover the required space.

The setup process cannot continue because a previous installation of RabbitMQ was performed by user '<UserName>'. You can either log in as '<UserName>' and restart the installer or contact your Quest Technical Support to relocate the RabbitMQ base folder.

This message appears when the installer detects that the user who originally installed RabbitMQ is not the user who is attempting the SCM upgrade. You can choose from two options:

·Log in as the original user and run the installer again to repair or upgrade SCM.

·Run the PowerShell script to relocate the RabbitMQ base folder from the previous user's %APPDATA% folder to a shared location like the %PROGRAMDATA% folder. The script is provided with the installation media (Support Tools > Rabbit Migration > Migrate-Rabbit.ps1). You can contact Quest Technical Support for assistance with this tool.

An error occurred while checking the user who installed RabbitMQ. Please contact Quest Technical Support.

RabbitMQ has not been installed properly on the system. Please contact Quest Technical Support.

The RabbitMQ Server path does not exist in Program Files.

RabbitMQ has not been installed properly on the system. Please contact Quest Technical Support.

An error occurred while updating the environment variable in the Process scope.

From version 2.2.1 the installer modifies the environment variable RABBITMQ_BASE. If the installer encounters a problem while loading or updating this variable, an error occurs. Please contact Quest Technical Support.