"No log files to analyze", Win7, IIS6 via ftp

Will

13 years ago
updated 12 years ago
Fixed

"No log files to analyze".

We had WebLog Analyzer set up and working on Windows XP. Then we upgraded the computer to Windows 7 and downloaded and installed WLA 7.7, but now when we try to connect via ftp to the log folder on IIS, we get the message "No log files to analyze".

We can't use the "local" option because the server isn't mapped locally and we don't want to go that route. WLA seems to "see" the log folder on our webserver via ftp, but does not "see" the log files. Using other ftp programs, we can get to and "see" the log files just fine.

What's going wrong?

Replies 3

Newest first
Newest first Oldest first

12 years ago

Thank you again for all the help!!!

Reply Link

Michael

The problem has been solved by changing the log path. Log path in the FTP settings is to include log file name or wildcard and may need to have slash at the beginning like /logs/*.log (if absolute path is used).

13 years ago

You should check that you enter full path including wildcard for file names, e.g. /logs/*.log. If it doesn't work, could you please send to us at support@weblogexpert.com screenshot of the Profile Properties > Log Files dialog with the FTP settings and screenshot of the log folder (e.g. opened in another FTP client). If it is possible, please send us log file of the FTP server so we'll be able to check why exactly the error appeared.