Salta al contenuto principale

Error writing to the output stream 0x580002

Thread needs solution

Can some kind person tell me what to make of this error message?

I have been backing up an Outlook Express email store (XP SP3) for about 5 months without a problem. Now I get the following error:

Error occurred while backing up. (0x40019)
Tag = 0xCE542E14DA203B82
Error writing to the output stream (0x580002)
Tag = 0x87D36265AB4AEF22

The backup is to a USB HDD. At this point, I can't backup to any drive, fixed or USB without this error.

My other backup to a NAS works.

There is no documentation in the KB of this error code, so I would appreciate it if anyone can tell me what it means.

0 Users found this helpful

What version Windows are you using? Have you updated any drivers lately? Microsoft issued some updates recently, did your errors start occurring after these updates if you recall?

I would try the following

With PC shutdown, unplug all USB devices except keyboard mouse, start PC and after boot reattach each USB device one at a time. Watch for any device that indicates it is being installed. If you see this wait for installation to complete before attaching additional devices. After all USB devices are reattached try your backup again.

If that fails, check for driver updates for all attached devices you have installed including video, network, storage, chipset drivers. Your error code 0x40019 indicates a possible out of date driver error.

I'm using Windows XP SP3.

Thank you for the recommendations.

I followed your suggestions regarding removing all of the USB devices and letting them reinstall, but to no avail. I also tried to update drivers in Device Manager for the disk drives and controller, but none reports a better driver. I am getting this error now regardless of whether I try to backup to an internal or USB drive.

I had run Windows Update before the problem began, but only installed security updates.

I noticed that each disk drives shows two Acronis drivers in addition to two Microsoft ones, if that makes any difference.

fltsrv.sys 1.2.0.2133 Copyright Acronic International GmbH Not Signed

vidsflt.sys 1.1.0.2105 Copyright Acronic International GmbH Not Signed

Now I have no idea what else to do.

One more piece of information -

The failing backup is the Outlook Express email store.

The mail store now resides on the system drive.

Currently, the drive itself is reliably backed up to NAS using Acronis, while the email backup fails every time with the "output stream" error message.

In other words, there are two backup jobs, both involving teh system (C:) drive-

  • 1.  The entire drive, daily
  • 2.  The Outlook Express email store, every 2 hours

Both are set to back up to a Synology NAS.

The full-drive backup works, the email store doesn't.

If it is a driver issue, I don't see why it would only affect the mail store and not the backup of the drive itself.

Other XP machines on my home network are able to back up the Outlook Express store to NAS using Acronis.

Just a few ideas, You say that other XP machines on your home network can backup outlook express fine while yours cannot, how many machines are connected in the network? I am assuming that your NAS is connected to the network via USB? If so, are you using a Hub for the connections and if so did you unplug the usb from your machine on the machine side or the hub side when you trued my suggestion? Are you backing up to individual folders on the NAS? If so are there size limits for these folders? Often cannot write to output stream errors result when destination is nearing full capacity.

I agree that it is strange that you can backup the system drive just not the email. You might try deleting your current backup task for the email and recreate it and see if that would correct the problem. If you try this I would recommend that after you delete the task that you close the TI app and shutdown (system off) your machine then restart, reopen TI and then create the new task. It may also be of benefit to compare the task configurations between your machine and another on the network that is known working and see if both tasks are setup the same.

It is possible that you have some errors in this machines registry that are the cause of this issue.