Jump to content

Error 1017 post MS critical update on 2/9/05


rroales

Recommended Posts

Since installing the latest MS "fixes" on 2/9/10, I keep getting tons of error messages that I never got before on both manual and automatic backups: Can't use Open File Backup option for Drive C (C:), error -1017 (insufficient permissions) as well as numerous sharing violation messages. I am using Retrospect 6.5.350.

 

Does anyone else have these errors all of a sudden?

 

Any suggestions?

Link to comment
Share on other sites

Agreed, on an XP SP2 system. I had seen this weeks before (still with Retro 6.5), after the last big Windows Update (on 1/3, mentioned in another forum post) but I had been running error free from 1/25 until 2/9 AM. My changeover from Retrospect 6.5.350 to Retrospect 7.0.249/RDU 7.0.1.103 was on 2/2 with no errors after that, so there was no Retro 7 upgrade problem.

 

However, after the mass WU and reboot on 2/9, the 2/10 AM and every one of the last several nightly backups have shown:

 

==> Can't use Open File Backup option for TheBackup on DRIVE_C (C:), error -1017 (insufficient permissions)

 

along with the subsequent "can't read, error -1020 (sharing violation)" and "Can't access registry for "S-1-5-21-2171835652-3597833224-2385646480-1005", error -1101 (file/directory not found)" errors.

 

The Windows Event Viewer shows corresponding Volume Shadow Copy Service errors of:

 

Event Type: Error

Event Source: VSS

Event Category: None

Event ID: 12289

Date: 2/10/2005

Time: 2:00:47 AM

User: N/A

Computer: ThePC

Description:

Volume Shadow Copy Service error: Unexpected error DeviceIoControl(00000228,0x0053c008,0003A1F0,0,000391E8,4096,[0]). hr = 0x80070057.

 

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Data:

0000: 49 4e 43 49 43 48 4c 48 INCICHLH

0008: 33 36 32 00 00 00 00 00 362.....

0010: 53 50 52 51 53 4e 50 43 SPRQSNPC

0018: 31 36 30 00 00 00 00 00 160.....

 

Clicking on the link in the Event Viewer shows nothing useful ("There is no additional information about this issue in the Error and Event Log Messages or Knowledge Base databases at this time").

Link to comment
Share on other sites

I have been doing some testing. I removed every MS "fix" that was installed on 2/8/05 and restored the machine to the pre "fix" state. I did this fix by fix and ran Retrospect after every reboot. I still got the error messages. I also performed a "repair" to Retrospect with all the fixes removed with the same result.

 

I also removed several .NET "fixes" --- same thing.

 

What I have not done is to remove some Office 2003 fixes that I downloaded that day as well, but I can't see the correlation between Office and the Retrospect issue.

Link to comment
Share on other sites

  • 1 month later...

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...