RESOLUTION
RESOLUTION 1
If a log file is only for a single IP address, check to make sure that there is no IP address specified in the Server Properties in the Usage Import Module's server manager. If an IP address is specified, remove it and try importing the log file again.
The reason for the
IP Address field under Server Properties is to differentiate between some types of Web servers. For example, Internet Information Server 3.0 (IIS) logs hits to all virtual servers in a single log file. Other types of Web servers, such as IIS 4.0, logs hits for each virtual directory to its own discrete log file.
NOTE: This only applies in single IP instances, such as the log file generated from a single instance of IIS4, or an IIS3 server that is not hosting virtual servers.
RESOLUTION 2
Check for an entry under the URL Path Extension on the
Basic tab for Site Properties; this can cause the same issue. If there is an entry under the URL Path Extension, try removing it, deleting all the logs that have been imported, and importing the data once again.
RESOLUTION 3
If the total number of hits to an unconfigured server is less than the total number of hits, it could be because the Web site is hosting both secure (SSL) and non-secure content. In this event, you should configure Server Manager like the following:
SERVER: Create a new site under the same Log Data Source, and make sure the port is set to 443, or whatever port the SSL portion of the site is using.
SITE: Create a new site under the new server created in the previous step, and make sure that you specify the HTTPS method in the Home Page URL field of the Basic tab (an example would show as https://www.mysite.com).