SRMSVC event ID 8197

▲
1
▼

Update: actual answer was finally found, see self-answer below.

I have a Windows 2003 R2 machine that is giving an Event ID 8197 about once an hour and ten minutes. The full error is attached below. The machine is primary used to host IIS webpages and SMTP. There is no known scheduled tasks on the machine.

I have read a lot of Google Search and Microsoft docs, but none of the suggestions found there have any impact. What I am curious is if there is any way to convert the SRMVOLMC81 and SRMVOLMC57 into mount point data so I could at least know where the error is sourcing from (there are no related errors in the logs, just the 8197 every hour and ten).

Event Type: Error
Event Source:   SRMSVC
Event Category: None
Event ID:   8197
Date:       2/7/2011
Time:       11:32:21 AM
User:       N/A
Computer:   SERVER001
Description:
File Server Resource Manager Service error: Unexpected error. 

Error-specific details:
   Error: GetVolumeNameForVolumeMountPoint, 0x80070001, Incorrect function.


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 52 4d 56 4f 4c 4d 43   SRMVOLMC
0008: 38 31 00 00 00 00 00 00   81......
0010: 53 52 4d 56 4f 4c 4d 43   SRMVOLMC
0018: 35 37 00 00 00 00 00 00   57......
windows-event-log
windows-server-2003-r2
asked on Server Fault Feb 7, 2011 by Godeke • edited Feb 15, 2011 by Godeke

2 Answers

▲
1
▼

If this is a 2003 machine see PRB: GetVolumeNameForVolumeMountPoint API may return Incorrect Name for Volumes with Multiple Names

answered on Server Fault Feb 7, 2011 by Jim B
▲
0
▼

As Windows still doesn't have a native ISO mount ability, I was using the Virtual CD-ROM Driver from Microsoft. This is described here: http://jamesewelch.wordpress.com/2007/08/13/mounting-an-iso-image-using-microsofts-virtual-cdrom-driver/

I used this to mount ISO files which in turn were shared across the network for deployment. As we no longer deploy any application this way I removed this tool and the error logs cleared up. No more error ever hour and some minutes.

Obviously, this driver is unsupported, but this fix would have been instantly obvious if the mount point error reported what it was trying to mount in a more usable manner.

answered on Server Fault Feb 15, 2011 by Godeke

User contributions licensed under CC BY-SA 3.0