Error Codes
This document contains a list of FlashStats Errors. These errors
are returned by FlashStats v1.5.
|
Error #1:
|
No form data posted.
|
Description:
No form data was provided. Data must be POSTed to FlashStats via an
HTML form. This error can occur if you attempt to access FlashStats
directly instead of via an HTML form.
Solution:
Generate FlashStats reports by filling out the FlashStats Report Request Form (the default installed location for this form is http://yourservername.com/FlashStats/).
If you are attempting to discover whether FlashStats is installed and
whether your web server correctly recognizes FlashStats as a cgi program,
check the trouble shooting guide's answer to "How can I tell if my web server is set up correctly to run FlashStats?"
|
Error #2:
|
Invalid user account name and/or password
|
Description:
You entered an invalid user account name and/or an invalid password
in the FlashStats Report Request Form.
Solution:
In the FlashStats Report Request Form verify that you have entered the
correct user account name and password. FlashStats will only run
reports if the user account name and password matches a user account
entry in its configuration file.
|
Error #3:
|
Invalid key or password
|
Description:
You have entered your key or password incorrectly
Solution:
Open your configuration file (Windows/Mac: FlashStats.INI, Unix: flashstats.conf) and check the Key= and Password= lines. You should be using the exact values provided when you purchased the software. These values are case-sensitive, so be sure to enter them exactly as provided.
|
Error #4:
|
User account is missing the 'URL' parameter
|
|
Error #5:
|
User account is missing the 'Logs' parameter
|
Description:
The user account is missing the Logs parameter. This parameter specifies the
location (full path) of old (i.e., rotated, archived) log files.
(Win example: Logs=C:\\Windows\\System\\LogFiles\\in*.log)
(Mac example: Logs=:logs:*.log)
(UNIX example: Logs=/usr/http/logs/*.log)
If it specifies a pattern which also matches the current log file, then the
AccessLogs= parameter can be omitted.
Solution:
Edit the FlashStats configuration file to include the Logs parameter
for the user account.
Back to Top
|
Error #6:
|
No start date specified
|
Description:
No start date for the report date range was specified.
Solution:
Specify a valid start date. The date range is usually specified in the FlashStats Report Request Form, but can be specified in the FlashStats configuration file instead.
|
Error #7:
|
Invalid date range or format
|
Description:
An invalid date range for the report was specified.
Solution:
Specify a valid date range. Make sure that the end date does not come before the start date. (The date range is usually specified in the FlashStats Report Request Form, but can be specified in the FlashStats configuration file instead.)
|
Error #8:
|
No end date specified
|
Description:
No end date for the report date range was specified.
Solution:
Specify a valid end date. The date range is usually specified in the FlashStats Report Request Form, but can be specified in the FlashStats configuration file instead.
|
Error #9:
|
Could not open configuration file
|
Description:
The configuration file (Windows/Mac: FlashStats.INI, Unix: flashstats.conf) could not be opened. This file is required for proper operation of FlashStats.
Solution:
Make sure that the configuration file is in the same directory as the FlashStats program file.
Also make sure that FlashStats has read access to the file.
On UNIX systems FlashStats runs as the same user/group as the
web software (often this is nobody:nogroup). Make sure that this
user has read access to the flashstats.conf file.
|
Error #10:
|
Could not open passwords file
|
Description:
The passwords file could not be opened. If the configuration file
parameter "UserPasswords" is set then the file specified in that parameter is required to validate the passwords of users that do not have a password specified in the configuration file.
Solution:
Make sure that the user account is defined properly, that the passwords
file is correctly specified (if it is used at all), and that
FlashStats has read access to the passwords file. Check the
UserPasswords= parameter in the FlashStats configuration file.
The presence of a UserPasswords= parameter and lack of a
password specified in the user account definition indicate that
the password will be looked up in the specified passwords file
(or system database if UserPasswords=system)
See Chapter 3 of the
FlashStats documentation
for more information on setting up the UserPasswords parameter.
|
Error #11:
|
No log files found
|
Description:
FlashStats did not find any log files. FlashStats looks at the user account
definition to find the location of the log files.
Solution:
Check the user account definition in the FlashStats configuration file is correct.
Look at the logs= and accesslog= parameters and make sure they
correctly point to files that exist. Double-check their values, since one small
typo could prevent FlashStats from finding the files. Macintosh users may want
to read
Tech
Note FS1444 for hints on specifying file paths on MacOS.
See the documentation for the
logs= and
accesslog= parameters.
Back to Top
