• Question

  • In the event log of a protected client running Windows2003 R2 64bit, I am seeing many, many of these errors in the application event log during the time the replications are performed. Recovery points are being created and all appears normal on the DPM 2010 server.

    EVENT ID 12290

    Volume Shadow Copy Service warning: GetVolumeNameForVolumeMountPointW(
    '\\?\Volume{044f7092-f35e-11dc-95a5-001d0965c9a7}\'): 0x00000003.  hr = 0x00000000.

    Any good suggestions on the cause of this and on a quick fix ?

    Tuesday, October 5, 2010 5:26 PM


All replies

  • Error ID 12290 indicates a time out error in the VSS writers. On the protected client running Windows 2003 R264bit can you run a vssadmin list writers when the error occurs to see if a VSS writer is in a failed state. It may not be the VSS writer you are using to back data up on that server but may be trying to start that VSS writer when the RA process starts.

    Also have a look at this Microsoft KB as it may apply to your situation.

    Tuesday, October 5, 2010 9:36 PM
  • Tried that. For each entry listed it reports: "Last error: No error". A review of the application log shows that the errors appear shortly after the DPM sync. 15minutes after each hour - every hour.

    Could it be due to a disk I/O overload because the data drive being protected still has Volume Shadow Copy enabled on it and is still using the same data drive to store the Volume Shadow Copy Recovery Points ? Note that VSC is configured to only create a recovery point once a day at 9:00PM, but these errors repeat every hour.

    Thursday, October 7, 2010 4:04 PM
  • On the protected server where you are seeing the errors can you run diskpart. Do a list disk, select the drive that shadow copies are being created on and do a detail disk. You should be able to see the volume identifier that is appearing in the event log. Does the volume status show as healthy?

    Can you also check to make sure that the VSC volumes are not reaching a set limit using the properties of the drive that VSC is writing to, under shadow copies check the settings to see what the limit is and whether you are nearing that limit.

    Thursday, October 7, 2010 8:51 PM
  • I disabled Volume Shadow Copy on the client target, rebooted and I am still seeing similar error messages in the event logs. For example:

    Volume Shadow Copy Service warning: GetVolumeNameForVolumeMountPointW( '\\?\Volume{044f7092-f35e-11dc-95a5-001d0965c9a7}\'): 0x00000003. hr = 0x00000000.

    Monday, October 25, 2010 7:47 PM
  • anyone ? time to call MS Technical Support ?
    Thursday, November 4, 2010 6:28 PM
  • Run mountvol from a command prompt on the protected server. Match this to a mount point so you know which volume this is referring to. Run diskpart and select the disk the volume is on, do a detail disk and match up the mount point info. Is there a volume there that is marked as raw or in an error state?

    I'd suggest making sure that patches are up to date on the protected server and also have a loook at even though it's not directly relevant I'd try updating to make sure you have the latest VSS patch (also mentioned here as the replacement for 940349

    Thursday, November 4, 2010 9:20 PM
  • Protected server is up-to-date on patches, but what about this hotfix - ?

    Sounds logical, but these "un-official" hotfixes scare the ____ out of me, especially on a production critical server.

    • Marked as answer by tgoetzman Tuesday, January 18, 2011 5:33 PM
    Tuesday, November 9, 2010 8:12 PM