Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 928437 - Last Review: January 23, 2007 - Revision: 1.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"
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 1Type: 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)
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)
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:
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.
To troubleshoot this problem, follow these steps:
- 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:
- In Control Panel, use Add or Remove Programs to remove the DPM File Agent program.
- Restart the affected server.
- Use the DPM Administrator Console to reinstall the DPM File Agent program on the affected server.
- 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.
- Verify that the affected server can access the DPM server.
- If a firewall is configured on the DPM server, verify that the firewall does not block requests from the affected server.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
APPLIES TO
- Microsoft System Center Data Protection Manager 2006
| kbtshoot kbbug kbpending kberrmsg kbprb KB928437 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate