Jump to content
Sign in to follow this  
sstevens

Error 1101 Can't Access Registry - aspnet

Recommended Posts

Please help! I'm getting only 1 error when I backup but I get this error on every server. The error is referring to the local account on each machine of "ASPNET". The error is:

 

Can't access registry for "S-1-5-21-448539723-884357618-839522115-1003", error -1101 (file/directory not found)

 

What do I need to do for this error to go away? Thanks so much!

 

Sean Stevens

Share this post


Link to post
Share on other sites

One possible cause is that the customer deleted a user previously. The above S-xxxxxxx could be any routine of numbers.

Here are the steps to fix this error so that Retrospect will not report these errors on these missing registry files.

 

1) Note the user number or a large part of it out of the log.

(Example: "1275210071-1682526488-1343024091-1003").

 

2) Open regedit.

 

3) Navigate to:

 

My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows

NT\CurrentVersion\ProfileList\

 

4) Click on the user ID. Note the name of the user that this entry refers to

in the info on the right in regedit.

 

5) If indeed this user is not currently on this computer, then delete the

item under ProfileList.

 

Retrospect will no longer complain about the missing registry files.

 

If you can confirm that the user has been deleted from the

computer, then deleting the item is the correct step to ta k e. Confirm this

by doing the following:

 

1) Check the registry, as detailed above, then see the name which this

profile refers to.

 

2) If the Admin thinks this user shouldn't exist on the computer, then close

RegEdit.

 

3) Open the User Manager and make sure they don't exist there; if they do,

delete them.

 

4) Go back to RegEdit, and see if that profile still exists. If it does,

then delete it.

 

Thanks.

Share this post


Link to post
Share on other sites

I've found that I get this message when backing up machines that have been migrated from a dead Domain Controller to a whole new domain and PDC. It is those abandoned accounts and registry entries that need to be deleted after a migration to make Retrospect not complain, at least in my case. I'm sure there are other things that can cause this, but this has been my experience. I don't get this kind of message for local user accounts or accounts associated with the current PDC.

 

I'm not sure why Retrospect chokes on these accounts, I just know that even though it complains it seems like the backups are still completing successfully.

Share this post


Link to post
Share on other sites

Hi

 

Quote:

I'm not sure why Retrospect chokes on these accounts, I just know that even though it complains it seems like the backups are still completing successfully.

 


 

This happens because portions of the user accounts are referenced in the registry. Retrospect follows those references to try to backup user information but the information has already been deleted. Hence the file not found error.

 

Thanks

Nate

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×