Table of Contents

Installing AppMonitor

Requirements

Installation Process

  1. If you haven't already installed SQL Server 2008 R2 Express, follow this guide before continuing. CLICK HERE
  2. Once you've obtained the AppMonitor installer, double-click setup.exe.
  3. If .NET 4.0 needs to be installed ensure you have internet connection, accept the license agreement, and continue with the installation. Once .NET is installed, Setup will ask you to restart your computer. Click Restart Now.
  4. After the system has rebooted, the AppMonitor Setup Wizard may begin automatically. If not, click setup.exe once more.
  5. On the Welcome screen, click Next.
  6. On the “Database Settings” screen, fill in the following fields as needed:
    • Database Host: this refers to the machine hosting the database. The default is “localhost” and refers to this machine. If you installed SQL Server on this machine, leave it as “localhost.”
    • Catalog: This will be the name of the database.
    • Username: A username for database administration. This user was created during the SQL Server 2008 R2 installation.
    • Password: The user's password.
  7. For the “Username” type in sa and provide the password you wrote down during the SQL Server installation. When you're finish, click Next.
  8. In the “Database Settings (continued)” screen, choose an action to take should a database with that name already exist and click Next.
  9. In The “Select Installation Screen, choose a folder to install the program files into. The default should be fine, but you may also click Browse… to select a different location. Clickin Disk Cost… will allow you to see how much hard drive space you have.
  10. Choose who you would like to install AppMonitor for and click Next. On Windows 7 machines, you will be prompted to enter a username and password. The username format must be: <COMPUTER>\<USERNAME> or <DOMAIN>\<USERNAME>. Example: MYMACHINE\Seraph
  11. On the next page, click Next to confirm the installation.
  12. If an error is encountered (error 1001 or 40) this is likely due to a mis-configured SQL Server or firewall. Consult THIS GUIDE or seek support.