Failure to import log file
When using License Statistics to import data, partial/rotated logs are not supported; if associated checkins/checkouts are not contained in the same log file, the data import may fail. In such cases, you will see an error message such as: "Cannot import log file. Checkin at line 177 references a checkout from an earlier log file. Merge the log files and try again." (Where line 177 is the line that contains the checkin that has no associated checkout contained in the same log file.)
You can try to merge the partial log files into one log file that contains complete checkin/checkout information, as described below.
For Windows, type the following from a command line:
type file1 file2... filen > output.txt
For Linux, type the following in a console:
cat file1 file2... filen > output.txt
where file1 file2... filen are the names of any number of files to be merged and output.txt is the name of the file that will result from the merge.
Merging CodeCollaborator log files
CodeCollabolator rotates log files when the file reaches 10 MB. Merging the rotated log files will generate more accurate data than a "license.log" file.
To merge the log files for Windows, type the following from a command line:
type collab.log.n ... collab.log.1 collab.log >> import.log
To merge the log files for Linux, type the following in a console:
cat collab.log.n ... collab.log.1 collab.log >> import.log
"Ignoring the negative user status from log" error
If there are problems with an unmatched checkout/checkin combination, you may see a warning similar to the following in the License Statistics log file:
[2011-01-16 08:30:56] NOTICE: Importing log file C:\Program Files\X-Formation\License Statistics\importlog\slbfd.rl. Depending on file size importing can take several hours!
[2011-01-16 08:30:58] WARNING: Ignoring the negative user status from log!
This problem may occur if the user borrowed licenses before the logging started. The login may contain additional borrow checkins that will be ignored and the warning will be recorded. Normally, this warning does not indicate an ongoing problem. However, if the number of warnings is high, this may indicate a broken log file or errors parsing.
To resolve this issue, send us the License Statistics log file for investigation.