Troubleshooting File Agent Installation Issues

Article
02/14/2008

Published : September 27, 2005

Table 6.2 provides troubleshooting guidance that supplements the specific error messages that you may encounter during file agent installation.

Table 6.2 Agent Installation Issues

Error message	Possible cause	To troubleshoot this error
300: The agent operation failed because it could not communicate with the specified server.	Firewall configuration on the file server Remote Procedure Call (RPC) is unavailable	See: The “Managing Servers” chapter in this guide for firewall configuration requirements. Microsoft Knowledge Base article 224370, “Troubleshooting RPC Server is Unavailable in Windows” (https://go.microsoft.com/fwlink/?LinkId=45817).
303: Agent operation with specified server failed.	Another installation is running on the specified server. The boot volume on the file server is formatted as file allocation table (FAT).	Wait for the installation to complete and then retry the operation. Convert the boot volume to NT file system (NTFS) if you have sufficient space. For more information on using the Convert command for converting FAT volumes to NTFS, see Microsoft TechNet article “Convert” (https://go.microsoft.com/fwlink/?LinkId=50882). You should also review article 156560 in the Microsoft Knowledge Base, “Free Space Required to Convert FAT to NTFS,” (https://go.microsoft.com/fwlink/?LinkId=50883). If neither of these actions resolves the problem, restart the specified server and then retry the operation.
306: Agent installation failed because the specified server already has a different version of the DPM File Agent installed.	This problem is caused when the File Agent has already been installed on a file server but the DPM database does not have a record of the File Agent being installed.	Uninstall the File Agent from the file server locally. On the DPM server, in DPM Administrator Console, in the Management task area, on the Agents tab, select the file server and then, in the Actions section, click Refresh information. The agent status will change to Error. In the Details section, click Remove the record of the server from this DPM computer. Reinstall the file agent on the file server. For instructions, see “Managing agents” (https://go.microsoft.com/fwlink/?linkid=51976) in DPM Help.
308: The agent operation failed because of a communication error with the DPM File Agent service on the specified server.	Firewall configuration on the file server Internet Protocol Security (IPSec) RPC is unavailable	See the “Managing Servers” chapter in this guide for firewall configuration requirements. IPsec may be configured to block particular IP traffic, such as on a particular port or to particular addresses. For assistance in troubleshooting IPsec, see IPsec Troubleshooting (https://go.microsoft.com/fwlink/?LinkId=50885). Microsoft Knowledge Base article 224370, “Troubleshooting RPC Server is Unavailable in Windows” (https://go.microsoft.com/fwlink/?linkid=45817).
316: The agent operation failed because the DPM File Agent service on the specified server did not respond.	Firewall configuration on the DPM server	See the “Managing Servers” chapter in this guide for firewall configuration requirements.
319: The agent operation failed because of a communication error with the DPM Agent Coordinator service on the specified server.	Firewall configuration on the file server	See the “Managing Servers” chapter in this guide for firewall configuration requirements.
324: The agent operation failed because the DPM Agent Coordinator service on the specified server did not respond.	Firewall configuration on the DPM server	See the “Managing Servers” chapter in this guide for firewall configuration requirements.
329: Agent operation failed because an incompatible version of Quota Advisor is installed on the specified server. Either install Quota Advisor version 5.3.2190.2 or later, or uninstall Quota Advisor from the server. If Quota Advisor was installed by your OEM, please contact your OEM support for instructions.	DPM cannot protect file servers running versions of QAFilter.sys earlier than 5.3.2190.0. QAFilter.sys is a component of the Veritas Storage Exec, Veritas Storage CeNTral, WQuinn Storage Manager, and WQuinn QuotaAdvisor products.	DPM cannot install the file agent on servers that are running an unsupported version of QAFilter.sys. Do not install an unsupported version of QAFilter.sys on a protected file server after installing the file agent. If your file server meets either of the following criteria, it is running an unsupported version of QAFilter.sys: The file server is a Windows Storage Server or Windows-Powered NAS device that has a version of the user-level or directory-level quota feature installed that is prior to 5.3.2190.0. The file server is running a version of Storage Exec or Storage CeNTral that has a version of the QuotaAdvisor feature installed that is prior to 5.3.2190.2 Note DPM will allow completion of the agent installation on versions 5.3.2190.0 and later, but only 5.3.2190.2 and later versions are officially supported. Directions for obtaining a hotfix that enables DPM to protect a Windows Storage Server or a Windows-Powered NAS device running Storage Manager are available in the Microsoft Knowledge Base article 896718 (https://go.microsoft.com/fwlink/?LinkId=50886).
341: Agent operation failed because credentials provided have insufficient privileges on specified server.	The account used does not have sufficient privileges on the file server. Because the system times of the DPM server, the file server, and the domain controller are not synchronized, Kerberos authentication fails. DNS setting on the DPM server or the file server is not correct.	Retry the operation with an account that has administrator privileges on the specified server. Verify that system times on the DPM server and the file server are synchronized with the system time on the domain controller. Verify that the DNS settings are correct. See “Identifying DNS Errors,” earlier in this chapter.
342: The agent operation failed because the DPM server could not communicate with the specified server.	Firewall configuration on the file server	See the “Managing Servers” chapter in this guide for firewall configuration requirements.
348: An error occurred when the agent operation attempted to communicate with the DPM Agent Coordinator service on the specified server.	Security on the COM object on the file server	Verify COM permissions on the file server. See Resolving "Access Denied" Errors, earlier in this chapter, for instructions.