Why Are Reports Missing from the Gallery Manager? :: SAS(R) IT Resource Management 3.3: Reporting Guide

Are the Gallery Manager Filters Defined Correctly?

Log off from the Gallery Manager and log back on.
Invoke the new Gallery wizard to create a new gallery that shows at least one report that should be generated by the report job.
1. On page 2 of the wizard, select one domain category, one subcategory, one schedule frequency, and one keyword (if applicable) that matches one of the reports in your report job.
2. On page 3 of the wizard, note how many reports are found. If one or more reports are found, click Next. On step 4 of the wizard, note how many reports are found.
  
  If no reports are found, go to the previous step and increase the number of occurrences to 999 and repeat. (For information about how to change the number of occurrences, see Step 3 of the “Create a Gallery” topic in SAS IT Resource Management: Gallery Manager User's Guide.)
If you are still not able to find any reports that should be generated from your report job, perform the following steps:
1. Try to determine whether the Gallery Manager can find any reports or whether the problem is limited to a subset of reports.
2. For more troubleshooting suggestions, see Are the Reports Stored on the SAS Content Server?.

Are the Reports Stored on the SAS Content Server?

Use the SAS Content Server Admin Console to traverse the SAS Content Server folder structure to search for at least one report that should be generated by the report job. (The SAS Content Server Admin Console is located at http://<YourMidTierName>:<Port Number>/SASContentServer/dircontents.jsp?path=/sasdav/ITRM. Log on using any user ID that has Read access to the SAS Content Server.)
Traverse the folder structure until you reach the folder that contains the actual report.

SCS Admin Console Contents

Note: The SAS Content Server folder names in the preceding display that are under the sasdav/ITRM folder correspond to the name of the EG project, the EG process flow, and the report definition that was used to define the report.
If the report is not in the SAS Content Server, check the report job log to make sure that the reports generated without errors. Investigate and eliminate the cause of the errors and rerun the report job. For more troubleshooting suggestions, see Why Report Jobs Are Not Generating Reports.You might have to rerun the report job with debugging turned on. Save the report job log and contact Technical Support.
- For more information about how to turn debugging on for the Gallery Manager, see How to Debug a Middle-tier Connection Problem in a Report Job.
If the report is in the SAS Content Server, perform the following steps:
1. Restart the Gallery Manager to refresh the cache. For information about how to do this, see How to Refresh the Cache for Gallery Manager Reports.
2. Check whether there are errors in the Gallery Manager log. (The log is located at <YourSASConfigFolder>\Lev1\web\Logs\GalleryManager3.3.) If there are errors in the Gallery Manager log, save a copy of the log and contact Technical Support. For information about how to do so, see Technical Support.

Does the Cache Need to Be Refreshed?

The Gallery Manager maintains an internal index, or cache, of the reports that are stored on the SAS Content Server. The reports that are associated with the Gallery Manager are only those that are generated by SAS IT Resource Management report jobs. When SAS IT Resource Management report jobs run successfully, the cache is updated correctly. However, in some cases, such as network connection failures, you might not be able to see new reports. Similarly, you might see a 404 error message that refers to reports that were deleted because the cache was not updated correctly.

Example of an HTTP Status of 404

To force an update of the cache, see How to Refresh the Cache for Gallery Manager Reports.

Did the Report Jobs Run Correctly?

Check the report job log to make sure that the reports were generated without errors. Investigate and eliminate the cause of the errors and rerun the report job. For more troubleshooting suggestions, see Why Report Jobs Are Not Generating Reports.