 |
 |
 |
 |
|
 |
 |
Error "No entries in database"
Surfstats could not parse the record
fields from your log files to enter it in
the log files. This can be because:
1. Surfstats does not support your
log file or could not determine the log
file format.
2. The specified log file is empty or
does not exist.
3. There are no entries between the
dates specified or the active filters
filtered out all data.
In case your log file format is not supported,
please e-mail us a compressed sample of
your log file so we can determine what the
problem is.
Every line in a log file should contain a valid
date with a few exceptions. You can view
the log file with Surfstats log viewer to
confirm. Some exceptions are:
MS IIS log files usually contains about 4
lines of header information at the start of the
log file. This contains the name, version,
description, record contents, etc. of the file.
Some log files are split into various smaller
files, e.g. an access_log, an error_log, a
referer_log, etc. Only the access_log will
contain date entries.
Some log entries take up two lines per hit
and the first line contains the date entry.
If you cannot create a site profile
The site profile may already exist on
your hard disk but is not shown in the
site profiles list.
Use a file manager like Windows Explorer
and delete the site profile under the
directory \Program
Files\SurfStats\Sites\mysite. Just exchange
"mysite" with the site profile name.
If you get problems after installing
a new release.
You might have files of the previous
release on your system that clashes
with the new release.
Uninstall SurfStats completely as described
in the Installation section in the SurfStats
Log Analyzer help.
No detail (or limited detail)
available in database for this
report. Dialog box displays with
message indicating 5 possible
reasons.
The database does not contain any
information to generate the report.
This could be because active filters
exclude all information for a specific
report or your log files do not contain
the required fields for the report.
Could also be that SurfStats does not
recognize the date format (especially
in Apache log files)
Make sure that you have no filters active
that filters out the required fields. Make sure
that your server logs the required fields.
Refer to the online help how to set up
extended logging (Help- search for
extended).
Inspect the date format in the log file and
change the “Log file date format” for the
specific profile from Auto-detect to the
correct value.
I have created a schedule, but
can’t seem to find a way to run it
right now in V7.0 as I did in V6.7.
The administration and running of
schedules are separate in V7.0 and
later. Schedules can only be run by
the SurfStats Scheduler Service
when the time for the schedule
arrives.
Install and start the SurfStats Scheduler
Service in SurfStats Log Analyzer from
Schedule Tasks – Service.
Squares display instead of
Eastern Asian characters when I
select an Eastern Asian
Language.
The language is not installed on the
computer.
Depending on the operating system install
the language from Regional Options in the
Windows Control Panel.
The icons in the SurfStats Log
Analyzer application look dull.
Color depth is set too low.
Increase the color depth above 256 colors
from Display in the Windows Control Panel.
SurfStats Scheduling can’t seem
to access log files on other
computers.
Access rights.
Specify a valid account with sufficient
access rights for the SurfStats Scheduler
service to run under (not the LocalSystem
account). This is done from Windows
Control Panel – Administrative Tools –
Service – SurfStats Scheduler – Log On
tab. Also use UNC names (for instance
\\remoteserver\logs\W3SVC1\*.log) and not
mapped drive letters.