Receiving VSS Error 8193 The object invoked has disconnected from its clients.


Receiving VSS Error 8193 The object invoked has disconnected from its...
Author
Message
tfedor
tfedor
New Member
New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)
Group: Forum Members
Posts: 3, Visits: 14
I have been running V6 on Windows 7 without an issue for almost 9 months.  I have upgraded to Windows 10 and when trying to execute a full or incremental backup I keep receiving the following error as noted below.

I have tried the Batch file fix and have downloaded the 64-bit VSS executible fix from this site.  Neither have resolved the problem.
I may be looking at this kind of screwy but from the logs it almost looks like somewhere a completion message is being sent halfway through a backup causing VSS to disconnect, and subsequently causing a backup error.  Like I said I may be wrong, but regardless, need some direction in order to resolve this issue.


Windows 10 Event Log

Log Name: Application

Source: VSS
Event ID: 8193
Level: Error
Volume Shadow Copy Service error: Unexpected error calling routine IVssAsync::QueryStatus.  hr = 0x80010108, The object invoked has disconnected from its clients.
Operation:
   BackupComplete Event
   Executing Asynchronous Operation
Context:
   Current State: BackupComplete



Reflect V6 Backup Log
Backup aborted! - Unable to read from disk - Error Code 21 - The device is not ready.

Reflect 6 VSS Log

(Gathering writer metadata...)

(Waiting for the asynchronous operation to finish...)
Initialize writer metadata ...
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get exclude files
- Enumerate components
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get file list descriptors
- Get database descriptors
- Get log descriptors
Discover directly excluded components ...
- Excluding writer '' since it has no selected components for restore.
- Excluding writer '' since it has no selected components for restore.
- Excluding writer 'MSSearch Service Writer' since it has no selected components for restore.
- Excluding writer 'BITS Writer' since it has no selected components for restore.
- Excluding writer 'Shadow Copy Optimization Writer' since it has no selected components for restore.
Discover components that reside outside the shadow set ...
Discover all excluded components ...
Discover excluded writers ...
Discover explicitly included components ...
Verifying explicitly specified writers/components ...
Select explicitly included components ...
 * Writer 'Task Scheduler Writer':
   - Add component \TasksStore
 * Writer 'VSS Metadata Store Writer':
   - Add component \WriterMetadataStore
 * Writer 'Performance Counters Writer':
   - Add component \PerformanceCounters
 * Writer 'IIS Config Writer':
   - Add component \IISCONFIG
 * Writer 'Registry Writer':
   - Add component \Registry
 * Writer 'COM+ REGDB Writer':
   - Add component \COM+ REGDB
 * Writer 'WMI Writer':
   - Add component \WMI
 * Writer 'MSMQ Writer (MSMQ)':
   - Add component \config
   - Add component \storage
Creating shadow set {3ce6cc32-1796-47da-9021-16e456fa97d0} ...
- Adding volume \\?\Volume{61530744-e66a-11e3-a96b-806e6f6e6963}\ [] to the shadow set...
- Adding volume \\?\Volume{61530745-e66a-11e3-a96b-806e6f6e6963}\ [C:\] to the shadow set...
- Adding volume \\?\Volume{4666cb39-c4f9-11e4-86b2-90489a0010ee}\ [F:\] to the shadow set...
Preparing for backup ...
(Waiting for the asynchronous operation to finish...)
(Waiting for the asynchronous operation to finish...)
Creating the shadow (DoSnapshotSet) ...
(Waiting for the asynchronous operation to finish...)
(Waiting for the asynchronous operation to finish...)
Shadow copy set succesfully created.
Saving the backup components document ...

List of created shadow copies:


Querying all shadow copies with the SnapshotSetID {3ce6cc32-1796-47da-9021-16e456fa97d0} ...

* SNAPSHOT ID = {f4009c0e-c62a-4a2e-a4e1-1c7aa4576f18} ...
   - Shadow copy Set: {3ce6cc32-1796-47da-9021-16e456fa97d0}
   - Original count of shadow copies = 3
   - Original Volume name: \\?\Volume{4666cb39-c4f9-11e4-86b2-90489a0010ee}\ [F:\]
   - Creation Time: 12/7/2015 8:25:28 AM
   - Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy41
   - Originating machine: WN7TED
   - Service machine: WN7TED
   - Not Exposed
   - Provider id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   - Attributes:  Auto_Release Differential

* SNAPSHOT ID = {b4d96234-4a0a-44af-8b3f-a13154d6396c} ...
   - Shadow copy Set: {3ce6cc32-1796-47da-9021-16e456fa97d0}
   - Original count of shadow copies = 3
   - Original Volume name: \\?\Volume{61530745-e66a-11e3-a96b-806e6f6e6963}\ [C:\]
   - Creation Time: 12/7/2015 8:25:28 AM
   - Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy40
   - Originating machine: WN7TED
   - Service machine: WN7TED
   - Not Exposed
   - Provider id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   - Attributes:  Auto_Release Differential

* SNAPSHOT ID = {f07a0f50-7837-4bce-96d8-4f0bfa743a2e} ...
   - Shadow copy Set: {3ce6cc32-1796-47da-9021-16e456fa97d0}
   - Original count of shadow copies = 3
   - Original Volume name: \\?\Volume{61530744-e66a-11e3-a96b-806e6f6e6963}\ []
   - Creation Time: 12/7/2015 8:25:28 AM
   - Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy39
   - Originating machine: WN7TED
   - Service machine: WN7TED
   - Not Exposed
   - Provider id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   - Attributes:  Auto_Release Differential






Tags
Gork
Gork
Guru
Guru (1.3K reputation)Guru (1.3K reputation)Guru (1.3K reputation)Guru (1.3K reputation)Guru (1.3K reputation)Guru (1.3K reputation)Guru (1.3K reputation)Guru (1.3K reputation)Guru (1.3K reputation)Guru (1.3K reputation)
Group: Forum Members
Posts: 629, Visits: 2.5K

I wonder if this advice might help you?
http://support.macrium.com/topic.asp?TOPIC_ID=14531

It also almost seems like we were told to un/reinstall Reflect after an upgrade of the OS to Win10.  I can't find this mentioned though, so I'm not sure.  I do know that we were told we'd have to update our Backup Definition Files when Reflect v6 was released if we wanted to use some of the newer features such as Rapid Delta Restore.  (What a cool name for a feature, btw.)  Though this may not have anything to do with your particular issue, I can say I performed all these operations and haven't seen the problem you're reporting.  Granted, I didn't use an "upgrade" process to Win10 - MS has proven they're not very good at issuing major upgrades.  I installed Win10 fresh.

Just some ideas I suppose.  I don't doubt Macrium will have better advice.


Edited 8 December 2015 8:34 AM by Gork
tfedor
tfedor
New Member
New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)
Group: Forum Members
Posts: 3, Visits: 14
This is an interim report....
Today I was able to execute a successful incremental image.   I turned on file write caching in Advanced -> Advanced Backup Options -> File Write Caching...
I will let the program run a couple of scheduled backups over the next few days before I call this solved...



tfedor
tfedor
New Member
New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)New Member (4 reputation)
Group: Forum Members
Posts: 3, Visits: 14
I was able to take a full and 2 incremental backups after turning write caching on.  However for the past 2 days, I get the error 21 about halfway through the backup.
I have turned on write caching on the drive along with specifying to not flush the windows cache....
This is getting to be a big pain and I may have to find another backup solution for this one computer....
So if anyone else has any suggestions... I'm all ears





Seekforever
Seekforever
Expert
Expert (880 reputation)Expert (880 reputation)Expert (880 reputation)Expert (880 reputation)Expert (880 reputation)Expert (880 reputation)Expert (880 reputation)Expert (880 reputation)Expert (880 reputation)Expert (880 reputation)
Group: Awaiting Activation
Posts: 565, Visits: 10K
Device not ready errors may indicate a hardware malfunction.

Have a look at:  VSS error post  and do have a look at the Windows Events.
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Reading This Topic

Login

Explore
Messages
Mentions
Search