Error -1017 When Creating DR CD In V6.0 After Driver Rename

[BitPusher]

Before I found out that I need to upgrade to Retrospect Professional V6.5 from V6.0 after upgrading to Windows XP Professional from Home Edition in order to create a usable Disaster Recovery CD, I ran in to an unexpected problem that I would like to know if it exists in Retrospect V6.5, and if so, what is the work-around.

 

After finally getting a successful Windows XP Professional upgrade to work, I took a Full (Recycle) backup of all hard drive partitions and then created the Disaster Recovery ISO image. During this process it never asked to mount any of the media from my backup set. I burned a CD and tested it and got the "Drive A" problem which I later found out is why I need to upgrade to Retrospect V6.5. Before I knew about that problem, I figured I had done something wrong and would repeat the process later.

 

In the meantime, I had problems with one of my software programs because it left several old versions of some of its drivers scattered around on my system. While trying to clean up this mess, I temporarily renamed some drivers in SYSTEM32\DRIVERS\ and then later renamed the correct ones back to their original names and deleted the bad files. While doing that I was signed on with my ID which has administrator privledges.

 

I then revisited the Disaster Recovery CD issue and tried to create a new ISO image, This time it called for me to mount the backup tape for the backup set and shortly after the tape started moving I got this error from Retrospect:

 

+ Executing Prepare for Disaster Recovery at 08/18/2003 18:26

From Backup Set FULLA120-4, Snapshot NTF_WXPRES0 (G:) 08/16/2003 15:10

To CD-ROM image file Restore NTF_WXPRES0.iso...

Can't continue execution, error -1017 (insufficient permissions)

exd2Begin: Coundn't create custom txtsetup file: error -1017 (insufficient permissions).

08/18/2003 18:28:19: Execution incomplete

 

Having to mount the tape and also getting this "permissions" error really surprised me since I was signed on with an ID with administrator privledges. I tried this several times and I happened to notice the name of one of the files I had worked with earlier as the last name that showed up in the Retrospect execution box.

 

I looked in SYSTEM32\DRIVERS\ and I saw that the owner for all of the files except the ones I had previously temporarily had renamed was "Administrators" and the ones I had worked with had the owner being SystemName\MyID.

 

As a result of this problem which I assume is because of the Owner change of these Drivers, I have the following questions:

1. Why did I get the permissions error -1017 when I was logged on with an account with administrator privledges?

2. Will I have this type of problem with Retrospect V6.5?

3. Do I have to logon as "Administrator" and not my "normal" ID with administrative privledges to get around this problem, and if so, what happens if I change the name of the "Administrator" account for security purposes as recommended on page 108 of the Microsoft Press book titled "Microsoft Windows XP Inside Out"?

 

Thank You,

Carl E. Johnson

 

 

[natew]

Carl,

 

Looking at your error message it seems that the error occured when creating a file not reading one. That is indeed strange.

 

Just some basics- make sure you are using the i386 folder from a windows XP install CD when you create the DR image. Try another backup and use the new snapshot for your DR CD.

You should also try this with XP system restore turned off and any virus protection disabled.

 

I don't think this has anything to do with user priveleges - Retrosepct is probably encountering a similar problem and reporting it that way.

Nate

[BitPusher]

Thanks Nate,

 

I was a little bit concerned at the time, that by renaming the driver files, I had created a situation whereby I would not be able to restore my system even without using the Disaster Recovery CD.

 

XP System Restore was on but Norton Auto-Protect was turned off. The only Norton security items in effect at the time were Email Scanning and Script Blocking. However, this was the case for the DR CDs I had created previously with no problem. Also, there was nothing in the Windows XP Event Viewer that showed any type of error at the time, which was a little bit surprising.

 

However, I'm going to upgrade to Retrospect V6.5 so I'm not going to worry about this particular problem now. If I have time, after I've created the DR CDs with V6.5 I'll rename a driver file ( to *.old and then back to its original name) and then just try to create the ISO image without actually burning a new CD. If the problem is still present with V6.5, I'll make a new post.

 

Thank You,

Carl E. Johnson