Data-Collection Package Output Logging
Applies To: Windows 7, Windows Vista
When you are creating a data-collection package (DCP) in the Application Compatibility Manager, you can select an output location for your log files. The configuration options are:
- Select a default ACT Log Processing share location. If you use this option, the data-collection package automatically writes the log files to the ACT Log Processing share. If the ACT Log Processing share is unavailable when the specified upload time interval is reached, the data-collection package will make two more attempts. If the problem persists, the data-collection package will store the log file in one of the locations listed in the following table, based on the operating system. All files are then retried during the next upload interval.
| Operating system | Location |
|---|---|
Windows® 7 Windows Vista® Windows Server® 2008 R2 |
%SYSTEMDRIVE%\Users\All Users\Microsoft\Application Compatibility Toolkit\LogProcessor\Failed |
Windows Server® 2003 Windows XP Windows XP with Service Pack 2 (SP2) |
%SYSTEMDRIVE%\Documents and Settings\All Users\Application Data\Microsoft\Application Compatibility Toolkit\LogProcessor\Failed |
- Select the Local (%ACTAppData%\DataCollector\Output) location. If you use this option, the data-collection package creates the log files on the local system (as shown in the table later in this topic) and the computer administrator must manually copy the files to the ACT Log Processing share location. This is a good option for mobile users who are not always connected to the network.
Important
A mobile user might not generate compatibility data because of the irregularity of the corporate network connection and the length of time the data-collection package should run. If the data-collection package cannot upload data to the network share after three attempts, the log files are stored in the failed location, as shown in the table later in this topic. If the duration of the data-collection package has expired the next time the user connects to the network share, then the data-collection package does not attempt to upload the information again and instead uninstalls itself, removing any of the data previously stored in the failed location.
| Operating system | Location |
|---|---|
Windows 7 Windows Vista Windows Server 2008 R2 |
%SYSTEMDRIVE%\Users\All Users\Microsoft\Application Compatibility Toolkit\DataCollector\Output |
Windows Server 2003 Windows XP Windows XP with Service Pack 2 (SP2) |
%SYSTEMDRIVE%\Documents and Settings\All Users\Application Data\Microsoft\Application Compatibility Toolkit\DataCollector\Output |
- Type an alternate network share location. If you use this option, you must verify that the data-collection package service can write to the location. This is a good option for companies that are geographically diverse (for example, with branches in North America and in Europe). An IT administrator can create data-collection packages and file shares individually for North America and for Europe. This enables administrators at a central location to move all of the collection log files to a central location. These log files are then mapped to the ACT Log Processing share for final processing and entry into the ACT database.
See Also
Concepts
Deploying a Data Collection Package
Configuring the Application Compatibility Toolkit
Phase 1: Collecting Your Compatibility Data
Troubleshooting ACT Setup