Registry Problem?

[Johnny Ooi]

Hi, everyone, I've got a problem which may be Windows-
related or hardware-related. The situation is this:

I've got a Proliant server which uses ArcServe 2000 for
backups. Recently, we've had the backup jobs coming back
saying "incomplete". I managed to find out what was
causing this. Two of the keys in the registry were
unaccessible via ArcServe, regedit and RegEdt32. These
keys are

HKLM\System\ControlSet001\Control\ProductOptions

and

HKLM\System\CurrentControlSet\Control\ProductOptions

The error message I get in Regedit is "Cannot open
ProductOptions: Error while opening key"

In Regedt32, it is greyed out and brining up the security
options of the key doesn't help, since it just displays a
window that reads "Unable to display security information".

Does anyone know what I can do to get access to this key
(I'm logged in as administrator on the domain)

Thanks in advance

Johnny

 

[Dave Patrick]

You only need to be concerned with CurrentControlSet. On a Windows 2000
Advanced server the key is set to 'inherit from parent', then ADD

'Everyone', read, this key and subkeys
'Users', read, this key and subkeys
'Power Users', read, this key and subkeys
'Administrators', full control, this key and subkeys
'System', full control, this key and subkeys
'Creator' Owner', full control, subkeys only

 

[Loopy]

I presume you're implying this should be done under regedt32?

Johnny

 

[Dave Patrick]

Yepper

 

[Loopy]

All I get under Permission is a window that says "Cannot display
security settings" and I cannot add or modify any permissions. The
permission on the parent key (Control) are fine and I can access them
with no problems. This is the same for both problem keys.

Johnny

Yepper

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows NT/2000 Operating Systems]

I presume you're implying this should be done under regedt32?

Johnny

 

[Dave Patrick]

Try taking ownership first. You may want to back up the reg before you
continue.

 

[Loopy]

I can't -- taking ownership of keys requires me to access the Permissions
option in the Security menu, and when I do so, I get the "Cannot Display"
error message window.

Johnny

Try taking ownership first. You may want to back up the reg before you
continue.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows NT/2000 Operating Systems]

All I get under Permission is a window that says "Cannot display
security settings" and I cannot add or modify any permissions. The
permission on the parent key (Control) are fine and I can access them
with no problems. This is the same for both problem keys.

Johnny

 

[Dave Patrick]

Let me get this straight. You can't click on the Security|Permissions
without error? If so what is the exact text of the error?

 

[Loopy]

I can open regedt32 with no problem. I can click on
Security=>Permissions no problem, on any other key except for the two
in question, the window that appears is what you would expect,
usernames and permissions, etc.

On the two keys in question, doing this gives you the correct sized
window, but instead of the contents expected, all I get is plastered
in the middle of page, the message "Cannot display security settings".

Regards

Johnny

 

[Ben-Zion Joselson]

Just an idea: Here is an excerpt from MS Article 186374:

"Using the Services tool in Control Panel, start the
Scheduler service and ensure that the Startup settings for
Scheduler allow the service to be started as System.
Open a command prompt and type the following:

at <time> /interactive "regedt32.exe"

where, <time> is replaced with the current time plus about
a minute to take care of your command typing time.
At <time>, Registry Editor (Regedt32.exe) appears on your
desktop. This execution of Regedt32.exe will be running in
the system's security context. As such, it will allow you
access to the entire registry, including SAM and SECURITY
hives. Hence, make changes very carefully. Note that this
will not work against a remote registry; you must do this
locally on the system you want to modify."

 

[Dave Patrick]

You'll need to take ownership first. Don't worry about the message.

 

[Loopy]

I'll give both methods a look when I can. I'll let you know what
happens.

Johnny