infoAdvantage Corrupted File Errors

Recently, users have been experiencing issues when trying to run reports stored in the Shared Documents folder in infoAdvantage.  Due to some technical issues, several infoAdvantage Webi and Business Objects Thick Client reports that had been published to either the Statewide Reports folders or any departmental folders were corrupted. 

If a report is corrupted the following errors will be generated when attempting to run the report in infoAdvantage:

Business Objects Thick Client corrupted report error

InfoAdvantage Webi corrupted report error

As well, for Thick Client users trying to Retrieve reports from Corporate Documents (Shared Documents), if a report is corrupted the following error messages will be generated:

At this time, the only way to resolve the problem is to republish a saved copy of the corrupted report to the Shared Documents folder.  SAS is currently looking into other options such as restoring reports from backups.  However, in the meantime, it is important that users first save all Webi reports to their Personal Documents-purged of data prior to saving (publishing) to any Shared Documents folders.  Thick Client users should be sure to save any Business Objects reports to their local machine or a shared network folder prior to publishing to any Shared Documents folders.  Unfortunately, several users have lost reports because a backup of the report was not saved in their Personal Documents folder. 

The technical issues that caused some reports to be corrupted have been resolved; however, the possibility exists for users to continue finding corrupted reports over time.  If you receive any of the above error messages please follow the steps listed below:

a.) If the report was created by a report developer in your department, contact that report developer
     and ask them to republish their report.
b.) If the report was created by you, republish a good copy of the report.
c.) If the report is a Statewide Report, send an e-mail to the Customer Resource Center (CRC) @
     Finance.CRCGroup@ky.gov stating the error message received, the name of the report, and
     the location of the report.

NOTE:  It is a best practice to always save Webi reports to Personal Documents prior to saving to Shared Documents.  Users should always follow this procedure in case restoring individual reports from a backup is not an option.  Thick Client users should save backup copies of all reports to a location where nightly backups are performed by their department.