Windows Server 2003 Registry Problem

After experiencing problems with modifying the directories selected for
indexing within Windows Search 4 for Windows Server 2003, I attempted an
uninstall, reboot and then re-installed the software. Unfortunately, this did
not solve the problem.

The software was again removed; however, I discovered that after a reboot
the registry key [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
Search\CrawlScopeManager\Windows\SystemIndex\DefaultRules\PresetPoolData] was
still present.

Any attempts to select or delete the key produced the following error:

Error Opening Key

The following solutions/techniques have been investigated but none have
resulted in a solution to delete the key:

- Modifying security permissions/ownership of key;
- Uninstalled McAfee VirusScan Enterprise 8.7;
- Deleting null-embedded key with Sysinternals utility RegDelNull v1.1;
- Deleting key while loading SOFTWARE hive offline within BartPE boot disk;
- Used Windows utility CHKREG to test registry hive files in Windows repair
mode – all hives reported as OK;

Any more suggestions?

 

Do you have a system state backup? You could restore it elsewhere, get the
software hive then replace it via the recovery console.



--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect


"tmr0" wrote:
> After experiencing problems with modifying the directories selected for
> indexing within Windows Search 4 for Windows Server 2003, I attempted an
> uninstall, reboot and then re-installed the software. Unfortunately, this
> did
> not solve the problem.
>
> The software was again removed; however, I discovered that after a reboot
> the registry key [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
> Search\CrawlScopeManager\Windows\SystemIndex\DefaultRules\PresetPoolData]
> was
> still present.
>
> Any attempts to select or delete the key produced the following error:
>
> Error Opening Key
>
> The following solutions/techniques have been investigated but none have
> resulted in a solution to delete the key:
>
> - Modifying security permissions/ownership of key;
> - Uninstalled McAfee VirusScan Enterprise 8.7;
> - Deleting null-embedded key with Sysinternals utility RegDelNull v1.1;
> - Deleting key while loading SOFTWARE hive offline within BartPE boot
> disk;
> - Used Windows utility CHKREG to test registry hive files in Windows
> repair
> mode – all hives reported as OK;
>
> Any more suggestions?

 

Have backups but all have the same problem!

"Dave Patrick" wrote:

> Do you have a system state backup? You could restore it elsewhere, get the
> software hive then replace it via the recovery console.
>
>
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
>
> "tmr0" wrote:
> > After experiencing problems with modifying the directories selected for
> > indexing within Windows Search 4 for Windows Server 2003, I attempted an
> > uninstall, reboot and then re-installed the software. Unfortunately, this
> > did
> > not solve the problem.
> >
> > The software was again removed; however, I discovered that after a reboot
> > the registry key [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
> > Search\CrawlScopeManager\Windows\SystemIndex\DefaultRules\PresetPoolData]
> > was
> > still present.
> >
> > Any attempts to select or delete the key produced the following error:
> >
> > Error Opening Key
> >
> > The following solutions/techniques have been investigated but none have
> > resulted in a solution to delete the key:
> >
> > - Modifying security permissions/ownership of key;
> > - Uninstalled McAfee VirusScan Enterprise 8.7;
> > - Deleting null-embedded key with Sysinternals utility RegDelNull v1.1;
> > - Deleting key while loading SOFTWARE hive offline within BartPE boot
> > disk;
> > - Used Windows utility CHKREG to test registry hive files in Windows
> > repair
> > mode – all hives reported as OK;
> >
> > Any more suggestions?
>
>