The Analyzer isn't processing the hits fast enough.

If your site is particularly busy, the Analyzer may not be able to keep up with the number of hits using the default settings. There are several ways to get the Log Analyzer to process more hits.
First, you should consider filtering any unimportant information from your log. Usually, it is not important to know what images were downloaded to the browser. Filtering images from the DomLog.nsf can cut the number of hits the Analyzer has to process by half or more. This leaves just the important information, such as which databases, views, forms, and documents were hit. It is best to filter Image hits by using the settings in the Server Document of the master NAB.
Second, check the verbosity settings in the Global Configuration Document. If these have been changed from low to medium or high, it can slow down the Analyzer significantly. Keep these set to low unless you are encountering problems.
Third, you may wish to run the agent more often. The more often it runs, the more hits it can process. By default, the Log Analysis agent runs hourly. You could change this to run the agent every half hour.
Fourth, you could increase the length of time that agents are allowed to run on the server. This setting is found in the Agent Manager section of the server document. The default daytime time limit for agents is 10 minutes. You could increase this limit as necessary. Be careful not to increase this beyond 30 minutes if you have agents set to run every half hour.
Fifth, you could run the Log Analyzer on a more powerful or less utilized server. If there is a lot of activity on the server that the Log Analyzer is running on, it can effect performance both of the Log Analyzer and the server itself. Moving the Log Analyzer to a different server gives more power and resources for the Log Analyzer to use, speeding up the processing of hits. See the help documentation for specific instructions on how to do this.