List of known issues in InTrust 9.5 Setup. (21854)

List of known issues in InTrust 9.5 Setup.

The following is a list of issues known to exist with regards to setup at the time of Quest release:InTrust 9.5.

CR0112449
You will have to log off and log on again once you have installed InTrust Manager to a location other than default. Otherwise, the InTrust Manager shortcut will not work.

CR0112184
If you have used the Add/Remove Programs dialog to uninstall InTrust, you will get the Modify/Repair/Remove dialog next time you launch InTrust setup from the CD.
Click Remove and wait until setup finishes, then run setup again.

CR0115384
The Quest InTrust Real-Time Monitoring Server service may not be able to start after installation. Setup will display the following error:
Error 214750037 (unspecified error).

Event ID 8202 is also written to the InTrust event log.
Restarting the computer resolves the issue.

CR0112303
You may get the following error while trying to install InTrust:
Cannot grant the following privileges:
Back up files and directories
Log on as a service
to <account_name>
Your Group Policy settings may be preventing setup from granting the privileges specified.

There must exist a Group Policy that controls the assignment of the specified privilege(s) in your environment. InTrust setup can neither override it nor check if the account inherits the required privilege(s) from a security group the policy applies to. Make sure the policy grants the specified privilege(s) to InTrust service account, either directly or through its membership in a security group, and click the Ignore button in the error dialog to proceed with the installation.

CR0117312
InTrust Monitoring Web Portal and InTrust Reporting Web Portal cannot be installed into a Virtual Directory with special characters (like !#$%^&()_+|][}{;,-=`~) in the name. An attempt to do so results in the following setup error:
Cannot configure Active Directory object 'VD_ITWEB'. Error -2147463168 E_ADS_BAD_PATHNAME.

CR0122748
If you receive the following error while upgrading an InTrust Server:
Error Code: 1603 Fatal error during installation.

First of all, check if all of the InTrust Server services have been stopped. Most often, it is Quest InTrust Real-Time Monitoring Server service that takes long to stop and causes the setup to fail with this error. If this is the case, quit the setup, make sure all of the Quest InTrust services have stopped and run the setup again.

CR0122347
If you receive the following error at InTrust setup:
Cannot configure default Audit Database. Error code: 0x80004005. Property value is invalid. Make sure the value is typed correctly. Unspecified error Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done. Property value is invalid. Make sure the value is typed correctly.

check if you have specified a database with a name that starts with a numeric character (0-9) as either Audit or Alert database.

The names of all InTrust Audit and Alert databases must start with an alphabetic character (a-z, A-Z).

CR0112182, CR0112212
On the Select Features step, InTrust setup wizard displays the required disk space only for the features you select in the tree. There are, however, some features required by those listed in the tree but not shown there because they are not user-selectable. Those 'hidden' features affect disk space requirements too. Click the Disk Cost button to see the more accurate numbers for required disk space calculated with regards to the features not displayed in the tree.

CR0112218
During InTrust setup, you may receive an error message stating that one or more specific privileges required for the InTrust Server service account cannot be granted to it because assignment of those privileges is controlled by a Group Policy. There is no way for the InTrust setup to check whether a Group Policy actually grants the specified privileges to the service account as a member of a group. If you receive this error message, verify that a Group Policy does grant the privileges and then click the Ignore button in the error message to proceed with the installation.

CR0112227
When InTrust installation fails and is rolled back, some registry keys it has created are not removed. This is controlled by the Microsoft Installer and cannot be handled from the InTrust setup code.

CR0152107
When you are running the configdb.sql SQL script on a pre-created InTrust configuration database to provide for not giving InTrust service account the database owner right for it, you may receive warnings like the following:
Cannot add rows to sysdepends for the current stored procedure because it depends on the missing object 'dbo.ITRTProcessingRule_change'.

These warnings may be ignored since they do not indicate of any problems that may affect the future InTrust operation.

CR0153990
Don't specify any existing Quest Active Roles Server database as the InTrust configuration database, since these two products have incompatible requirements to the system configurations of their databases.

CR0153344
At the installation of a report pack, setup prompts you for a name of a Report Library. When you are installing the report pack into an existing Report Library, any change you make to the Report Library name on this step will be ignored and the existing Report Library will not be renamed.

CR0153504
Components and configuration objects added to an existing InTrust installation by installing an individual Knowledge Pack cannot be consistently removed from InTrust by deselecting the related nodes on the 'Select Features' step of the Installation Wizard.

CR0151260
A path to the default repository is saved for the whole InTrust Organization when the first InTrust Server in that organization is installed, and defaults to a folder on that InTrust Server's computer local hard disk. Every InTrust Server in the organization uses this parameter 'as is' and treats it as a local path on its computer, which may be resolved to a location where no valid repository exists. If this is not the case, every gathering job configured to store data to a default repository actually stores it to a local disk on the computer of InTrust Server that processes the job. This may result in storing data at unexpected location. To avoid this, don't use the Default Repository predefined object in any gathering, import and consolidation jobs you set up. Instead, make copies of it with the Quest InTrust Manager snap-in, make the changes to the repository name, location, etc. if necessary, and always provide a name of an edited copy of a repository object when you configure a job.

CR0156239
When you install InTrust or upgrade it from an earlier version, you may receive the following error message:
Error 1335. The cabinet file '<cab_file_name>' required for this installation is corrupt and cannot be used. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.

One of the recommendations you can find in the Microsoft KB article 314810

CR0184325
If you have individual InTrust component(s) installed on a computer to a non-default path, be sure to not use the InTrust Suite setup to add other InTrust components to that machine. Install additional InTrust components by running their individual setup (.MSI) packages from the product DVD instead. This will let you avoid problems at both installation and uninstallation of those components in the future.

CR0190311
When you change the installation path for the InTrust Server node of the feature tree (on the Select Features step of the Quest InTrust 9.5 Setup wizard), installation paths for features down the tree is changed accordingly so that individual InTrust components are installed to subfolders of the folder you specify for InTrust Server. Note that this, however, does not apply to the InTrust Knowledge Portal component which does not inherit its installation path from the InTrust Server component and requires that you explicitly change the installation path if you need that.

CR0149166
It is recommended that you install the same set of InTrust components on all InTrust Servers in an InTrust Organization. Otherwise, you may have problems, for example, when switching the server that runs a task.