Cannot Control WebWatchBot Service or Issues Starting WebWatchBot Client

From WebWatchBotWiki
Jump to: navigation, search
 Share 

Summary

NOTE: As of WebWatchBot 8.0.2 a fix has been introduced to launch WebWatchBot Manager with elevated privilege. Users may encounter the User Account Control (UAC) prompt when launching WebWatchBot Manager - this is by design - to ensure the currently logged in user has elevated privilege to access the registry, file system, and database.

NOTE: These instructions apply to WebWatchBot version 8.0.1 and older.

WebWatchBot is fully compatible with some versions of Windows. Due to the tightened security that is inherent to some installations of Windows, it may be necessary to make some changes to ensure WebWatchBot works properly.

Problem/Cause

  • Applies to Windows Server 2008, 2012, 2016 (R1 or R2), Windows (Client) 8.0, 8.1
  • After installing WebWatchBot, the WebWatchBot Manager is unable to connect to the database or make changes. Error messages may include that settings cannot be read (registry) or the database cannot be updated.
  • The cause is tight security settings and/or UAC.
  • Even if logged in as an Administrator, certain system settings, e.g. registry, controlling services, require elevated permission to access.
  • UAC affects all users, even administrators: MSDN Blog post explains: http://blogs.msdn.com/b/patricka/archive/2010/05/13/if-i-m-an-administrator-why-do-i-get-access-denied.aspx

Resolution/Workaround

There are several options to resolving this problem, in order of effectiveness:

  1. Ensure that WebWatchBot Manager is executed with an elevated Administrator account.
    1. Locate the WebWatchBot Manager shortcut in the Windows Start Menu.
    2. Right-click on the WebWatchBot Manager shortcut, select "Send To", and then "Desktop (Create shortcut)
    3. Locate and right-click on the newly created shortcut on the Desktop, and then select properties.
    4. On the "Shortcut" tab, click the button "Advanced"
    5. Check the box for "Run as administrator"
    6. Click the OK button until both windows are closed.
  2. Install WebWatchBot with a local Administrator account and use the same account for the WebWatchBot service - do not use an Active Directory or Domain Administrator account, which has been known to cause problems with permission and access. In our tests and from feedback received, domain/AD accounts can create issues with permissions in how it relates to WebWatchBot. If necessary, create a new user account that is used for both installation and the use of the WebWatchBot service (WWBServer).
  3. Disable UAC. This has been found to be the primary cause of many of the security related problems between Windows Server 2008 and WebWatchBot (possibly other versions of Windows). We recommend disabling UAC as a last resort.