in

logresolvemerge drops all records on awstats

The title pretty much says it. I've read every single piece of documentation about this and no matter what I do, all my records are either dropped or corrupted. When I run each individual log however, the records are all imported into awstats without issue.
When I look at the reason for all these corrupted or dropped records, this is what I get.....

Corrupted error message - record format does not math LogFormat parameter
Dropped error message - method/protocol '*' not qualified when LogType=W

Anybody know what I'm doing wrong? Please see a sample portion of my config file below...

# AWSTATS CONFIGURE FILE 6.5
#-----------------------------------------------------------------------------
# Copy this file into awstats.www.mydomain.conf and edit this new config file
# to setup AWStats (See documentation in docs/ directory).
# The config file must be in /etc/awstats, /usr/local/etc/awstats or /etc (for
# Unix/Linux) or same directory than awstats.pl (Windows, Mac, Unix/Linux...)
# To include an environment variable in any parameter (AWStats will replace
# it with its value when reading it), follow the example:
# Parameter="__ENVNAME__"
# Note that environment variable AWSTATS_CURRENT_CONFIG is always defined with
# the config value in an AWStats running session and can be used like others.
#-----------------------------------------------------------------------------
# $Revision: 1.324 $ - $Author: eldy $ - $Date: 2005/10/30 15:56:38 $



#-----------------------------------------------------------------------------
# MAIN SETUP SECTION (Required to make AWStats work)
#-----------------------------------------------------------------------------

# "LogFile" contains the web, ftp or mail server log file to analyze.
# Possible values: A full path, or a relative path from awstats.pl directory.
# Example: "/var/log/apache/access.log"
# Example: "../logs/mycombinedlog.log"
# You can also use tags in this filename if you need a dynamic file name
# depending on date or time (Replacement is made by AWStats at the beginning
# of its execution). This is available tags :
#   %YYYY-n  is replaced with 4 digits year we were n hours ago
#   %YY-n    is replaced with 2 digits year we were n hours ago
#   %MM-n    is replaced with 2 digits month we were n hours ago
#   %MO-n    is replaced with 3 letters month we were n hours ago
#   %DD-n    is replaced with day we were n hours ago
#   %HH-n    is replaced with hour we were n hours ago
#   %NS-n    is replaced with number of seconds at 00:00 since 1970
#   %WM-n    is replaced with the week number in month (1-5)
#   %Wm-n    is replaced with the week number in month (0-4)
#   %WY-n    is replaced with the week number in year (01-52)
#   %Wy-n    is replaced with the week number in year (00-51)
#   %DW-n    is replaced with the day number in week (1-7, 1=sunday)
#                              use n=24 if you need (1-7, 1=monday)
#   %Dw-n    is replaced with the day number in week (0-6, 0=sunday)
#                              use n=24 if you need (0-6, 0=monday)
#   Use 0 for n if you need current year, month, day, hour...
# Example: "/var/log/access_log.%YYYY-0%MM-0%DD-0.log"
# Example: "C:/WINNT/system32/LogFiles/W3SVC1/ex%YY-24%MM-24%DD-24.log"
# You can also use a pipe if log file come from a pipe :
# Example: "gzip -d g.gz |"
# If there is several log files from load balancing servers :
# Example: "/pathtotools/logresolvemerge.pl *.log |"
#
#LogFile="C:\Web Server Logs\indonesia\ex%YY%MM%DD.log"
#LogFile="c:/wlogs/indonesia/logresolvemerge.pl c:/wlogs/indonesia/*.log |"
#LogFile="C:/wLogs/indonesia/ex%YY%MM%DD-30.log
LogFile="c:/inetpub/wwwroot/awstats/indonesia/cgi-bin/logresolvemerge.pl c:/wlogs/indonesia/*.log |"


# Enter the log file type you want to analyze.
# Possible values:
#  W - For a web log file
#  S - For a streaming log file
#  M - For a mail log file
#  F - For a ftp log file
# Example: W
# Default: W
#
LogType=W


# Enter here your log format (Must match your web server config. See setup
# instructions in documentation to know how to configure your web server to
# have the required log format).
# Possible values: 1,2,3,4 or "your_own_personalized_log_format"
# 1 - Apache or Lotus Notes/Domino native combined log format (NCSA combined/XLF/ELF log format)
# 2 - IIS or ISA format (IIS W3C log format). See FAQ-COM115 For ISA.
# 3 - Webstar native log format.
# 4 - Apache or Squid native common log format (NCSA common/CLF log format)
#     With LogFormat=4, some features (browsers, os, keywords...) can't work.
# "your_own_personalized_log_format" = If your log is ftp, mail or other format,
#     you must use following keys to define the log format string (See FAQ for
#     ftp, mail or exotic web log format examples):
#   %host             Client hostname or IP address (or Sender host for mail log)
#   %host_r           Receiver hostname or IP address (for mail log)
#   %lognamequot      Authenticated login/user with format: "john"
#   %logname          Authenticated login/user with format: john
#   %time1            Date and time with format: [dd/mon/yyyy:hh:mm:ss +0000] or [dd/mon/yyyy:hh:mm:ss]
#   %time2            Date and time with format: yyyy-mm-dd hh:mm:ss
#   %time3            Date and time with format: Mon dd hh:mm:ss or Mon dd hh:mm:ss yyyy
#   %time4            Date and time with unix timestamp format: dddddddddd
#   %methodurl        Method and URL with format: "GET /index.html HTTP/x.x"
#   %methodurlnoprot  Method and URL with format: "GET /index.html"
#   %method           Method with format: GET
#   %url              URL only with format: /index.html
#   %query            Query string (used by URLWithQuery option)
#   %code             Return code status (with format for web log: 999)
#   %bytesd           Size of document in bytes
#   %refererquot      Referer page with format: "http://from.com/from.htm"
#   %referer          Referer page with format: http://from.com/from.htm
#   %uabracket        User agent with format: [Mozilla/4.0 (compatible, ...)]
#   %uaquot           User agent with format: "Mozilla/4.0 (compatible, ...)"
#   %ua               User agent with format: Mozilla/4.0_(compatible...)
#   %gzipin           mod_gzip compression input bytes: In:XXX
#   %gzipout          mod_gzip compression output bytes & ratio: Out:YYY:ZZpct.
#   %gzipratio        mod_gzip compression ratio: ZZpct.
#   %deflateratio     mod_deflate compression ratio with format: (ZZ)
#   %email            EMail sender (for mail log)
#   %email_r          EMail receiver (for mail log)
#   %virtualname      Web sever virtual hostname. Use this tag when same log
#                     contains data of several virtual web servers. AWStats
#                     will discard records not in SiteDomain nor HostAliases
#   %cluster          If log file is provided from several computers (merged by
#                     logresolvemerge.pl), use this to define cluster id field.
#   %extraX           Another field that you plan to use for building a
#                     personalized report with ExtraSection feature (See later).
#   If your log format has some fields not included in this list, use:
#   %other            Means another not used field
#   %otherquot        Means another not used double quoted field
#
# Examples for Apache combined logs (following two examples are equivalent):
# LogFormat = 1
# LogFormat = "%host %other %logname %time1 %methodurl %code %bytesd %refererquot %uaquot"
#
# Example for IIS:
# LogFormat = 2
#
LogFormat=2


# If your log field's separator is not a space, you can change this parameter.
# This parameter is not used if LogFormat is a predefined value (1,2,3,4)
# Backslash can be used as escape character.
# Example: " "
# Example: "\t"
# Example: "\|"
# Example: ","
# Default: " "
#
LogSeparator=" "

 I'm using IIS in a complete microsoft environment.

Solution: logresolvemerge drops all records on awstats

Hi,

If you are using Helm then use the following setting :


1.      Download the Latest version of Awstats from following url:
(http://awstats.sourceforge.net/)

2.      Install the Awstats using Downloaded Installer. (Recommended path is c:\Awstats).

3.      Create a Directory with the name of Data at c:\Awstats.

4.      Make the configuration of log format in IIS (Windows 2003) IIS>web site>properties>website tab>Active Log format>properties>Advanced Tab.

5.      Create a virtual directory in IIS through which you can view the Awstats through Helm CP or directly by url like (http://IPAddress/awstats/cgi-bin/awstats.pl?config=domainname.com), we preferred that create virtual directory under Helm CP website in IIS.

6.      Add update. bat file in the schedule task, update. bat will be available in ‘C:\Awstats\wwwroot\cgi-bin’, it will be daily process the log files and update the stats.

7.      Add the Awstats in Helm CP as a service through Helm CP>System Settings>Server>server name, and make sure to configure following settings:

Log file format: %time2 %other %other %other %method %url %other %other %logname %host %other %ua %other %referer %other %code %other %other %bytesd %other %other

Update via browser: No.

Enable Full DNS Lookup:  Yes (It will to view the countrywide detail in Awstats).

Connection Info: Url through which you can access the Awstats for e.g. (http://IP/awstats/cgi-bin/awstats.pl?config =[domainname]" class= "linkColour" > Click Here to View Stats )

8.      Add the Resources for Awstats through Helm CP>System Settings>Resource Setup.

9.      Enable the resources for Awstats in Reseller Hosting Plan, Hosting plan in reseller and package of a user under web site settings.

10.      Check with Enabling Awstats in any domain and then click on Click Here to view Stats, You can get a error here that you are not authorize to view this page then login into the server right click on the virtual directory of Awstats> Click on Directory>Enter administration username+password, this problem will be resolved.

11.      Please check the conf file in C:\Awstats\wwwroot\cgi-bin’ after enabling the Awstats from Helm CP to make sure that Awstats has been enable, file name will be ‘awstats.domainname.conf’.

12.      Make sure check the Awstats after one or two days to make sure that your stats are updating or not because if any problem in installation then you can’t recover the old logs. If the Awstats is working fine also the c:\Awstats\data directory, it should contain a data file for each domain on which Awstats has been enabled.

13.      If you want to update the logs manually then please use following command:

c:\awstats\wwwroot\cgi-bin> Awstats.pl config=domain name -update

Some useful Links:

http://forums.webhostautomation.com/viewtopic.php?t=13388&postdays=0&postorder=asc&highlight=awstats+icon&start=0

http://forums.webhostautomation.com/viewtopic.php?t=1792&highlight=awstats

http://www.allscoop.com/tools/awstats-log-format/index.php