The Global Configuration document has not been edited yet.
In this case, all you need to do is select Actions - Edit Global Configuration from the menu and make sure that all the settings in the Global Configuration document are the way you want them. Most importantly, check that the path to the Domino Log is correct.
The path to the DomLog.nsf is incorrect or the DomLog.nsf is not on the server.
If this error occurs, you either have to edit the Global Configuration document and correct the path to the DomLog.nsf, or there is no DomLog.nsf on the server. If this is the case, you must either replicate the DomLog.nsf to the server from your web server, or create a new DomLog.nsf by enabling logging to the DomLog.nsf. This is done in the HTTP Server section of the Server Document.
The views from the AddDesign.nsf have not been copied to the DomLog.nsf
Provided with the demo is a database called AddDesign.nsf. There are two views in this database that must be copied to the DomLog.nsf. Simply cut and paste the views from the design of one database to the other. In addition there are two agents in this database that should be copied into the DomLog.nsf database.

If the error message you get doesn't say "Analyzer Terminating", then the error is probably more serious than a configuration problem. In this case, check the fix list for the Analyzer to see if the problem you are encountering has already been fixed. If not, collect as much information about the error as you can, such as the error messages themselves, the hits that were being processed at the time of the error, etc. If you set the Message Verbosity to High in the Global Configuration document, you will get more detailed information on where the problem occurred. We recommend that you do this and send us the resulting information so that we can use it to determine the cause of your problem.

Send any technical questions to: Matt_Fox@wfs.com

Some documents are titled "Unidentified"

Back to top

If a document is titled "Unidentified" in the view, it means that there is no Identifier document defined for the form that the document was created with. Open the hit that is unidentified and note the full database path. Also, in the Comments field near the bottom of the document, there should be a message stating the name of the form that does not have an identifier. Using the database path and form name, find the form in question and open it. Choose a field from this form that all documents that use the form will have, preferably one that uniquely identifies each document such as a title or subject. Using all this information, go to the Identifiers view in the Log Analyzer database and create an Identifier. Fill in the database path, the form name, and the name of the field you chose. Do this for every combination of database and form on your site.

Reprocess the Unidentified hits
Select all the hits in the views of hits and delete them. Then, go into the DomLog.nsf Old Hits view and select all the documents in the view. Next, run the Set to Unprocessed agent that you should have copied from the AddDesign.nsf database that came with the demo. This will move all the hits from the Old Hits view to the New Hits view. The next time the agent runs, the "Unidentified" hits should be titled with the contents of the field you specified in the Identifier documents. If not, double check the information in the Identifier documents.

Some documents are titled "Not Found"

Back to top

If a hit is titled "Not Found", it means that the object of the hit was probably deleted or somehow renamed between the time it was hit and the time the Analyzer ran. At the time the object was hit the hit was successful, but when the Analyzer tried to find the object later it was unable to find it. Unfortunately, there is no way to fix this because the information needed is no longer available.

The views contain a lot of errors.

Back to top

There are two kinds of errors that may appear in the Log Analyzer. The first kind are HTML errors. These errors occur when users request pages that aren't there, mis-typed URLs, etc. These errors will have two red Xs beside them in the views. These may be caused by broken links on your site and should be investigated. They may also just be the user's fault and can be ignored.
The second type of error that can occur is errors in analysis. These occur when the Log Analyzer cannot open the database or view that was hit, or some other situation that prevents the Analyzer from properly identifying the hit. These types of errors have one red X beside them in the views. They usually contain an explanation of what is wrong in the Comments field near the bottom of the hit document. If you are getting these types of errors, check the Comments field for more information on what to do about the error.

The hits in the DomLog.nsf are processed, but no hits are displayed in the Analyzer

Back to top

If the hits in the DomLog.nsf New Hits view are being moved to the Old Hits view, but little or nothing is appearing in the view in the Analyzer, your problem is most likely caused by improperly set filters. Try disabling all the filters, setting them to Ignore nothing, then reset the Old Hits to unprocessed in the DomLog.nsf and run the Log Analysis agent again. If you get hits in the Analyzer database, then your filters were filtering out the documents that you really wanted to see. Try applying the filters again, paying careful attention to the wording of the filter. For instance, setting a filter to Include Only and leaving the next part blank will essentially include nothing, leaving you with no hits in the Analyzer. Also, double check that the Include \ Ignore is the right way around for what you want to do. You may be ignoring what you really want to include. If you are using more than one type of filtering, try one at a time to make sure that each filter filters the information correctly. Once you are sure that each filter works properly, then combine them.

The views are cluttered with image hits

Back to top

If your site uses a lot of images, the views in the Log Analyzer can become cluttered with hits on these images. Usually, it is not necessary to keep a record of every image the user downloaded. Removing these hits from the views can make the log much clearer and easier to read. If you wish to remove image hits from the views, there are two ways to do it.
One, you can use the MIME filter in the server document of the web server. This will prevent any hits of a particular type (such as images) from being logged to the DomLog.nsf. Not only can this make the views easier to read, but it will also speed up the Analysis of the log because there will be fewer hits to process. To enable the MIME filter on the server, open the HTTP Server section of the server document in the Name and Address book and find the "Exclude from logging" settings. One of these settings should be MIME types. To filter the most common types of images, enter images/gif, images/jpeg, and images/bmp in this field. This tells the web server to ignore .gif, .jpg and .bmp images when logging hits on the site. You will have to restart the HTTP server task for the settings to take effect. This can be done by typing "tell http quit" on the web server console, then waiting for the HTTP task to end, then typing "load http" on the console.
The second way of filtering images from the Log Analyzer is to enable MIME filtering in the Global Configuration document in the Log Analyzer. This is done by editing the Global Configuration document and setting the MIME filtering to Ignore Images.

When the Analyzer comes across a hit of any image MIME type, it will skip over it. This method is simpler and doesn't require access to the server document or the server console, but it may be a little slower because there are more hits to process, even if it is just skipping many of them. If speed is an issue and access rights are not, we recommend that you use the first method.

The views don't show me what I want to see.

Back to top

The Using This Database document in the Log Analyzer gives a brief description of the information displayed in each view provided with the Log Analyzer. If you have looked at each view and have not found one that displays the hits in the way that you want to see them, you have the rights to create your own views. By default, users will have Manager access to the Log Analyzer database. This will allow you to create your own custom public views. You may wish to simply create a private view instead. If you are unfamiliar with how to go about creating a view, consult your Notes administrator, or contact us.

The Analyzer isn't processing the hits fast enough.

Back to top

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.
Second, 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.
Third, 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.
Fourth, 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 documentation for specific instructions on how to do this.

Log Analyzer gets terminated by the Agent manager

Back to top

When you first run the Domino Log Analyzer against your DomLog.nsf there may be to many hits in DomLog.nsf to be processed within the time allowed for the agent to run (see the settings in your server document). You may want to increase these time to allow the agent to run longer. However, if the log is very large even this may not be enough to let the agent run to completion.

If your DomLog.nsf is large we would suggest the following:

1. Stop the HTTP task and rename the DomLog.nsf to DomLogOld.nsf (or something similar).
2. Create a new DomLog.nsf from the template and copy the two views and agents from the Additional Design database into the new DomLog.nsf
3. Re-start the HTTP task and logging will start into the new DomLog.nsf
4. Periodically "Cut and Paste" groups of documents from the DomLogOld.nsf into the new DomLog.nsf. You should experiment a bit with how many documents to cut at a time to insure that the agent can run through to completion in the time allowed.

Another option would be to:

1. Select all of the documents in the DomLog.nsf
2. Run the agent "Set To Processed"
3. Periodically select groups of documents and run the agent "Set To UnProcessed". You should experiment a bit with how many documents to select at a time to insure that the agent can run through to completion in the time allowed.

This memory allocation situation is beyond our control, so we suggest some preventative measures be taken.