Microsoft KB Archive Search

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.

  1. Home
  2. Error message when you run a consistency check on a server volume that is configured for protection by System Center Data Protection Manager 2006: "Internal error code: 0x8099090E"

Error message when you run a consistency check on a server volume that is configured for protection by System Center Data Protection Manager 2006: "Internal error code: 0x8099090E"

Symptoms

When you run a consistency check on a server volume that is configured for protection by Microsoft System Center Data Protection Manager 2006, you receive one of the following error messages:

Error message 1
Type: Consistency check

Status: Failed

Description: DPM failed to communicate with the DPM File Agent on protected_server_name because the agent is not responding. (ID 43 Details: Internal error code: 0x8099090E)
Error message 2
Type: Consistency check

Status: Failed

Description: DPM failed to communicate with the DPM File Agent on localhost because the agent is not responding. (ID 43 Details: Internal error code: 0x8099090E)
Note Sometimes the Data Protection Manager (DPM) engine cannot communicate with the replica agent that is running on the affected server. In these cases, the DPM engine uses the word "localhost" in the error message description instead of using the name of the affected server. Error code 0x8099090E corresponds to the following error:
Response Timeout

↑ Back to the top

Cause

This problem may occur if a response from the DPM volume filter is lost. The DPM File Agent sends a message to the DPM volume filter. Then, the DPM File Agent waits for a response. If the response from the DPM volume filter is lost, the DPM File Agent may enter an infinite waiting state.

Note Network problems may also cause the DPM File Agent to generate the same error code.

↑ Back to the top

Resolution

To troubleshoot this problem, follow these steps:
  1. Restart the DPM File Agent service on the affected server. If you cannot start the DPM File Agent service, reinstall the DPM File Agent. To do this, follow these steps:
    1. In Control Panel, use Add or Remove Programs to remove the DPM File Agent program.
    2. Restart the affected server.
    3. Use the DPM Administrator Console to reinstall the DPM File Agent program on the affected server.
  2. Examine recent Application log entries on the affected server to help determine the reason that the DPM File Agent stopped responding. To do this, search for entries that have a source value of MSDPMFSAGENTCA.
  3. Verify that the affected server can access the DPM server.
  4. If a firewall is configured on the DPM server, verify that the firewall does not block requests from the affected server.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

Keywords: kbtshoot, kbbug, kbpending, kberrmsg, kbentirenet, kbprb, kb

↑ Back to the top

Article Info
Article ID : 928437
Revision : 2
Created on : 4/12/2018
Published on : 4/12/2018
Exists online : False
Views : 87