Security Compliance

Troubleshoot Patch Manager error 1064

Use this article to troubleshoot "Could not start the EminentWare Data Grid Server service on Local Computer" error messages when launching the Patch Manager console. The error code is 1064, and the detailed message is: An exception occurred in the service when handling the control request.

First published date

11/15/2018 5:23 PM

Last published date

3/22/2025 2:07 AM

Overview

The article describes how to troubleshoot error code 1064. When the error exists, the following messages display when launching the Patch Manager Console:

Could not start the EminentWare Data Grid Server service on Local Computer

An exception occurred in the service when handling the control request.

Product section

Patch Manager

Cause

Multiple causes

Resolution

  1. Verify the credentials in the Patch Manager Console. Ensure that the credentials match the service account on the Patch Manager server.
  2. Verify the service account used to start the EminentWare Data Grid server. Ensure that the account is set to log on as a service.
  3. Verify that DCOM is configured for the SERVICE group.
  4. Check the Registry and other settings.
  5. Check the SQL settings.
  6. (Non-upgraded Eminentware Customers only) Check the ewlicense.lic file. Ensure that the file is not missing.

See the following sections for specific procedures.

Verifying the credentials in the Patch Manager Console

During initial setup, Patch Manager creates a local service account (ewdgs-#######) to start the EminentWare Data Grid Server service unless you specify a different account in the Installation Wizard. If you change the password or account used to start the EminentWare Data Grid Server service, there are several areas on the Patch Manager server where you must  change those settings. See Change the account or password used for the Patch Manager service for details. This account should also be present directly (not part of a group) in the Local server Administrators group.
 

Verifying the service account

  1. Ensure the service account is listed directly in the Local server Administrators security group.
  2. Open the Local Security Policy on the Patch Manager server.
  3. Expand Local Policies and select User Rights Assignment.
  4. Select Log on as a service in the center pane, click the Actions menu, and select Properties.
  5. Add the service account used to start the EminentWare Data Grid Server service to this list.
  6. Click OK.

Verify that DCOM is configured for the SERVICE group

  1. On the remote computer, launch dcomcnfg using a command prompt or the Run dialog.
  2. in the navigation pane, expand Component Services > Computer, and then select My Computer.
  3. Click the Action menu, and then select Properties.
  4. Click the Default Properties tab.
  5. Select the Enable Distributed COM on this computer option if necessary.
  6. Click the COM Security tab, and then click Edit Default under Access Permissions.
  7. Add SERVICE as an account, and then select Local Access under Permissions for SERVICE.
  8. Click OK.
  9. Back on the COM Security tab, click Edit Default under Launch and Activate Permissions.
  10. Add SERVICE as an account, and then select Local Launch and Local Activation under Permissions for SERVICE.
  11. Click OK.
  12. In the My Computer Properties window, click OK.

Check the Registry and other settings

  1. Launch Services and then select and right-click EminentWare Data Grid Service.
  2. In the Properties, go to the Log on tab and retype your login (domain\username) and password.
  3. Click Browse and select the required DataGridService account.
  4. Enter the password and click OK.
  5. Run regedit and go to HKEY_LOCAL_MACHINE\SOFTWARE\EminentWare\Data Grid Service\Roles\Application\Data.
  6. Delete MEkey and MPKey.

Check the SQL settings

  1. Launch SQL Management Studio, expand Security and Logins.
  2. Determine if the necessary ewdgs-####### (or custom) account is present in the list.
    If the account is missing, create the account. 
    1.  Right-click Logins > New Login.
    2.  In the Login window, click Search and add the account.
    3.  Scroll down to the bottom, and then select EminentWare as the default database.
    4.  In Login window, go to Server Roles and then select the public and sysadmin options.
    5.  In Login window, go to Status and ensure that the Grant and Enabled options are selected.
    6.  Save the new login.
      If the account exists, check the default database and permissions for the account per above.
  3. Go to [Instance name] > Databases > EminentWare > Security > Users.
  4. Determine if the necessary account is present in the list.
    If the account is missing, create the account. 
    1. Right click on Users > New User.
    2. In Database User window click "..." button and select account.
    3. Enter User Name.
    4. Check db_accessadmin and db_owner options in Owned Schemas and Database role membership.
    5. Save new user.
      If the account exists, check the permissions for the account.
  5. Right-click the SQL Instance name and select Properties.
    1. In the Server Properties window, go to Permissions and ensure that Connect SQL option is selected for the account. 
    2. Save the properties setting.
  6. Right-click EminentWare Database and select Properties.
  7. In Database Properties window go to Permissions and ensure that Connect option is checked for needed account.
  8. Save the properties setting.
  9. Start the EminentWare Data Grid Service.