When Backup Exec Remote Agent for Windows Systems (RAWS) is installed on server with SQL 2005, SQL reporting takes inordinate amount of time to run. Before installation of RAWS, reports would take 20 to 30 seconds to complete. After RAWS installation, same reports take over 20 minutes to complete.
If the Deduplication Option is not being used, log on to the affected SQL server, and follow these steps:
Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.
On the Windows Operating System that is running Microsoft SQL Server:
1. Click Start | Run and type REGEDIT to open the Windows registry editor
2. Browse the registry tree to the following registry key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\NetworkProvider\Order
3. Delete "PDVFSNP," from value ProviderOrder
Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.
This issue is currently under investigation by Symantec Corporation. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release. If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Symantec Sales representative or the Symantec Sales group to discuss these concerns. For information on how to contact Symantec Sales, please see http://www.symantec.com Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.
Customers experiencing this issue are encouraged to contact Symantec Technical Support as data is still being collected to assist in resolving this issue.