Code:
Event[4]:
Log Name: Application
Source: VSS
Date: 2011-09-09T18:06:35.000
Event ID: 12348
Task: N/A
Level: Warning
Opcode: Info
Keyword: Classic
User: N/A
User Name: N/A
Computer: Peter-PC
Description:
Volume Shadow Copy Service warning: VSS was denied access to the root of volume \\?\Volume{a566d7d6-ecf4-11df-82db-6cf049ec58f2}\. Denying administrators from accessing volume roots can cause many unexpected failures, and will prevent VSS from functioning properly. Check security on the volume, and try the operation again.
Operation:
Removing auto-release shadow copies
Loading provider
Context:
Execution Context: System Provider
Resolve
Ensure that VSS has access to the volume root directory
If the Volume Shadow Copy Service (VSS) does not have access to the volume root directory, shadow copy creation on the volume will fail.
To perform this procedure, you must have membership in
Administrators, or you must have been delegated the appropriate authority.
To ensure that VSS has access to the volume root directory:
- Open an elevated Command Prompt window. Click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
- Type icacls <VolumeRootPath> /grant system:f at the command prompt, where <VolumeRootPath> is the path to the volume root directory, for example, D:\.
For more information about the
icaclscommand, see
Icacls.
Verify
To verify that the Volume Shadow Copy Service (VSS) is operating correctly, retry the previous VSS operation.
----------------------------------------------------------------------------------------------------------
Code:
Event[1]:
Log Name: Application
Source: CVHSVC
Date: 2011-09-09T18:13:01.000
Event ID: 100
Task: Client Virtualization Handler
Level: Warning
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Peter-PC
Description:
Information only. Failed to complete bits job
-----------------------------------------------------------------------------------------------------------
Code:
Event[13]:
Log Name: Application
Source: Windows Error Reporting
Date: 2011-09-09T18:03:15.000
Event ID: 1001
Task: N/A
Level: Information
Opcode: Info
Keyword: Classic
User: N/A
User Name: N/A
Computer: Peter-PC
Description:
Fault bucket , type 0
Event Name: StartupRepairOnline
Response: Not available
Cab Id: 0
Problem signature:
P1: 6.1.7600.16385
P2: 6.1.7600.16385
P3: Gigabyte Technology Co., Ltd.
P4: 171
P5: 0
P6: AutoFailover
P7: 1
P8: NoRootCause
P9:
P10:
Attached files:
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_6.1.7600.16385_5d9d6d12f486f9f3e780236dbd53daacbc746ecd_cab_11bcfc48
Analysis symbol:
Rechecking for solution: 0
Report Id: 997eb835-db05-11e0-ac0a-6cf049ec58f2
Report Status: 4
------------------------------------------------------------------------------------------------------------
Code:
Event[21]:
Log Name: Application
Source: Application Virtualization Client
Date: 2011-09-09T18:02:57.000
Event ID: 3057
Task: N/A
Level: Warning
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Peter-PC
Description:
{tid=A5C}
The Application Virtualization Client Core initialized correctly.
Installed Product:
Version: 4.6.0.1523
Install Path: C:\Program Files (x86)\Microsoft Application Virtualization Client
Global Data Directory: C:\ProgramData\Microsoft\Application Virtualization Client\
Machine Name: PETER-PC
Operating System: Windows 7 64-bit Service Pack 1.0 Build 7601
OSD Command:
Probably ought to look at those applications and reinstall them..