Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

MBAM Data Store Communication Failure when you click on MBAM Hardware


View products that this article applies to.

Symptoms

Hardware Compatibility in MBAM manages the hardware inventory and checks whether hardware models are compatible with Bitlocker drive encryption.
When you select on Hardware in MBAM Console, you may receive the following error messages:

Data store request not completed

Data store communication failure





You may see following error message in SQL logs located at
C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\Error log

Logon  Error: 18456, Severity: 14, State: 11.
Logon  Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Token-based server access validation failed with an infrastructure error. 
Logon  Error: 18456, Severity: 14, State: 11.
Logon  Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Token-based server access validation failed with an infrastructure error.

↑ Back to the top


Cause

The issue occurs if 'NT AUTHORITY\NETWORK SERVICE' does not have access to MBAM Recovery and Hardware Database or Firewall is blocking UDP traffic to port 1434.

↑ Back to the top


Resolution

To resolve this issue, follow the steps mentioned below to add NT AUTHORITY\NETWORK SERVICE:
  1. Connect to MBAM server where MBAM Recovery and Hardware DB is installed.
  2. Open SQL Server Management Studio and connect to your Database Engine.
  3. Browse to Security and click on Logins.
  4. Make sure you have NT AUTHORITY\NETWORK SERVICE in the list, if not then you will have to add it.
  5. Right Click on NT AUTHORITY\NETWORK SERVICE and click Properties.
  6. In User Mapping make sure MBAM Recovery and Hardware DB is checked and it has dbo and public role membership.
  7. Restart the SQL Server Services.
  8. Now you should see the below screen.



UDP port 1434 might be required for the SQL Serve Brower Service when you are using named instances. Check that no firewall is blocking UDP traffic to port 1434.

↑ Back to the top


More Information

Read more about 'Allow hardware compatibility checking' policy setting:

Planning and Configuring Group Policy for MBAM
http://onlinehelp.microsoft.com/en-us/mdop/hh285629.aspx

↑ Back to the top


Keywords: kbtshoot, kb

↑ Back to the top

Article Info
Article ID : 2668508
Revision : 1
Created on : 1/7/2017
Published on : 2/27/2015
Exists online : False
Views : 430