Unfortunately I too cannot find a 2003 server forum, so hopefully someone here may be to provide some insight to a problem I have run into. I am just configuring FSRM on 1 of our windows 2003 R2 servers and when the service is started an error is entered in the application log about every hour. Event Type:ErrorEvent Source:SRMSVCEvent Category:NoneEvent ID:8197Date:10/26/2009Time:4:14:38 PMUser:N/AComputer:CB-FILESERV-06Description:File Server Resource Manager Service error: Unexpected error. Error-specific details: Error: GetVolumeNameForVolumeMountPoint, 0x80070001, Incorrect function. I cannot find any information on this at all. Any that I have found refer to email functionality. Everything appears to run fine (1 file blocking rule and email notification works). Anythoughts would be appreciated. thanks

Hello ricklaur, Based on the research, the Error-specific details indicates that FSRM is failing to get a volume name for a mount point. 1. Install the hotfixes and reboot the server The computer may stop responding when you run the disk quota-related functions that are provided by the File Server Resource Manager (FSRM) component on a Windows Server 2003 R2-based computer http://support.microsoft.com/kb/939446 On a Windows Server 2003 R2-based computer, the Quota function of the File Server Resource Manager (FSRM) may report incorrect disk usage when both the Quota function and the shadow copies are configured on the same volume http://support.microsoft.com/kb/944830 2. Meanwhile, please make sure "System" has full access to quota.xml on all the volumes (Quota.xml is located inside the hidden folder System Volume Information\SRM). Please also check whether the volume of multiple GUIDs in the following scenarios: a. Dual booting two or more copies of Windows which access the drive. b. Using a volume on a shared disk in a cluster where multiple nodes have accessed the volume. c. Moving the disk which hosts the volume from one computer to another. d. In a SAN environment where the volume was assigned to multiple instances of Windows. I suspect that FSRM may hit the same issue as described in the following KB: 959573 PRB: GetVolumeNameForVolumeMountPoint API may return Incorrect Name for Volumes with Multiple Names http://support.microsoft.com/kb/959573 Hope this can be helpful. Best Regards, David ShenThis posting is provided "AS IS" with no warranties, and confers no rights.