Check the Installation on Windows

Checking the Installation with the Dashboard

To check that all servers have loaded correctly:

  1. Sign in to the Dashboard.

    The Username of the default administrator account is admin . The default administrator Password is also admin . We recommend you change this default password as soon as possible.
  2. Open the Servers page and verify that there’s a row for the core server, the Analytics server, and each of your installed language servers.
  3. Select a Language Server to open the corresponding page.
  4. For each language server, verify the following:
    • The Guidance Package section displays the correct version information of the installed guidance package.
    • The Writing Guides section lists all of the configured writing guides.
    • The Term Sets section lists all of the configured term sets.

Checking the Log Files for Errors or Warnings

You can diagnose issues that occur during installation by reviewing the core server and language server log files.

To check the log files for errors or warnings, follow these steps:

  1. Open the core server and language server log files.
    • Navigate to the directory where the log files are stored and open the files in an editor<INSTALL_DIR>/server/logs/coreserver.log for the core server log file and <INSTALL_DIR>/server/logs/ls-<LS_NUMBER>.log for the language server log files.
    • In the dashboard, navigate to Maintenance > Logs View Recent Entries, and select the desired log file to display.

    The log file entries have the following syntax:



    2010/08/18 12:41:25.805 | [INFO ][init] Term database initialized

Pay special attention to entries that have the severity FATAL CRITICAL , or ERROR. When displaying the log files in the dashboard, you can select to display only warnings and errors.

The server can successfully start despite critical issues or errors, but these entries can indicate that a vital component of the Acrolinx Server isn’t functioning correctly.

For more information about log files, see the article Managing the Server Logs.