Error code 0x8000ffff Failed-Retrying without VSS Writers


Author
Message
IronZorg89
IronZorg89
New Member
New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)
Group: Forum Members
Posts: 7, Visits: 18
I always make a system image backup right after any update and/or upgrade of MR. Just after updating to the latest version V. 7.1.2614 today, I had this error code (Failed-0x8000ffff-retrying without VSS writers) which I have never seen before. It appeared on both of my PCs, but didn't prevent the backup to go to full completion. I was wondering if that was caused by the update, and if so, how do I fix it?. Any help from a moderator or any other member of this forum, who has experienced the same issue, would be really appreciated. Please, see also the seen screenshot attached.

Attachments
MR Error Code 0x8000ffff.JPG (4 views, 86.00 KB)
jphughan
jphughan
Most Valuable Professional
Most Valuable Professional (3.1K reputation)Most Valuable Professional (3.1K reputation)Most Valuable Professional (3.1K reputation)Most Valuable Professional (3.1K reputation)Most Valuable Professional (3.1K reputation)Most Valuable Professional (3.1K reputation)Most Valuable Professional (3.1K reputation)Most Valuable Professional (3.1K reputation)Most Valuable Professional (3.1K reputation)
Group: Forum Members
Posts: 2.2K, Visits: 14K
Have you tried just restarting the PC and reattempting the image?  I have some issues creating a viBoot VM but they went away that way and have not returned after numerous tests.  Also, you posted this in the V6 section, not V7.  And just for future reference, if you use the Insert Image feature rather than Add File, images you upload will display embedded in the post.

Edited 29 September 2017 10:00 PM by jphughan
IronZorg89
IronZorg89
New Member
New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)
Group: Forum Members
Posts: 7, Visits: 18
jphughan - 29 September 2017 9:57 PM
Have you tried just restarting the PC and reattempting the image?  I have some issues creating a viBoot VM but they went away that way and have not returned after numerous tests.  Also, you posted this in the V6 section, not V7.  And just for future reference, if you use the Insert Image feature rather than Add File, images you upload will display embedded in the post.

I haven't tried reattempting the image yet. From the time of my first post to now, the PC has been restarted many times already. So, I will just tried to make another system image backup to see what gives, and I will post back. Now, with regard to the viBoot VM, I remember during installation of the latest version, there was a window where one was asked to check the features to install. There were four of them already pre-checked except one regarding exactly the viBoot VM. It was unticked and I left it just like that. I don't know if that could be the cause of the error.

jphughan
jphughan
Most Valuable Professional
Most Valuable Professional (3.1K reputation)Most Valuable Professional (3.1K reputation)Most Valuable Professional (3.1K reputation)Most Valuable Professional (3.1K reputation)Most Valuable Professional (3.1K reputation)Most Valuable Professional (3.1K reputation)Most Valuable Professional (3.1K reputation)Most Valuable Professional (3.1K reputation)Most Valuable Professional (3.1K reputation)
Group: Forum Members
Posts: 2.2K, Visits: 14K
Interesting. Everything was checked when I ran the update, although maybe that’s because I already had viBoot and CBT, and MIG was of course new. Anyhow, I haven’t been able to reproduce the error I saw the first two times, even though I’ve tried several more times since then, so I’m not too worried about it.
Edited 30 September 2017 11:24 PM by jphughan
IronZorg89
IronZorg89
New Member
New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)New Member (31 reputation)
Group: Forum Members
Posts: 7, Visits: 18
jphughan - 30 September 2017 11:23 PM
Interesting. Everything was checked when I ran the update, although maybe that’s because I already had viBoot and CBT, and MIG was of course new. Anyhow, I haven’t been able to reproduce the error I saw the first two times, even though I’ve tried several more times since then, so I’m not too worried about it.

Living up to my commitment, I have just finished doing another system image backup. This time around, the error was no where to be seen (See attachment: screenshot). So according to your advice, it's a good thing to always restart the computer after an update/upgrade before making a system image backup. I'll keep that in mind. So, everything seems to be back to normal and I am not worrying anymore about it. Thanks a lot for taking the time to answer to my query.
As far as I am concerned, this case has been resolved and this thread can be closed. Smile



Attachments
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search