Did not detect a successful analysis from the inspection of the statuslogs


Webtrends Analytics 9.x
Webtrends Analytics 8.x

Webtrends Legacy


The profile’s status messages display the following:

Did not detect a successful analysis from the inspection of the statuslogs


The status messages indicate the reason for a failed analysis, sometimes general, and at other times specific. These may often result from problems with the the data source configuration, availability (or accessibility) of log files in the data source, problems with the contents of the log files in the data source (errors or time stamps which may prevent analysis from occurring), or problems with Webtrends components (for example, using a mismatched version of the geotrends.dat file).


For detailed information regarding why this message displays, review the profile’s statuslog:
1. Edit the profile in the user interface and under the “General” tab in the “Profile file name” field the profile’s globally unique identifier or “guid” displays. Make note of the guid and proceed to the next step.

2. On the Webtrends server, navigate to the location shown below:


3. Statuslogs are files of the same name as the matching profile guid, without an extension. Open the profile’s statuslog with a text editor. (Ensure the profile is not undergoing analysis at the time or the statuslog will be locked and prevent debugging information from being added to it.)

4. Search the statuslog for messages similar to the following examples:

  • Geotrends not installed – Edit the profile and go to the Internet Resolution tab and uncheck geotrends, or install geotrends.
  • Could not parse log file – (bad log file, check the log for validity. Is Process Accounting enabled? Is the file 0 bytes? Is there no header? etc.)
  • Could not connect to FTP – Verify ftp settings and try again.
  • Invalid log file format – The log is not supported by Webtrends.
  • The log file has a header with field descriptions that do not match the data contained in the records, or there are more fields than the log files contain.
  • Using ISA log files.
  • Multiple physical web servers and log files missing on one or more of the servers for a given day.
  • No log files found for data source – Verify that the data source is set up properly. Note: If data source is on the network do not use mapped drives.