Thanks for your reply. Looks like I have the right version of tools installed.
I had run windows update, butI guess there were still some updates to the updates and some updates to the updates updates left to install, as always. I did that and then reinstalled Tools and still have the same issue. Here are some of the error messages and windows events...
The Create Virtual Machine Snapshot task fails with status:
Create virtual machine snapshot
VMName
Cannot create a quiesced snapshot because the
create snapshot operation exceeded the time limit
for holding off I/O in the frozen virtual machine.
The following four errors are logged in the Event Viewer's Application log after every attempted snapshot:
#1....
Log Name: Application
Source: VSS
Date: 10/25/2010 1:35:03 PM
Event ID: 12289
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer:
Description:
Volume Shadow Copy Service error: Unexpected error DeviceIoControl(
?\fdc#generic_floppy_drive#6&2bc13940&0&0#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b} - 0000000000000418,0x00560000,0000000000000000,0,00000000002332C0,4096,[0]). hr = 0x80070001, Incorrect function.
.
Operation:
Exposing Recovered Volumes
Locating shadow-copy LUNs
PostSnapshot Event
Executing Asynchronous Operation
Context:
Device:
?\fdc#generic_floppy_drive#6&2bc13940&0&0#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
Examining Detected Volume: Existing -
?\fdc#generic_floppy_drive#6&2bc13940&0&0#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
Execution Context: Provider
Provider Name: VMware Snapshot Provider
Provider Version: 1.0.0
Provider ID: {564d7761-7265-2056-5353-2050726f7669}
Current State: DoSnapshotSet
Event Xml:
DeviceIoControl(
?\fdc#generic_floppy_drive#6&2bc13940&0&0#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b} - 0000000000000418,0x00560000,0000000000000000,0,00000000002332C0,4096,[0])
Operation:
Exposing Recovered Volumes
Locating shadow-copy LUNs
PostSnapshot Event
Executing Asynchronous Operation
Context:
Device:
?\fdc#generic_floppy_drive#6&2bc13940&0&0#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
Examining Detected Volume: Existing -
?\fdc#generic_floppy_drive#6&2bc13940&0&0#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
Execution Context: Provider
Provider Name: VMware Snapshot Provider
Provider Version: 1.0.0
Provider ID: {564d7761-7265-2056-5353-2050726f7669}
Current State: DoSnapshotSet
#2....
Log Name: Application
Source: ESENT
Date: 10/25/2010 1:35:04 PM
Event ID: 482
Task Category: General
Level: Error
Keywords: Classic
User: N/A
Computer:
Description:
Directory (1072) An attempt to write to the file "
?\Volume{49b11140-e066-11df-9b39-00505685000a}\ProgramData\VMware\VDM\ldap\data\VMwareVDMDS\edb.log" at offset 1287680 (0x000000000013a600) for 512 (0x00000200) bytes failed after 0 seconds with system error 19 (0x00000013): "The media is write protected. ". The write operation will fail with error -1032 (0xfffffbf8). If this error persists then the file may be damaged and may need to be restored from a previous backup.
Event Xml:
?\Volume{49b11140-e066-11df-9b39-00505685000a}\ProgramData\VMware\VDM\ldap\data\VMwareVDMDS\edb.log
#3....
Log Name: Application
Source: ESENT
Date: 10/25/2010 1:35:04 PM
Event ID: 408
Task Category: Logging/Recovery
Level: Error
Keywords: Classic
User: N/A
Computer:
Description:
Directory (1072) Unable to write to logfile
?\Volume{49b11140-e066-11df-9b39-00505685000a}\ProgramData\VMware\VDM\ldap\data\VMwareVDMDS\edb.log. Error -1032 (0xfffffbf8).
Event Xml:
?\Volume{49b11140-e066-11df-9b39-00505685000a}\ProgramData\VMware\VDM\ldap\data\VMwareVDMDS\edb.log