The following is a list of problems reported for iFileAudit along with the solutions that we have developed for them. If you have a problem that is not covered here, ask us via E-mail and we'll address your problem.
iFileAudit Release 8 Problem Reports:
iFileAudit Release 7 Problem Reports:
iFileAudit Release 6 Problem Reports:
iFileAudit Release 5 Problem Reports:
iFileAudit Release 8 Problems:
When we run the analysis process for a file, the CPF7053 error is being shown with reason code 4
A limit on the number of journal receivers allowed for a given journal is imposed by the IBM i OS. The best way to deal with this issue is to remove some of the journal receivers on file for the journal being used for the file. You must start with the oldest receiver and remove journal receivers until there are fewer than the number indicated in the error message (2,045). It is very important that you not remove any journal receivers out of the sequence in which they were created by the IBM i OS. Once this has been done, then the analysis process can be run. If keeping the old journal receivers is important to your security policy, you can save them into a save file or save them to offline storage before removing them.
History purge fails for large date range
This PTF fixes a problem with the history purge that caused it to fail when a large number of days was used for the time span to purge.
The fix for this issue is available as a PTF. This PTF can only be installed on a Release 8.02 version of iFileAudit. The correction is available in PTF package FAPTF803. E-mail support@kisco.com to request the PTF package.
Unintented trigger program registration in Bluescape
Under certain conditions, a trigger program registration could happen on a new file being added using the Bluescape interface. Customers using the Bluescape UI are advised to check for triggers on recently registered files and remove them.
The fix for this issue is available as a PTF. This PTF can only be installed on a Release 8.01 version of iFileAudit. The correction is available in PTF package FAPTF802. E-mail support@kisco.com to request the PTF package.
iFileAudit Release 7 Problems:
Menu option #4 on the MASTER menu fails with MCH3601
When running the DSPFILAUD command (option #4 on the MASTER menu), the process fails with an MCH3601 error message. This has now been corrected. While waiting for an update, all functions processed by the DSPFILAUD can be accessed using WRKFILAUD (option #1).
The fix for this issue is available as a PTF. This PTF can only be installed on a Release 7.05 version of iFileAudit. The correction is available in PTF package FAPTF706. E-mail us and request the PTF package.
iFileAudit Release 6 Problems:
There appears to be a discrepancy over the size of information stored by iFileAudit.
When this was reported to us, we found that the Size information being reported on each registered file did not include index size information. We have now added this information to the total Size being shown. In addition, we found the some information was missing from the detail file registration information being shown when using the iFileAudit browser interface.
The fix for these issues is available as a PTF. This PTF can only be installed on a Release 6.14 version of iFileAudit. The correction is available in PTF package FAPTF615. E-mail us and request the PTF package.
We started the Automatic Analysis but it doesn't look like anything is getting updated.
When a customer reported this to us, we discovered that the user profile issuing the start for the Automatic Analysis was not authorized as an "Admin" in the iFileAudit security feature. To avoid this issue coming up again, we have added a check in both the start and end processes for the Automatic Analysis to make sure that the user is properly enrolled as an "Admin" in iFileAudit.
This update also includes a change to the menus for iFileAudit to include a long format command line.
The fix for these issues is available as a PTF. This PTF can only be installed on a Release 6.13 version of iFileAudit. The correction is available in PTF package FAPTF614. E-mail us and request the PTF package.
MCH1210 can be issued during Automatic Analysis process.
The following issues have now been addressed:
The fix for these issues is available as a PTF. This PTF can only be installed on a Release 6.12 version of iFileAudit. The correction is available in PTF package FAPTF613. E-mail us and request the PTF package.
Several issues addressed - see details.
The following issues have now been addressed:
The fix for these issues is available as a PTF. This PTF can only be installed on a Release 6.11 version of iFileAudit. The correction is available in PTF package FAPTF612. E-mail us and request the PTF package.
I am seeing numeric fields in our audit history with 2 decimal points.
Under certain conditions, decimal fields could be rendered in the audit history showing 2 decimal points. This has now been fixed and a correction program for those customers affected is included in the PTF.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 6.08 version of iFileAudit. The correction is available in PTF package FAPTF609. E-mail us and request the PTF package.
I sometimes see a delay when running the WRKFILAUD command.
After a recent update to the software, a customer reported that the WRKFILAUD command (option #1 on the MASTER menu) was sometimes slow to start. We have found the source of this intermittent delay and adjusted for it.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 6.07 version of iFileAudit. The correction is available in PTF package FAPTF608. E-mail us and request the PTF package.
We are getting an error when running the Export function and selecting the *LONG file format option.
We found and corrected the error that was causing this problem.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 6.06 version of iFileAudit. The correction is available in PTF package FAPTF607. E-mail us and request the PTF package.
The HTTP server instance KISCOIFA issued an error code of CPF3C17.
Under certain obscure situations, the HTTP server instance that supports the iFileAudit Browser Interface feature could issue this error code. The programs have now been updated to avoid this problem in the future. No customers discovered this issue, but it did come up in some stress testing here in our test environment.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 6.01 version of iFileAudit. The correction is available in PTF package FAPTF602. E-mail us and request the PTF package.
When running a date and time audit report for all files being tracked in a given library, I am seeing files from different libraries on the report.
Based on this customer report, we discovered a problem with the selection criteria for the report. It has now been fixed.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 6.00 version of iFileAudit. The correction is available in PTF package FAPTF601. E-mail us and request the PTF package.
iFileAudit Release 5 Problems:
When I try to run multiple FILANZ processes in batch at the same time, one of the processes fails.
We have fixed the process so that you can now run multiple FILANZ processes concurrently.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 5.21 version of iFileAudit. The correction is available in PTF package FAPTF521. E-mail us and request the PTF package.
The batch file registration command seems to be skipping some files.
We found that the batch registration process that uses the CRTIFAREG command was skipping files with the object attribute of PF38. This has now been fixed and these files can be registered using the batch method.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 5.20 version of iFileAudit. The correction is available in PTF package FAPTF520. E-mail us and request the PTF package.
Daily Automatic Analysis start time keeps creeping up.
A customer brought this situation to our attention. They were running the automatic analysis once per day. They initially indicated a start time for 8:00pm. After several days, the start time had moved up to 8:15pm and was getting in the way of other scheduled processing.
We have changed the product to apply the interval time to the start time for the process. It had been calculating the interval based on when the previous analysis process ended.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 5.19 version of iFileAudit. The correction is available in PTF package FAPTF519. E-mail us and request the PTF package.
Not all fields are sometimes being reported on a full record delete.
When this was reported by a customer, we discovered that under certain conditions, not all field content was being reported through iFileAudit on a record delete for a registered file.
This has now been corrected so that all fields with content will be reported in detail on record deletions.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 5.18 version of iFileAudit. The correction is available in PTF package FAPTF518. E-mail us and request the PTF package.
Customer reported two problems, one with MCH1202 error codes and another with LNR7207 errors.
The MCH1202 error was reported in the export feature. The source of this problem has now been identified and corrected.
The LNR7207 error was reported in the iFileAudit purge process. Ignoring the error would result in a completed purge, but we have now corrected the problem so that these messages are no longer issued.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 5.15 version of iFileAudit. The correction is available in PTF package FAPTF516. E-mail us and request the PTF package.
I'm seeing a system error crash when I try to enter an End User profile that does not exist.
The End User Table lets you grant read access to information captured in iFileAudit for registered files. When doing this, the program would fail if a bad user profile was entered. This has now been changed to simply issue a warning messsage and stop the profile add process.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 5.13 version of iFileAudit. The correction is available in PTF package FAPTF514. E-mail us and request the PTF package.
I entered several field selection settings for a registered file, but when I call them back up, they are no longer there.
A customer reported this on a new software installation. The problem has now been identified and corrected.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 5.12 version of iFileAudit. The correction is available in PTF package FAPTF513. E-mail us and request the PTF package.
When I try to start the Automatic Analysis with a start time of 8am, it fails to start.
We found that an error is an edit routine was preventing certain start times from being used. This has now been corrected and any valid start time will now be accepted and processed correctly.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 5.11 version of iFileAudit. The correction is available in PTF package FAPTF512. E-mail us and request the PTF package.
We are seeing a CPF3130 error during file registration maintenance.
A customer was doing a major registration of many new files which needed key maintenance updates. They had multiple users in different work sessions doing the upgrade and were see the CPF3130 error on some sessions. This file conclict has now been fixed.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 5.10 version of iFileAudit. The correction is available in PTF package FAPTF511. E-mail us and request the PTF package.
I am getting an error when working with the manual file key option - F8.
Based on a customer report, we found that there was an incorrect file lock being set during manual file key maintenance. This has now been corrected.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 5.09 version of iFileAudit. The correction is available in PTF package FAPTF510. E-mail us and request the PTF package.
The Export process is failing for us with a CPF0001 error message.
The Export process was failing when run for the *ALL or GENERIC* option. It has now been fixed.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 5.08 version of iFileAudit. The correction is available in PTF package FAPTF509. E-mail us and request the PTF package.
The purge works when I run it for a single file, but it fails when I use the *ALL files option.
We discovered that a recent update to the software caused the purge for all files to fail. It has now been corrected.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 5.06 version of iFileAudit. The correction is available in PTF package FAPTF507. E-mail us and request the PTF package.
The export file information process fails when the destination file is to be stored in the QTEMP library.
We found that when a file export was run to a file in the QTEMP library and the export was in *LONG file format, the export would fail. This has now been corrected.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 5.05 version of iFileAudit. The correction is available in PTF package FAPTF506. E-mail us and request the PTF package.
The export file information process is failing sometimes.
A customer reported to us that the export file information process was failing at times. After testing, we found that when the export process was run in *LONG format mode and the process was set to append records into an existing export file, then it would fail. This has now been corrected.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 5.03 version of iFileAudit. The correction is available in PTF package FAPTF503. E-mail us and request the PTF package.
Pressing the F8 or F9 key from a new file registration screen causes the program to fail.
We found that customer could select these function keys at the wrong time during the file registration process. To avoid the program failure, we now test for this and issue well behaved error messages that will not cause the program to abnormally end.
The fix for this problem is available as a PTF. This PTF can only be installed on a Release 5.02 version of iFileAudit. The correction is available in PTF package FAPTF502. E-mail us and request the PTF package.
When I create a note on an update and the try to cancel to skip the process, a blank note is getting created.
We found that the F3/F12 function keys were not functioning correctly to exit the note authoring process. This has now been fixed. Concurrent with this, we found that in rare situations, a note could get attached to an incorrect field update report. This too has now been corrected.
The fix for these problems is available as a PTF. This PTF can only be installed on a Release 5.01 version of iFileAudit. The correction is available in PTF package FAPTF501. E-mail us and request the PTF package.
Product Information:
> Product Summary
> Complete list of features
> Online Product Demo
> Online Browser Interface Demo
> Frequently Asked Questions
Technical Support:
> Features + Enhancements
> Problem Reports
> Renew Browser Certificate
> PTF Install Instructions
Related Products:
> SafeNet/i
> iSecMap Security Enforcement
> i2Pass Two Factor Authentication
> iResetMe
