IntroductionIntroduction
  InstallingInstalling
  HandlingHandling
  Virtual serversVirtual servers
  ModulesModules
  FilesystemsFilesystems
  RXML tagsRXML tags
  GraphicsGraphics
  ProxyProxy
  Miscellaneous modulesMiscellaneous modules
  Security considerationsSecurity considerations
  ScriptingScripting
  DatabasesDatabases
  LDAPLDAP
  SiteBuilderSiteBuilder
  Access ControlAccess Control
  IntraSeekIntraSeek
  LogViewLogView
    <Installing>Installing<Installing>Installing
    <Configuration>Configuration<Configuration>Configuration
    <Event log>Event log<Event log>Event log
    <Configuration page>Configuration page<Configuration page>Configuration page
    <Troubleshooting>Troubleshooting<Troubleshooting>Troubleshooting
  FrontPageFrontPage
  UpgradingUpgrading
  Third party extensionsThird party extensions
  PortabilityPortability
  Reporting bugsReporting bugs
  AppendixAppendix
 
Troubleshooting

The first thing to do in case of a problem is to check LogView's error log files and, failing that, the main Roxen server's error log files. Both LogView and Roxen try to generate comprehensible reports on errors that occur.

Specific problems:

The installation of LogView failed
This is typically due to one of the following things:

  • The server may not have write permission in the log files directory, or may lack permission to read some of the files in the LogView distribution. The main server's error log files will contain information about which file accesses has failed.

  • LogView was instructed to store its logs and groups files in a directory other than the default logview.data, and this directory did not exist. Such directories must be created manually.