Article ID: 3641, created on Feb 8, 2008, last review on May 11, 2014

  • Applies to:
  • Helm 4
  • Helm 3


How do I set up AWStats for use with Helm?
Firstly, go here:
You can either download AWStats from the official site or you can use our own installer from the link above.

Run on server you want AWStats installed on and create the service in Helm as per this guide:
Make sure that the perl paths, and the paths to the awstats cgi-bin and perl files are set correctly.

The installer that has been put together will install AWStats into C:\\AwStats. By default this is where the AWStats service properties are configured too.

When a domain has AWStats "installed", Helm will create the config file for the domain in the c:\\awstats\\wwwroot\\cgi-bin folder and add in an update command to the UpdateStats.bat file in the same folder.

All you have to do is to set up an IIS site so that the cgi-bin can be accessed over the web. Where you want to put this is totally up to you. When setting up the IIS site or virtual directory, make sure that the cgi-bin has execute permissions since its in perl. (Under website tab at the bottom is a drop down box, change from "scripts" to scripts and executables")

Awstats needs to run with admin priviledges to access the log folders as under 2k3 the permissions are non-inherited and only allow admins to access them.

What you need to do is to create an NT user account (lets say Awstats_user) and assign it administrator rights. Add this user account to the anonymous details for the awstats site in IIS. You now won't have the permissions problem and you can update the stats using the link on the stats page.

To get AWStats to read in the log files you just have to run the UpdateStats.bat file. What is the best idea is to get that file run in a windows scheduled task at least once a day just before midnight. Again, when and how often it is run is totally up to you.
The batch file will not create stats on domains properly if you do not have the following in the Statistics service in Helm:
- The path must end in cgi-bin\\
- The data directory must end in wwwroot\\data\\
- The cgi-bin folder must end in cgi-bin\\
- The Perl folder must be correctly pointing to your perl.exe file.

For IIS6 users, select W3C Extend Log File Format, then click on Properties. Set "New Log Schedule" to Daily, and then on the advanced tab, check ALL extended logging options. If any were unchecked, you will need to delete your current log files as AWStats will not be able to read them. If you find it necessary to read existing logs, then you need to create your own log format (see AWStats documentation to find out how to do this).
Something that you must remember to do:
Ensure that the log formats in IIS include all the information except processor information (IIS5). This is better for the stats and is required for the Helm Bandwidth Monitor anyway.

It is worth changing the log formats to fit your requirements. You can
change the log file format in Helm in the Statistics service in Helm. This is located here:
Home > System Settings > Servers > Your Server > Statistics service
The following settings assume you have switched on all available log file properties:

For Window 2000 users change the log format to:

%time2 %host %logname %other %other %other %other %method %url %other %code %other %bytesd %other %other %other %other %ua %other %referer

For Window 2003 users change the log format to:

%time2 %other %other %other %method %url %other %other %logname %other %other %ua %other %referer %other %code %other %other %bytesd %other %other
Once AWStats is installed on a domain, the path to get to their stats is as follows:
Where AWStats URL is the path to the AWStats site on your webserver, and being the name of their domain.

0331e0e4efc12686c3f22fc2cdda9f03 152090ff5e9a05ea7e1cf0c248449638 110556ad4b9f1c73a3682661cd1dca89 6311ae17c1ee52b36e68aaf4ad066387

Email subscription for changes to this article
Save as PDF