System Requirements
Optional Components
What's New
Technical Notes
Known Issues
Contacting Compuware Technical Support
This section describes the minimum requirements for running the TrackRecord Windows Client.
The following system requirement is necessary for users to access the Web Server through a browser from their client machine:
The following sections detail the minimum system requirements necessary for installing each optional TrackRecord component.
All the client requirements listed previously, as well as the following minimum system requirements, are necessary to install a server that will house the database. This component can be installed on a central server on your network. A minimum of one server must be installed on a network for database access.
All the client requirements listed previously, as well as the following minimum system requirements, are necessary for installing TrackRecord’s email notification service:
Note: Compuware recommends Microsoft Outlook be installed on the Server where AutoAlert is installed to facilitate configuration and testing of the mail profile.
All of the client requirements listed previously, as well as the following minimum system requirements, are necessary for the machine upon which the Web Server component is installed:
TrackRecord administrators may enforce a minimum length for all users’ passwords in the system (see TrackRecord Service Pack Available).
If the minimum length is zero, then no minimum password length will be enforced. If the minimum length is non-zero, the minimum will be enforced when:
Administrators create new users
Administrators change a user’s password
A user changes the password
Current users and their passwords will not be affected. If a user currently has no password set, they will continue to be able to login without a password. If they have a password set which is less than the newly-entered minimum length, they will continue to be able to use their current password. However, as soon as the Admin or that user attempts to change his password, the minimum length restrictions will be enforced.
The information contained in the User's Guide has been assimilated into the Online Help to expedite searching and accessing TrackRecord information.
Compuware TrackRecord can run in VMWare Workstation 5.5, Player 1.0, Server 1.0, and ESX/GSX Servers 3. The following requirements must be met:
The VMWare Bridged Networking type must be selected.
Environments must be running Compuware licensing in concurrent mode (node-locked licenses are not supported).
Due to major changes in several tables throughout the TrackRecord database, the previous client (6.2.x and prior) will not be able to connect to the new database. All existing TrackRecord data will have to be converted to the new schema. A stand-alone migration utility is provided to upgrade the existing TrackRecord schema to the schema level required for TrackRecord 06.03.00
A major schema change in TrackRecord 06.03.00 requires the installation of a TrackRecord 06.03.00 client. TrackRecord 06.03.00 supports the silent installation of TrackRecord clients and server. Refer to the Installation Guide for a detailed description of the installation process.
TrackRecord 06.03.00 provides record locking to prevent two users from editing an item at the same time or losing data when one user is editing an item and another user is viewing the same item.
TrackRecord 06.03.00 allows users to lock a particular item for modifications by clicking the “Edit” button or opening the item in edit mode. If a user has an item locked for edit then the user who tries to open the same item is notified that the item is locked. The notification message displays user’s name, machine name, date and time the edit lock was created.
When the item is in the read-only (view) mode, the user must click the “Edit” button in the toolbar to enter into edit mode. If an edit lock cannot be obtained, a notification is presented to the user.
TrackRecord 06.03.00 improves history record integrity. The present “change history” is dynamic, if an element of the history record is modified, the history also gets modified to reflect the change. The change history in TrackRecord now provides a true audit-trail of the changes made to the item.
This release of TrackRecord is a major release focused on data integrity and stability. Therefore, integrations with certain obsolete technologies have been discontinued in TrackRecord 06.03.00 These include:
For more information on these dropped features, please contact Compuware Customer Support.
In TrackRecord 06.03.00, integration is only provided for passive agents in ClientVantage 9.9. Support for integration with ClientVantage 10.0 will not be available.
TrackRecord supports integration with the following versions of DevPartner Fault Simulator
This section includes technical information that may affect how you use the product.
After installing the TrackRecord 6.3 product, you may choose to install the TrackRecord Service Pack from:
Installation media\CARS Setup\QACenter\Service Pack\TrackRecord
The Service Pack contains defect fixes as well as Enforcing Minimum Password Length functionality.
If the TRDBAService service does not start, the TrackRecord Database Administration Utility is unable to start. If the service does not start, the reason may be a corrupt TRDBAConfig.xml file. Verify this by checking the event log. Delete this file and restart the utility. Note: Uninstalling and installing TrackRecord does not help because the installation routine will not replace an existing TRDBAConfig.xml file and the uninstallation routine does not delete this file in order to preserve settings in case of an upgrade.
If a task is manually removed from the TRDBAConfig.xml file, it's placeholder is consumed. This causes the subsequent task created to have a duplicate task ID, which results in a crash. Ensure that the task IDs are properly re-sequenced in the TRDBAConfig.xml file to avoid this issue.
The Database Administration Utility writes most of its output to the Windows Event Log. If the Event Log is filled, the messages will be discarded. If necessary, set the Event Log to automatically overwrite the oldest messages to prevent losing any new messages. For additional information, refer to the online help for Microsoft Windows.
To enable a computer running Windows XP Service Pack 2 to serve other machines, you must configure the Windows Firewall.
To enable the server to serve Windows clients on other machines:
Click Start>Settings>Control Panel>Windows Firewall.
Select the Exceptions tab.
Click Add Program.
Double-click on TrackRecord Server.
Click OK.
To enable the server to serve Web clients on other machines:
Click Start>Settings>Control Panel>Windows Firewall.
Select the Exceptions tab.
Click Add Program.
Click Browse, navigate to C:\WINDOWS\System32\inetserv\inetinfo.exe, and click OK.
Double-click on inetinfo.exe.
Please see Install Guide for detailed instructions on running TrackRecord Web Server on Windows Server 2003.
During an import or export of TrackRecord data, the Date/Time regional settings must be the same on both machines in order to keep the original Date/Time format.
Importing causes the workflow to lose some of its status/action relationships. After these relationships are recreated, the workflow operates normally.
When creating COM applications, all login and logout calls should be done from the same thread as nmdbinfo is singlethreaded.
When a new item is created by means of Save and Duplicate, the status of the newly created item is reset to the initial state and the date is set to the current date.
This occurs when Editing Workflow, Edit Types, Edit Rules, Check Database, Rebuild or with Group Administration.
When you log on to TrackRecord Client as an administrator and begin one of the activities mentioned above, a message may appear informing you that active users are logged on.
The message box also appears when multiple Admin users are logged on at the same time. Making changes to the Workflow or Edit Types in this situation may cause the database to react adversely.
A maximum of 12 databases can be open concurrently. If 12 are open and you attempt to open an additional database, an error will display. To open additional databases, modify the TrackRecord Server configuration. To do so, perform the following procedure:
The maximum length of a field name is 31 characters.
TrackRecord does not support double-byte languages, such as Japanese, Korean, and Chinese or right-to-left languages, such as Hebrew and Arabic.
Compuware recommends that you do not move or rename TrackRecord's Databases or Backups folders. Doing so will cause a loss in TrackRecord functionality. However, you can safely move and rename the subfolders.
When creating a new user, any queries marked for electronic notification that apply to the new user will return all results during the next AutoAlert poll. This may result in a large volume of AutoAlert emails being sent to the new user during the first AutoAlert poll.
If a Web Server login fails, you will not receive an error message from within DCOMCNFG. Instead, when an attempt is made to login to a database through the Web Server, you receive an automation error indicating that the configured identity is not correct. This is due to a DCOMCNFG login failure. To remedy this situation, ensure that the log in information is correct and ask a network administrator to grant the NT account "log on as a service" privileges.
There are two ways to log on to a database server not specified during installation:
1) At the login prompt, you can specify the database server using the following convention in the database field:
Hostname:databasename
Where “Hostname” is the DNS name or IP address of the alternate TrackRecord database server and “databasename” is the name of the database.
2) At the command line, you can use the –s switch to specify the server’s hostname. The convention is as follows:
<path to trackrecord executable> -u<login id> -p<password> -s<server> -d<database>
When making changes to the type structure, templates, user and group administration, rules, or other processes, these changes are not reflected to the Web Server component if there are active Web session processes running. To ensure that your updates are immediately reflected in the Web Server, follow these steps:
This section describes known issues related to the current release of TrackRecord.
If TrackRecord version 06.01.01 or earlier is installed on your computer, or if you have a Beta version installed, Compuware strongly recommends that you uninstall the previous version. If prompted, reboot your PC before proceeding with the installation of TrackRecord.
If the installation detects a previous version, yet you have uninstalled all previous versions, check for the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{CB535B40-A00D-45FF-8329-40B8E5EAFACB} registry key and delete it if it exists.
You need to upgrade QADirector or CARS Portal to Version 5.3.1, if you are installing TrackRecord 06.03.00. If you install TrackRecord 06.03.00 on a machine running QADirector or CARS Portal with versions earlier than 5.3.1, they will no longer work properly.
If you have a trial license and install TrackRecord and the TrackRecord Web Server on the same workstation, you must start TrackRecord before starting the Web Server or your system may hang. If this happens, reboot. Then, start TrackRecord before starting the Web Server.
The size limits of requests sent to IIS can be configured in Windows 2003. If they are not configured properly, attachments can fail. Two settings in Windows 2003 can limit the size of a request.
Open the metabase.XML file which is located in C:\Windows\System32\Inetsrv. Find the line "AspMaxRequestEntityAllowed" and change the value to at least "12582912".
Change the value of the registry setting HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\w3svc\parameters\MaxClientRequestBuffer to at least "12582912".
The TrackRecord limit on file attachment size per item is 12 MB. After attachment, these files are compressed, stored in attach.dat, and can only be viewed through the TrackRecord Client or Web Server. Their compressed physical size when stored in the database can be notably smaller than the original file size.
By default, when IIS is installed on any version of the Windows Server 2003 family, IIS only serves static content (HTML). To permit IIS to serve dynamic content, the administrator must unlock this content in the Web service extensions node in IIS Manager. To do this for the TrackRecord Web Server, the administrator must enable Active Server Pages and the ISAPI files used by the Web Server by either enabling a pre-existing Web service extension or adding a new Web service extension and enabling it.
Open IIS Manager, expand the master server node or Servername node, and select the Web service extensions node.
In the right pane of IIS Manager, right-click the Active Server Pages extension.
Select Allow.
Click Ok to save your changes.
Open IIS Manager, expand the master server node or Servername node, and select the Web service extensions node.
In the right pane of IIS Manager, right-click All Unknown ISAPI Extensions.
Select Allow.
Click Ok to save your changes.
Open IIS Manager, expand the master server node, and then select the Web service extensions node.
In the right pane of the IIS Manager, click Add a new Web service extension under Tasks.
In Extension, type a name for the extension that you want to add. For example, TrackRecord ISAPI Extensions.
In the Required files box, click Add, and then select the path and the name of the TrackRecord files that will handle requests for the TrackRecord Web Server. These files are typically located in c:\inetpub\cgi-win. The files you need to add are itemview.dll and outline.dll.
Select Set extension status to Allowed.
Click Ok to save your changes.
The check box field is read-only in a Web Server Outline Report.
When printing an Outline Report in the Web Server, click in the frame containing the data that you wish to print before clicking the Print button.
Compuware recommends that you do not add or delete any fields on the Attached File type. Doing so will result in an error when attempting to attach a file through the Web Server.
In the Web Server, Outline Report columns are read-only and can only be sorted in the TrackRecord Windows Client. To change the way your Outline Report columns are sorted:
If JRE is not installed, the Monitor Statistics window may not respond if you click Manage>Monitor Statistics.
TrackRecord's Webserver does not recognize time/date settings for the Norwegian language.
In the Webserver, after editing an existing item or creating a new item within a combo box or drop-down field; do not click Save and Release Lock. Instead, click the Save icon to save any changes or additions.
If an Admin user has an item open in edit mode and a non-admin user with Delete privileges highlights and clicks Shift+Delete on the same item and clicks Cancel on the 'Record In Use' message, all the items under the highlighted items get deleted.
Deleting a field in the Type Editor will disable all the 'Insert field' options until the type is saved, closed, and re-opened.
Currently, it is not possible to merge items from the sub-type level.
If you run a check database on a database not currently online, that database is automatically put online when the check is completed.
Please note that tasks scheduled to run in the Database Administration Utility as well as settings in AutoAlert are not kept after migrating the database. You must reschedule any tasks scheduled in the Database Administration Utility and re-enter any settings you wish to keep in AutoAlert.
Also, if there are duplicate items in the database after migration, please contact technical support.
If a popup message from Microsoft Windows appears notifying of a Software Update on MS Windows Server 2003, TrackRecord Server hangs and you cannot connect to the TrackRecord database from the Windows client, nor from the Web client. You must wait for the download to finish, restart the machine and then the TrackRecord database again becomes accessible.
TrackRecord currently does not support reconciling the database through the Database Administration Utility.
The default time in the Database Administration Utility is taken from the system clock of the machine running the TRDBAService not the client.
An Administrator user running a check database cannot have a home page set in their browser if they are using a batch file to run check database. This will cause a dialog to appear at the end of the check and the system will not respond.
In TrackRecord, "Team Member" is a special type that identifies a user and is associated with the TR_User tag. Although you may create a child type of Team Member, do not attempt to create a child of the child type of Team Member. Doing so will cause unexpected results.
This is an example of a correct association:
This is an example of an incorrect association:
QAManager (Unexpected results will occur)
When you delete multiple fields, it is best to note the order that the fields were deleted. If you recreate the fields, you must do so in the reverse order that they were originally created. Then, perform a database rebuild and a Check Database to ensure data integrity.
When creating a new assignment type, ensure that you select the type and click New. Do not double-click the assignment type to open the dialog box. Doing so will create empty items and can result in loss of data integrity.
The 'Send Message' in the Active Users window has to be clicked twice to send messages.
When two or more Templates are created and are "Applied to All" with different fields populated, all the templates are applied. When the same fields are populated, the first template is applied.
When exporting to an Access Database, Multi Item List fields produce the following error: "Run-time error '3163 The field is too small to accept the amount of data you attempted to add." Insert or paste less data to work around this issue.
The search string is limited to 33 characters. If it is not possible to modify the search string to fit these parameters, create a query to search for the string.
When importing duplicate items into the database, ensure that the Discard Duplicates option is selected. Otherwise, the existing item in the database will also be deleted.
The stack bar graph only displays results from the first page of an Outline Report. To display your Outline Report in a graph, select bar or pie graphs instead.
Executable buttons do not work in the web interface.
TrackRecord client does not save last window opened even though "Open the windows that were open at the end of the last session" radio button is selected.
If a Guest User clicks Advanced Search, the following message appears "You don't have sufficient rights to create a new Defect".
The addition of radio buttons to a type that already contains items, may cause a crash when attempting to Save and Close the type in Type Editor. The workaround is to either redo the changes a second time, or make certain that the last task within type editor is not the addition of the radio buttons (that is, perform another task before saving).
Compuware Customer Support can assist you with all your technical problems, from installation to troubleshooting.
Prior to contacting customer support, gather the following information:
800.538.7822
Refer to Compuware's Frontline support web site for fast access to critical information about your QACenter product. You can read and print documentation, download product fixes, review frequently asked questions, or directly e-mail Compuware with questions or comments. The first time you access FrontLine, you are required to register and obtain a password.
Refer to Compuware's corporate web site at http://www.compuware.com for information about Compuware customer support policies and problem resolution process.
Customer Support
Compuware Corporation
One Campus Martius
Detroit, MI 48226-5099
End of TrackRecord Release Notes
©2007 Compuware Corporation. All rights reserved. Unpublished rights reserved
under the Copyright Laws of the United States.