Empty results in REPORTS.NSF

03 Troubleshooting

Server
Empty results in REPORTS.NSF

If you receive an "empty" report, for example, where only the original request information is present, after running a message report in REPORTS.NSF, there may be a protection problem with the reports database. If this happens, there are several things you can check:

2. Check the signature of the agent by looking at the $UpdatedBy field in Designer. If the signer of the agent doesn't have Editor access, it won't work.

3. Ensure that the signer of the agent is allowed to run unrestricted agents on this server. You can check this in the Security section of the server's Domino Directory.

4. The signer of the agents should be the administrator for the server. If it is not, edit each agent in the Designer and save the agent. This re-signs the agent (see step 3 again.)

5. If the report was created by a scheduled agent, make sure the server has Manager access.

6. If you don't receive any reports at all for a scheduled agent, make sure it is enabled. If you enable the scheduled agent, you re-sign it, so perform step 3 above.

7. Make sure that the database is not full-text indexed.

Note: An "empty" report is not one where the Message Tracking Store (MtStore located in \DATA\MTDATA) is empty or not present. If that is the case, you receive a message in the report indicating a problem with the MtStore.

If you still are having problems getting a report to run, an SPR should be written. To expedite the SPR process, first turn on debugging for the reports agent. This is accomplished by setting the NOTES.INI variable DEBUG_REPORTS=1. The output for scheduled reports appear on the server console. The output for one-time reports appears in the client debug window. Include this output in your SPR.