locked
whs "Cannot mount the backup" RRS feed

  • Question

  • i have been trying (has been 4 hours now) to get whs to open a backup from the 01/20/2011 and it errors out at 82% however the backup from 01/24/2011 works fine

    when i tried to open 01/20/2011 on the 23rd it worked fine but whs has ran automatic updates since then

    any ideas?   also is their a preferred way of attaching or linking error logs to posts? as 60,000 characters seems a bit short for the logs whs creates i had to remove the MountBackup.020111_2580.log file to be allowed to post

    here are the log files i think are relevant if there is anything i missed that might help please let me know

    RestoreOffProc.020111_2592.log

     

    [2/1/2011 6:06:19 PM  94c] Parent 2580 sequence  5037062

    [2/1/2011 6:06:19 PM  94c] OPTION: -v <volume> 0 was specified

    [2/1/2011 6:06:19 PM  94c] OPTION: -X <extend> 1465143296 was specified

    [2/1/2011 6:06:19 PM  94c] GetMountedVolumeLetter: uniqueId = \??\Volume{52b2baec-2e56-11e0-b2f0-00188bd395f4}\

    [2/1/2011 6:06:27 PM  94c] MountedRestoreHelper::GetMountedVolumeLetter() - got volume at Z:\

    [2/1/2011 6:06:33 PM  94c] FindFirstFile failed for volume Z:\, trying GetDiskFreeSpace instead (in case the volume is empty)

    [2/1/2011 6:06:40 PM  94c] GetDiskFreeSpace failed on Z:\

    [2/1/2011 6:06:40 PM  94c] MountedRestoreHelper::GetMountedVolumeLetter() - volume discovered but it's not active yet

    [2/1/2011 6:06:40 PM  94c] MountedRestoreHelper::GetMountedVolumeLetter() - failed getting volume letter

    [2/1/2011 6:06:40 PM  94c] WARN : Unable to locate the mounted volume letter - sleeping 1000ms

    [2/1/2011 6:06:41 PM  94c] GetMountedVolumeLetter: uniqueId = \??\Volume{52b2baec-2e56-11e0-b2f0-00188bd395f4}\

    [2/1/2011 6:06:41 PM  94c] MountedRestoreHelper::GetMountedVolumeLetter() - got volume at Z:\

    [2/1/2011 6:06:44 PM  94c] FindFirstFile failed for volume Z:\, trying GetDiskFreeSpace instead (in case the volume is empty)

    [2/1/2011 6:06:46 PM  94c] GetDiskFreeSpace failed on Z:\

    [2/1/2011 6:06:46 PM  94c] MountedRestoreHelper::GetMountedVolumeLetter() - volume discovered but it's not active yet

    [2/1/2011 6:06:46 PM  94c] MountedRestoreHelper::GetMountedVolumeLetter() - failed getting volume letter

    [2/1/2011 6:06:46 PM  94c] WARN : Unable to locate the mounted volume letter - sleeping 1000ms

    [2/1/2011 6:06:47 PM  94c] GetMountedVolumeLetter: uniqueId = \??\Volume{52b2baec-2e56-11e0-b2f0-00188bd395f4}\

    [2/1/2011 6:06:47 PM  94c] MountedRestoreHelper::GetMountedVolumeLetter() - got volume at Z:\

    [2/1/2011 6:06:49 PM  94c] FindFirstFile failed for volume Z:\, trying GetDiskFreeSpace instead (in case the volume is empty)

    [2/1/2011 6:06:52 PM  94c] GetDiskFreeSpace failed on Z:\

    [2/1/2011 6:06:52 PM  94c] MountedRestoreHelper::GetMountedVolumeLetter() - volume discovered but it's not active yet

    [2/1/2011 6:06:52 PM  94c] MountedRestoreHelper::GetMountedVolumeLetter() - failed getting volume letter

    [2/1/2011 6:06:52 PM  94c] WARN : Unable to locate the mounted volume letter - sleeping 1000ms

    [2/1/2011 6:06:53 PM  94c] GetMountedVolumeLetter: uniqueId = \??\Volume{52b2baec-2e56-11e0-b2f0-00188bd395f4}\

    [2/1/2011 6:06:53 PM  94c] MountedRestoreHelper::GetMountedVolumeLetter() - got volume at Z:\

    [2/1/2011 6:06:55 PM  94c] FindFirstFile failed for volume Z:\, trying GetDiskFreeSpace instead (in case the volume is empty)

    [2/1/2011 6:06:58 PM  94c] GetDiskFreeSpace failed on Z:\

    [2/1/2011 6:06:58 PM  94c] MountedRestoreHelper::GetMountedVolumeLetter() - volume discovered but it's not active yet

    [2/1/2011 6:06:58 PM  94c] MountedRestoreHelper::GetMountedVolumeLetter() - failed getting volume letter

    [2/1/2011 6:06:58 PM  94c] WARN : Unable to locate the mounted volume letter - sleeping 1000ms

    [2/1/2011 6:06:59 PM  94c] GetMountedVolumeLetter: uniqueId = \??\Volume{52b2baec-2e56-11e0-b2f0-00188bd395f4}\

    [2/1/2011 6:06:59 PM  94c] MountedRestoreHelper::GetMountedVolumeLetter() - got volume at Z:\

    [2/1/2011 6:07:01 PM  94c] FindFirstFile failed for volume Z:\, trying GetDiskFreeSpace instead (in case the volume is empty)

    [2/1/2011 6:07:04 PM  94c] GetDiskFreeSpace failed on Z:\

    [2/1/2011 6:07:04 PM  94c] MountedRestoreHelper::GetMountedVolumeLetter() - volume discovered but it's not active yet

    [2/1/2011 6:07:04 PM  94c] MountedRestoreHelper::GetMountedVolumeLetter() - failed getting volume letter

    [2/1/2011 6:07:04 PM  94c] WARN : Unable to locate the mounted volume letter - sleeping 1000ms

    [2/1/2011 6:07:05 PM  94c] GetMountedVolumeLetter: uniqueId = \??\Volume{52b2baec-2e56-11e0-b2f0-00188bd395f4}\

    [2/1/2011 6:07:05 PM  94c] MountedRestoreHelper::GetMountedVolumeLetter() - got volume at Z:\

    [2/1/2011 6:07:07 PM  94c] FindFirstFile failed for volume Z:\, trying GetDiskFreeSpace instead (in case the volume is empty)

    [2/1/2011 6:07:09 PM  94c] GetDiskFreeSpace failed on Z:\

    [2/1/2011 6:07:09 PM  94c] MountedRestoreHelper::GetMountedVolumeLetter() - volume discovered but it's not active yet

    [2/1/2011 6:07:09 PM  94c] MountedRestoreHelper::GetMountedVolumeLetter() - failed getting volume letter

    [2/1/2011 6:07:09 PM  94c] WARN : Unable to locate the mounted volume letter - sleeping 1000ms

    [2/1/2011 6:07:10 PM  94c] GetMountedVolumeLetter: uniqueId = \??\Volume{52b2baec-2e56-11e0-b2f0-00188bd395f4}\

    [2/1/2011 6:07:10 PM  94c] MountedRestoreHelper::GetMountedVolumeLetter() - got volume at Z:\

    [2/1/2011 6:07:13 PM  94c] FindFirstFile failed for volume Z:\, trying GetDiskFreeSpace instead (in case the volume is empty)

    [2/1/2011 6:07:16 PM  94c] GetDiskFreeSpace failed on Z:\

    [2/1/2011 6:07:16 PM  94c] MountedRestoreHelper::GetMountedVolumeLetter() - volume discovered but it's not active yet

    [2/1/2011 6:07:16 PM  94c] MountedRestoreHelper::GetMountedVolumeLetter() - failed getting volume letter

    [2/1/2011 6:07:16 PM  94c] WARN : Unable to locate the mounted volume letter - sleeping 1000ms

    [2/1/2011 6:07:17 PM  94c] GetMountedVolumeLetter: uniqueId = \??\Volume{52b2baec-2e56-11e0-b2f0-00188bd395f4}\

    [2/1/2011 6:07:17 PM  94c] MountedRestoreHelper::GetMountedVolumeLetter() - got volume at Z:\

    [2/1/2011 6:07:19 PM  94c] FindFirstFile failed for volume Z:\, trying GetDiskFreeSpace instead (in case the volume is empty)

    [2/1/2011 6:07:24 PM  94c] GetDiskFreeSpace failed on Z:\

    [2/1/2011 6:07:24 PM  94c] MountedRestoreHelper::GetMountedVolumeLetter() - volume discovered but it's not active yet

    [2/1/2011 6:07:24 PM  94c] MountedRestoreHelper::GetMountedVolumeLetter() - failed getting volume letter

    [2/1/2011 6:07:24 PM  94c] WARN : Unable to locate the mounted volume letter - sleeping 1000ms

    [2/1/2011 6:07:25 PM  94c] GetMountedVolumeLetter: uniqueId = \??\Volume{52b2baec-2e56-11e0-b2f0-00188bd395f4}\

    [2/1/2011 6:07:25 PM  94c] MountedRestoreHelper::GetMountedVolumeLetter() - got volume at Z:\

    [2/1/2011 6:07:32 PM  94c] FindFirstFile failed for volume Z:\, trying GetDiskFreeSpace instead (in case the volume is empty)

    [2/1/2011 6:07:37 PM  94c] GetDiskFreeSpace failed on Z:\

    [2/1/2011 6:07:37 PM  94c] MountedRestoreHelper::GetMountedVolumeLetter() - volume discovered but it's not active yet

    [2/1/2011 6:07:37 PM  94c] MountedRestoreHelper::GetMountedVolumeLetter() - failed getting volume letter

    [2/1/2011 6:07:37 PM  94c] WARN : Unable to locate the mounted volume letter - sleeping 1000ms

    [2/1/2011 6:07:38 PM  94c] GetMountedVolumeLetter: uniqueId = \??\Volume{52b2baec-2e56-11e0-b2f0-00188bd395f4}\

    [2/1/2011 6:07:38 PM  94c] MountedRestoreHelper::GetMountedVolumeLetter() - got volume at Z:\

    [2/1/2011 6:07:39 PM  94c] FindFirstFile failed for volume Z:\, trying GetDiskFreeSpace instead (in case the volume is empty)

    [2/1/2011 6:07:39 PM  94c] GetDiskFreeSpace failed on Z:\

    [2/1/2011 6:07:39 PM  94c] MountedRestoreHelper::GetMountedVolumeLetter() - volume discovered but it's not active yet

    [2/1/2011 6:07:39 PM  94c] MountedRestoreHelper::GetMountedVolumeLetter() - failed getting volume letter

    [2/1/2011 6:07:39 PM  94c] WARN : Unable to locate the mounted volume letter - sleeping 1000ms

    [2/1/2011 6:07:40 PM  94c] ERROR: Unable to locate the mounted volume letter - giving up

    [2/1/2011 6:07:40 PM  94c] Returning 0

    Wednesday, February 2, 2011 2:11 AM

All replies

  • whs log from event viewer


    2/1/2011,10:40:53 PM,Application Error,Error,None,1001,N/A,SERVER,Fault bucket 1582212318.
    2/1/2011,10:40:51 PM,Application Error,Information,(100),1004,N/A,SERVER,"Reporting queued error: faulting application whsbackup.exe, version 6.0.2423.0, faulting module whsbackup.exe, version 6.0.2423.0, fault address 0x0001dcd1."
    2/1/2011,10:40:50 PM,Application Error,Error,None,1001,N/A,SERVER,Fault bucket 1582212318.
    2/1/2011,10:40:36 PM,Application Error,Information,(100),1004,N/A,SERVER,"Reporting queued error: faulting application whsbackup.exe, version 6.0.2423.0, faulting module whsbackup.exe, version 6.0.2423.0, fault address 0x0001dcd1."
    2/1/2011,10:29:38 PM,Application Error,Error,(100),1000,N/A,SERVER,"Faulting application whsbackup.exe, version 6.0.2423.0, faulting module whsbackup.exe, version 6.0.2423.0, fault address 0x0001dcd1."
    2/1/2011,9:43:27 PM,LoadPerf,Information,None,1000,N/A,SERVER,Performance counters for the WmiApRpl (WmiApRpl) service were loaded successfully. The Record Data contains the new index values assigned to this service.
    2/1/2011,9:43:27 PM,LoadPerf,Information,None,1001,N/A,SERVER,Performance counters for the WmiApRpl (WmiApRpl) service were removed successfully. The Record Data contains the new values of the system Last Counter and Last Help registry entries.
    2/1/2011,9:41:53 PM,CqvSvc.exe,Warning,None,9000,N/A,SERVER,"Exception occurred:  System.IO.IOException

    Message:  The process cannot access the file 'C:\inetpub\intranet\health\health.xml' because it is being used by another process.
    "
    2/1/2011,9:41:12 PM,LoadPerf,Information,None,1000,N/A,SERVER,Performance counters for the WmiApRpl (WmiApRpl) service were loaded successfully. The Record Data contains the new index values assigned to this service.
    2/1/2011,9:41:06 PM,LoadPerf,Information,None,1001,N/A,SERVER,Performance counters for the WmiApRpl (WmiApRpl) service were removed successfully. The Record Data contains the new values of the system Last Counter and Last Help registry entries.
    2/1/2011,9:40:10 PM,DriveExtenderMigrator,Information,None,0,N/A,SERVER,Drive Extender Migrator Service started successfully.
    2/1/2011,9:39:47 PM,CqvSvc,Information,None,0,N/A,SERVER,Service started successfully.
    2/1/2011,9:39:39 PM,Windows Search Service,Information,Search service ,1003,N/A,SERVER,"The Windows Search Service started.
    "
    2/1/2011,9:39:28 PM,ESENT,Information,General ,102,N/A,SERVER,Windows (1856) Windows: The database engine started a new instance (0).
    2/1/2011,9:39:28 PM,ESENT,Information,General ,100,N/A,SERVER,SearchIndexer (1856) The database engine 5.02.3790.3959 started.
    2/1/2011,9:39:21 PM,EventSystem,Information,None,4625,N/A,SERVER,The EventSystem sub system is suppressing duplicate event log entries for a duration of 86400 seconds.  The suppression timeout can be controlled by a REG_DWORD value named SuppressDuplicateDuration under the following registry key: HKLM\Software\Microsoft\EventSystem\EventLog.
    2/1/2011,9:39:20 PM,MSDTC,Information,TM,4193,N/A,SERVER,"MS DTC started with the following settings (OFF = 0 and ON = 1):

      Security Configuration:
          Network Administration of Transactions = 0,
          Network Clients = 0,
          Inbound Distributed Transactions using Native MSDTC Protocol = 0,
          Outbound Distributed Transactions using Native MSDTC Protocol = 0,
          Transaction Internet Protocol (TIP) = 0,
          XA Transactions = 0
      Filtering Duplicate events = 1"
    2/1/2011,8:44:09 PM,Application Error,Error,(100),1000,N/A,SERVER,"Faulting application whsbackup.exe, version 6.0.2423.0, faulting module whsbackup.exe, version 6.0.2423.0, fault address 0x0001dcd1."
    2/1/2011,5:30:01 PM,Application Error,Error,None,1001,N/A,SERVER,Fault bucket 1582212318.
    2/1/2011,5:29:58 PM,Application Error,Information,(100),1004,N/A,SERVER,"Reporting queued error: faulting application whsbackup.exe, version 6.0.2423.0, faulting module whsbackup.exe, version 6.0.2423.0, fault address 0x0001dcd1."
    2/1/2011,5:29:55 PM,Application Error,Error,None,1001,N/A,SERVER,Fault bucket 1577806496.
    2/1/2011,5:29:01 PM,Application Error,Information,(100),1004,N/A,SERVER,"Reporting queued error: faulting application whsbackup.exe, version 6.0.2423.0, faulting module whsbackup.exe, version 6.0.2423.0, fault address 0x0003da38."
    2/1/2011,5:28:59 PM,Application Error,Error,None,1001,N/A,SERVER,Fault bucket 1577806496.
    2/1/2011,5:28:26 PM,Application Error,Information,(100),1004,N/A,SERVER,"Reporting queued error: faulting application whsbackup.exe, version 6.0.2423.0, faulting module whsbackup.exe, version 6.0.2423.0, fault address 0x0003da38."
    2/1/2011,5:24:58 PM,Application Error,Error,None,1001,N/A,SERVER,Fault bucket 1577806496.
    2/1/2011,5:24:33 PM,Application Error,Information,(100),1004,N/A,SERVER,"Reporting queued error: faulting application whsbackup.exe, version 6.0.2423.0, faulting module whsbackup.exe, version 6.0.2423.0, fault address 0x0003da38."
    2/1/2011,5:24:26 PM,Application Error,Error,None,1001,N/A,SERVER,Fault bucket 1577806496.
    2/1/2011,5:23:53 PM,Application Error,Information,(100),1004,N/A,SERVER,"Reporting queued error: faulting application whsbackup.exe, version 6.0.2423.0, faulting module whsbackup.exe, version 6.0.2423.0, fault address 0x0003da38."
    2/1/2011,5:23:51 PM,Application Error,Error,None,1001,N/A,SERVER,Fault bucket 1577806496.
    2/1/2011,5:22:50 PM,Application Error,Information,(100),1004,N/A,SERVER,"Reporting queued error: faulting application whsbackup.exe, version 6.0.2423.0, faulting module whsbackup.exe, version 6.0.2423.0, fault address 0x0003da38."
    2/1/2011,5:22:49 PM,Application Error,Error,None,1001,N/A,SERVER,Fault bucket 1583296884.
    2/1/2011,5:21:47 PM,Application Error,Information,(100),1004,N/A,SERVER,"Reporting queued error: faulting application whsbackup.exe, version 6.0.2423.0, faulting module whsbackup.exe, version 6.0.2423.0, fault address 0x0003d848."
    2/1/2011,5:14:39 PM,LoadPerf,Information,None,1000,N/A,SERVER,Performance counters for the WmiApRpl (WmiApRpl) service were loaded successfully. The Record Data contains the new index values assigned to this service.
    2/1/2011,5:14:38 PM,LoadPerf,Information,None,1001,N/A,SERVER,Performance counters for the WmiApRpl (WmiApRpl) service were removed successfully. The Record Data contains the new values of the system Last Counter and Last Help registry entries.
    2/1/2011,5:11:09 PM,DriveExtenderMigrator,Information,None,0,N/A,SERVER,Drive Extender Migrator Service started successfully.
    2/1/2011,5:10:59 PM,CqvSvc,Information,None,0,N/A,SERVER,Service started successfully.
    2/1/2011,5:10:50 PM,Windows Search Service,Information,Search service ,1003,N/A,SERVER,"The Windows Search Service started.
    "
    2/1/2011,5:10:39 PM,ESENT,Information,General ,102,N/A,SERVER,Windows (1788) Windows: The database engine started a new instance (0).
    2/1/2011,5:10:39 PM,ESENT,Information,General ,100,N/A,SERVER,SearchIndexer (1788) The database engine 5.02.3790.3959 started.
    2/1/2011,5:10:32 PM,EventSystem,Information,None,4625,N/A,SERVER,The EventSystem sub system is suppressing duplicate event log entries for a duration of 86400 seconds.  The suppression timeout can be controlled by a REG_DWORD value named SuppressDuplicateDuration under the following registry key: HKLM\Software\Microsoft\EventSystem\EventLog.
    2/1/2011,5:10:31 PM,MSDTC,Information,TM,4193,N/A,SERVER,"MS DTC started with the following settings (OFF = 0 and ON = 1):

      Security Configuration:
          Network Administration of Transactions = 0,
          Network Clients = 0,
          Inbound Distributed Transactions using Native MSDTC Protocol = 0,
          Outbound Distributed Transactions using Native MSDTC Protocol = 0,
          Transaction Internet Protocol (TIP) = 0,
          XA Transactions = 0
      Filtering Duplicate events = 1"
    2/1/2011,5:08:38 PM,CqvSvc,Information,None,0,N/A,SERVER,Service has been successfully shut down.
    2/1/2011,2:03:12 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    2/1/2011,2:02:26 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    2/1/2011,2:01:39 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    2/1/2011,2:01:19 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    2/1/2011,2:01:01 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    2/1/2011,2:00:32 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/31/2011,12:23:51 PM,CqvSvc.exe,Warning,None,9000,N/A,SERVER,"Exception occurred:  System.Runtime.InteropServices.COMException

    Message:  
    "
    1/31/2011,2:03:12 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/31/2011,2:02:26 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/31/2011,2:01:39 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/31/2011,2:01:18 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/31/2011,2:01:02 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/31/2011,2:00:32 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/30/2011,5:33:04 AM,Application Error,Error,(100),1000,N/A,SERVER,"Faulting application whsbackup.exe, version 6.0.2423.0, faulting module whsbackup.exe, version 6.0.2423.0, fault address 0x0001dcd1."
    1/30/2011,2:03:08 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/30/2011,2:02:22 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/30/2011,2:01:36 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/30/2011,2:01:15 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/30/2011,2:00:58 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/30/2011,2:00:33 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/29/2011,2:03:07 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/29/2011,2:02:21 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/29/2011,2:01:35 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/29/2011,2:01:14 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/29/2011,2:00:57 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/29/2011,2:00:32 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/28/2011,8:22:27 PM,CqvSvc.exe,Warning,None,9000,N/A,SERVER,"Exception occurred:  System.Runtime.InteropServices.COMException

    Message:  
    "
    1/28/2011,2:03:18 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/28/2011,2:02:32 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/28/2011,2:01:45 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/28/2011,2:01:25 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/28/2011,2:01:07 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/28/2011,2:00:37 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/27/2011,2:03:12 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/27/2011,2:02:25 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/27/2011,2:01:37 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/27/2011,2:01:17 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/27/2011,2:00:59 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/27/2011,2:00:34 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/26/2011,4:21:42 AM,LoadPerf,Information,None,1000,N/A,SERVER,Performance counters for the WmiApRpl (WmiApRpl) service were loaded successfully. The Record Data contains the new index values assigned to this service.
    1/26/2011,4:21:42 AM,LoadPerf,Information,None,1001,N/A,SERVER,Performance counters for the WmiApRpl (WmiApRpl) service were removed successfully. The Record Data contains the new values of the system Last Counter and Last Help registry entries.
    1/26/2011,4:20:07 AM,CqvSvc.exe,Warning,None,9000,N/A,SERVER,"Exception occurred:  System.IO.IOException

    Message:  The process cannot access the file 'C:\inetpub\intranet\health\health.xml' because it is being used by another process.
    "
    1/26/2011,4:19:53 AM,MsiInstaller,Information,None,11707,NT AUTHORITY\SYSTEM,SERVER,Product: Windows Live ID Sign-in Assistant -- Installation completed successfully.
    1/26/2011,4:18:09 AM,DriveExtenderMigrator,Information,None,0,N/A,SERVER,Drive Extender Migrator Service started successfully.
    1/26/2011,4:17:58 AM,CqvSvc,Information,None,0,N/A,SERVER,Service started successfully.
    1/26/2011,4:17:49 AM,Windows Search Service,Information,Search service ,1003,N/A,SERVER,"The Windows Search Service started.
    "
    1/26/2011,4:17:44 AM,ESENT,Information,General ,102,N/A,SERVER,Windows (1700) Windows: The database engine started a new instance (0).
    1/26/2011,4:17:44 AM,ESENT,Information,General ,100,N/A,SERVER,SearchIndexer (1700) The database engine 5.02.3790.3959 started.
    1/26/2011,4:17:37 AM,EventSystem,Information,None,4625,N/A,SERVER,The EventSystem sub system is suppressing duplicate event log entries for a duration of 86400 seconds.  The suppression timeout can be controlled by a REG_DWORD value named SuppressDuplicateDuration under the following registry key: HKLM\Software\Microsoft\EventSystem\EventLog.
    1/26/2011,4:17:36 AM,MSDTC,Information,TM,4193,N/A,SERVER,"MS DTC started with the following settings (OFF = 0 and ON = 1):

      Security Configuration:
          Network Administration of Transactions = 0,
          Network Clients = 0,
          Inbound Distributed Transactions using Native MSDTC Protocol = 0,
          Outbound Distributed Transactions using Native MSDTC Protocol = 0,
          Transaction Internet Protocol (TIP) = 0,
          XA Transactions = 0
      Filtering Duplicate events = 1"
    1/26/2011,2:03:11 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/26/2011,2:02:25 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/26/2011,2:01:40 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/26/2011,2:01:19 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/26/2011,2:00:54 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/26/2011,2:00:19 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/25/2011,2:03:26 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/25/2011,2:02:40 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/25/2011,2:01:53 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/25/2011,2:01:32 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/25/2011,2:01:07 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/25/2011,2:00:35 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/24/2011,3:49:13 AM,CqvSvc.exe,Warning,None,9000,N/A,SERVER,"Exception occurred:  System.Runtime.InteropServices.COMException

    Message:  
    "
    1/24/2011,2:03:14 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/24/2011,2:02:28 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/24/2011,2:01:41 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/24/2011,2:01:20 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/24/2011,2:00:55 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/24/2011,2:00:23 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/23/2011,5:29:26 AM,CqvSvc.exe,Warning,None,9000,N/A,SERVER,"Exception occurred:  System.IO.IOException

    Message:  The process cannot access the file 'C:\inetpub\intranet\health\health.xml' because it is being used by another process.
    "
    1/23/2011,5:27:35 AM,DrWatson,Information,None,4097,N/A,SERVER,"The application, C:\Program Files\Windows Home Server\whsbackup.exe, generated an application error The error occurred on 01/23/2011 @ 03:27:32.223 The exception generated was 80000003 at address 7C81A3E1 (ntdll!DbgBreakPoint)"
    1/23/2011,5:27:12 AM,Application Error,Error,(100),1000,N/A,SERVER,"Faulting application whsbackup.exe, version 6.0.2423.0, faulting module whsbackup.exe, version 6.0.2423.0, fault address 0x0003da38."
    1/23/2011,2:03:15 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/23/2011,2:02:28 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/23/2011,2:01:40 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/23/2011,2:01:20 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/23/2011,2:00:54 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/23/2011,2:00:22 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/22/2011,8:00:39 AM,DrWatson,Information,None,4097,N/A,SERVER,"The application, C:\Program Files\Windows Home Server\whsbackup.exe, generated an application error The error occurred on 01/22/2011 @ 06:00:37.754 The exception generated was 80000003 at address 7C81A3E1 (ntdll!DbgBreakPoint)"
    1/22/2011,8:00:25 AM,Application Error,Error,(100),1000,N/A,SERVER,"Faulting application whsbackup.exe, version 6.0.2423.0, faulting module whsbackup.exe, version 6.0.2423.0, fault address 0x0003da38."
    1/22/2011,2:03:19 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/22/2011,2:02:33 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/22/2011,2:01:47 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/22/2011,2:01:27 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/22/2011,2:01:01 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/22/2011,2:00:29 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/21/2011,11:49:47 AM,CqvSvc.exe,Warning,None,9000,N/A,SERVER,"Exception occurred:  System.Runtime.InteropServices.COMException

    Message:  
    "
    1/21/2011,2:05:04 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/21/2011,2:04:01 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/21/2011,2:03:03 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/21/2011,2:02:34 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/21/2011,2:02:02 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/21/2011,2:01:18 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/20/2011,2:03:28 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/20/2011,2:02:37 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/20/2011,2:01:50 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/20/2011,2:01:29 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/20/2011,2:01:03 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/20/2011,2:00:31 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/19/2011,5:30:07 AM,CqvSvc.exe,Warning,None,9000,N/A,SERVER,"Exception occurred:  System.NullReferenceException

    Message:  Object reference not set to an instance of an object.
    "
    1/19/2011,5:27:58 AM,DrWatson,Information,None,4097,N/A,SERVER,"The application, C:\Program Files\Windows Home Server\whsbackup.exe, generated an application error The error occurred on 01/19/2011 @ 03:27:58.472 The exception generated was 80000003 at address 7C81A3E1 (ntdll!DbgBreakPoint)"
    1/19/2011,5:27:54 AM,Application Error,Error,(100),1000,N/A,SERVER,"Faulting application whsbackup.exe, version 6.0.2423.0, faulting module whsbackup.exe, version 6.0.2423.0, fault address 0x0003da38."
    1/19/2011,5:25:40 AM,CqvSvc.exe,Warning,None,9000,N/A,SERVER,"Exception occurred:  System.IO.IOException

    Message:  The process cannot access the file 'C:\inetpub\intranet\health\health.xml' because it is being used by another process.
    "
    1/19/2011,2:03:10 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/19/2011,2:02:24 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/19/2011,2:01:38 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/19/2011,2:01:16 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/19/2011,2:00:51 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/19/2011,2:00:19 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/18/2011,7:51:20 PM,CqvSvc.exe,Warning,None,9000,N/A,SERVER,"Exception occurred:  System.Runtime.InteropServices.COMException

    Message:  
    "
    1/18/2011,5:53:18 AM,DrWatson,Information,None,4097,N/A,SERVER,"The application, C:\Program Files\Windows Home Server\whsbackup.exe, generated an application error The error occurred on 01/18/2011 @ 03:53:17.559 The exception generated was 80000003 at address 7C81A3E1 (ntdll!DbgBreakPoint)"
    1/18/2011,5:53:09 AM,Application Error,Error,(100),1000,N/A,SERVER,"Faulting application whsbackup.exe, version 6.0.2423.0, faulting module whsbackup.exe, version 6.0.2423.0, fault address 0x0003da38."
    1/18/2011,2:03:17 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/18/2011,2:02:30 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/18/2011,2:01:44 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/18/2011,2:01:24 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/18/2011,2:00:58 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/18/2011,2:00:25 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/17/2011,6:41:16 AM,CqvSvc.exe,Warning,None,9000,N/A,SERVER,"Exception occurred:  System.NullReferenceException

    Message:  Object reference not set to an instance of an object.
    "
    1/17/2011,6:39:40 AM,DrWatson,Information,None,4097,N/A,SERVER,"The application, C:\Program Files\Windows Home Server\whsbackup.exe, generated an application error The error occurred on 01/17/2011 @ 04:39:38.461 The exception generated was 80000003 at address 7C81A3E1 (ntdll!DbgBreakPoint)"
    1/17/2011,6:39:20 AM,Application Error,Error,(100),1000,N/A,SERVER,"Faulting application whsbackup.exe, version 6.0.2423.0, faulting module whsbackup.exe, version 6.0.2423.0, fault address 0x0003da38."
    1/17/2011,6:38:46 AM,CqvSvc.exe,Warning,None,9000,N/A,SERVER,"Exception occurred:  System.IO.IOException

    Message:  The process cannot access the file 'C:\inetpub\intranet\health\health.xml' because it is being used by another process.
    "
    1/17/2011,2:03:22 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/17/2011,2:02:37 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/17/2011,2:01:49 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/17/2011,2:01:29 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/17/2011,2:01:03 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/17/2011,2:00:31 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/16/2011,5:02:13 AM,DrWatson,Information,None,4097,N/A,SERVER,"The application, C:\Program Files\Windows Home Server\whsbackup.exe, generated an application error The error occurred on 01/16/2011 @ 03:02:12.648 The exception generated was 80000003 at address 7C81A3E1 (ntdll!DbgBreakPoint)"
    1/16/2011,5:02:00 AM,Application Error,Error,(100),1000,N/A,SERVER,"Faulting application whsbackup.exe, version 6.0.2423.0, faulting module whsbackup.exe, version 6.0.2423.0, fault address 0x0003d848."
    1/16/2011,4:52:06 AM,CqvSvc.exe,Warning,None,9000,N/A,SERVER,"Exception occurred:  System.IO.IOException

    Message:  The process cannot access the file 'C:\inetpub\intranet\health\health.xml' because it is being used by another process.
    "
    1/16/2011,4:05:55 AM,CqvSvc.exe,Warning,None,9000,N/A,SERVER,"Exception occurred:  System.Runtime.InteropServices.COMException

    Message:  
    "
    1/16/2011,2:03:08 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/16/2011,2:02:22 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/16/2011,2:01:37 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/16/2011,2:01:17 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/16/2011,2:00:51 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/16/2011,2:00:20 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/15/2011,2:03:09 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/15/2011,2:02:22 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/15/2011,2:01:36 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/15/2011,2:01:16 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/15/2011,2:00:51 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/15/2011,2:00:15 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/14/2011,2:03:04 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/14/2011,2:02:18 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/14/2011,2:01:33 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/14/2011,2:01:12 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/14/2011,2:00:47 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/14/2011,2:00:14 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/13/2011,12:04:32 PM,CqvSvc.exe,Warning,None,9000,N/A,SERVER,"Exception occurred:  System.Runtime.InteropServices.COMException

    Message:  
    "
    1/13/2011,12:03:31 PM,CqvSvc.exe,Warning,None,9000,N/A,SERVER,"Exception occurred:  System.Management.ManagementException

    Message:  Shutting down 
    "
    1/13/2011,2:03:10 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/13/2011,2:02:24 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/13/2011,2:01:40 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/13/2011,2:01:18 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/13/2011,2:00:53 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/13/2011,2:00:21 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/12/2011,2:03:13 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/12/2011,2:02:28 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/12/2011,2:01:41 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/12/2011,2:01:20 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/12/2011,2:00:55 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/12/2011,2:00:23 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/11/2011,2:03:04 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/11/2011,2:02:18 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/11/2011,2:01:33 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/11/2011,2:01:13 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/11/2011,2:00:47 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/11/2011,2:00:16 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/10/2011,7:53:07 PM,CqvSvc.exe,Warning,None,9000,N/A,SERVER,"Exception occurred:  System.Runtime.InteropServices.COMException

    Message:  
    "
    1/10/2011,2:02:49 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/10/2011,2:02:08 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/10/2011,2:01:22 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/10/2011,2:00:57 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    1/10/2011,2:00:34 AM,Chkdsk,Information,None,26212,N/A,SERVER,Chkdsk was executed in read-only mode on a volume snapshot.
    Wednesday, February 2, 2011 5:02 AM
  • Your logfile indicates, that whsbackup.exe is crashing.

    Why I cannot tell, I assume, your backup database is corrupted. This can happen due to damaged sectors on the server disk, a crash during an attempted write access to the database or similar stuff.

    Maybe you can to try the repair functionality in the console. If you have a spare big enough disk, you still can try to use clientrestorewizard.exe to restore the entire volume with the missing files to that disk.

    Best greetings from Germany
    Olaf

    Thursday, February 3, 2011 8:01 AM
    Moderator
  • i ran check disk on all attached drives with no errors how would the database get corrupted?
    Tuesday, February 8, 2011 12:48 AM
  • Try upgrading or uninstalling any addons. I had a problem with an older version of Lights-Out which disappeared once I upgraded. Failing that, maybe you just have too many files for it to handle . . .
    Friday, February 11, 2011 12:07 AM
  • the only addon i have installed is the windows home server toolkit 1.1 the server has 1.37 TB of storage across 5 drives only 144.08 GB free space   904 GB is taken up by PC Backups only 5 computers are attached to this server the pc backup i am trying to open has somewhere around 500,000 files as when i counted the current number of files as of today is 596,140

     

    i am going to try uninstalling the whs server toolkit then cleaning up the backup database and trying again

     

    also do i understand correctly that the "repair" option simply erases everything and starts over?

    Monday, February 14, 2011 3:25 AM
  • ok uninstalled whs toolkit and cleaned up database still no change would the whsbackup.exe crash dump help figure this out?

    any other ideas?

    Monday, February 14, 2011 7:26 AM
  • How did you clean the backup database - deleting the files manually or with a tool? The manual method would be described in this thread.

    If this method does not help, I would recommend a server reinstall.

    Best greetings from Germany
    Olaf

    Monday, February 14, 2011 3:40 PM
    Moderator
  • i used the cleanup button in the windows home server console

    i am interested in the recovery of the backup and preventing this problem from reoccurring

    i am able to open backups before and after that date but i have not found any disk errors and there have been no power failures since the backup was made so i dont know how corruption could have occurred but i do need to find out....

    i can open backups all the way from 8/3/2009 to last night except the backup on 1/20/2011

    i had problems with the server running out of memory when backing up my computer when i first set it up with 512MB of ram

    after upgrading to 1GB of ram the problem disappeared the hardware does not support memory above 1GB total

    • Edited by sims80 Monday, February 21, 2011 2:38 AM rather not post twice in a row
    Monday, February 21, 2011 2:01 AM
  • Well almost a year later I finally get another drive that I can attempt a restore to here's the results of my attempt today

    After about 30 minutes of the restore running I get
    "I/O error reading clusters 5051383 through 5051383 on the server.

    Do you want to continue?"

    I click yes an after a short pause I get
    "Unable to refresh RestoreWizard from your server. Your server
    may be an older version of windows home server than this CD or
    your server may be damaged, we will attempt a restore with an
    older version."

    Then the above repeats and the restore cd crashes (restarts the computer)

    Chkdsk comes back clean on all drives both on the server and the computer I am restoring

    Ps just because it's a old post doesn't mean it's any less relevant as the problem still hasn't been solved
    Sunday, January 22, 2012 10:29 PM
  • The message

    "I/O error reading clusters 5051383 through 5051383 on the server."

    would point to damaged sectors on the disk, which stores the relevant backup database files, or to damaged segments within the database (although not always the messages are reliable if it comes to determine the cause).
    So there is not much you can do. Running chkdsk /r on each disk on the server, as described in the FAQ How to check all the drives in your server for errors here in the forum, might fix the disk issues, but usually not repair the database. If there is important data, you can mount the backup into a running OS and try to copy the data step by step.

    Best greetings from Germany
    Olaf

    Monday, January 23, 2012 10:48 AM
    Moderator
  • i have checked all drives for errors but all come back clear no errors and i cannot mount the backup on another computer because it says cannot mount backup at 82%

    any way i can force it? or otherwise recover the data?

    Monday, January 23, 2012 4:53 PM
  • Once the backup is damaged in a way, that it cannot be read from different machines, and also a Backup Database Repair from within console does not fix the issue, the only thing you can try is to check, if a backup from a different date can be mounted.

    If this also does not work, the backup database is not recoverable, unless you did backups of the backup database with the WHS DB Backup Add-On.

    Best greetings from Germany
    Olaf

    Tuesday, January 24, 2012 11:53 AM
    Moderator
  • well i tried restoring to a backup from 7/18/2011 most recent backup and its been at 24 minutes left for 2 days now

    so im going to try the repair option and hope it doesnt just delete everything

    Wednesday, January 25, 2012 1:15 AM
  • well i inteded to but then i got side tracked as i still think there must be some way to recover the only file out of the 750gb backed up that i really need is only 4KB is there anyway i can recover that file? are backups stored as on the harddrive plaintext?
    Wednesday, January 25, 2012 5:11 AM
  • The backup database is a very complex collection of clusters and pointers to those.

    Did you already try to mount the backup from within the console ny double clicking the computer, selecting a backup from here and click Open (which would be the preferred method to recover a single file)?

    Best greetings from Germany
    Olaf

    Wednesday, January 25, 2012 7:15 AM
    Moderator
  • as i stated when i started the thread it hangs at 82% then says cannot mount backup regardless of the system i try to open it on i only have a vista and several xp machines on my network but the result is the same on all no problems with any of the other backed up computers that i know of although i havent needed to use the backup for them yet

     

    another oddity is that the computer im having problems with its failed backups are not being cleared on cleanup even when set to do so on next clean up and then cleanup is invoked from the whs console

    Wednesday, January 25, 2012 2:59 PM
  • Which also would point to some corruption in the backup database, related to a segment belonging to that special PC (maybe its cluster assignments). Some unexpected data is found and causing the software to crash or error out.

    So this does not look good really.

    Best greetings from Germany
    Olaf

    Wednesday, January 25, 2012 11:02 PM
    Moderator
  • ok i finally tried to do a repair but despite it completing successfully it didn't actually fix anything 
    Thursday, January 26, 2012 3:49 AM
  • so no way at all to recover then huh?

    i think this is likely the last question

    if i call microsoft support on the matter is there anything they could do or would i just be wasting $79


    • Edited by sims80 Tuesday, February 7, 2012 3:07 AM
    Tuesday, February 7, 2012 3:06 AM
  • The product is not even part of the official support chain, since it is OEM/Systembuilder only. So I would assume, a support call would not solve anything.

    And I am afraid, there is not much they can do even if they wanted due to the proprietary format of the backup database. If anybody, the WHS developer team could look into it, but I highly doubt, that they will get involved.

    Sorry for the bad news.

    Best greetings from Germany
    Olaf

    • Proposed as answer by clnatr Saturday, February 11, 2012 10:43 PM
    • Unproposed as answer by clnatr Saturday, February 11, 2012 10:44 PM
    Tuesday, February 7, 2012 9:29 AM
    Moderator
  • I had the same error and found this page:
    http://kelvyntaylor.blogspot.com/2010/11/fixing-cannot-mount-backup-problem-in.html

    Their instructions were to run diskpart as administrator and then "automount enable" - this worked perfectly for me, first try.  Now all my restore sets are usable again! :)

    A recommendation was also to ensure that your Z: drive was not mapped - that is the default letter that will be used when you open a restore set.

    My system is Windows 7 Home Premium (64 bit).  I have not tested opening restore set from my older systems yet (Windows XP Pro and Vista Ultimate 64 bit).

    Best of luck with your own restores!

    • Edited by clnatr Saturday, February 11, 2012 10:51 PM link
    Saturday, February 11, 2012 10:45 PM