Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Win XP Pro registry help


  • Please log in to reply
3 replies to this topic

#1 screamerUSA

screamerUSA

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:03:01 PM

Posted 26 February 2009 - 06:41 AM

I somehow deleted some registry entries while doing some maintenance. I found this out when it was time to "auto copy / update" FD-ISR. I followed the event ID error and found someone who had the exact same problem. I know this because he posted results from command line entries and my results were exactly the same. The thing I don't know is if he was running Win XP or some other platform like Server 2003. In any case the post had a fix via a *.reg file. I would hate to implement this reg fix and go from the frying pan into the fire if it's for another platform and not compatible w/ Win XP Pro.
Is there any way to tell if this reg entry will work?

...screamer

Here's the reg fix:

! REG.EXE VERSION 3.0

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlset\Control\ContentIndex\Catalogs

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlset\Control\ContentIndex\Catalogs\Sy
stem
Location REG_SZ C:\System Volume Information
IsIndexingW3Svc REG_DWORD 0x0
IsIndexingNNTPSvc REG_DWORD 0x0

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlset\Control\ContentIndex\Catalogs\Sy
stem\Properties
A4790B72-7113-4348-97EA-292BBC1F6770 5 REG_SZ 31,500,1,1
A4790B72-7113-4348-97EA-292BBC1F6770 6 REG_SZ 31,500,1,1

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlset\Control\ContentIndex\Catalogs\We
b
Location REG_SZ C:\Inetpub
IsIndexingW3Svc REG_DWORD 0x1
IsIndexingNNTPSvc REG_DWORD 0x0
W3SvcInstance REG_DWORD 0x1
GenerateCharacterization REG_DWORD 0x1
FilterFilesWithUnknownExtensions REG_DWORD 0x0
MaxCharacterization REG_DWORD 0x140

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlset\Control\ContentIndex\Catalogs\We
b\Scopes

c:\inetpub\wwwroot\ REG_SZ ,,3
c:\windows\web\printers\ REG_SZ ,,3
c:\windows\help\iishelp\ REG_SZ ,,3
c:\program files\common files\business
objects\3.0\crystalreportviewers11\ REG_SZ ,,3
Cisco 851 + DIR-655 as Firewall NOD32 2.70 MalwareDefender2.0.5
Life Savers - FD-ISR & ShadowProtect

XPS 600, Pentium D "950" 3.4Ghz, 2GB Ram, 1 TB Seagate Barracuda + 2 160GB Seagate HDD, Dual nVidia GeForce 7800GTX

BC AdBot (Login to Remove)

 


#2 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,277 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:12:01 PM

Posted 26 February 2009 - 07:07 AM

I think I'd try something less dangerous first, like a System Restore.

Start> All Programs> Accessories> System Tools> System Restore.

When this opens make sure that "Restore my computer to an earlier time" is chosen, and click on Next>.
The dates appearing in bold are the dates that you can restore to, click on the date that you want and then click Next> to start the System Restore, you may get the message telling you that you will have to restart your computer to start, click ok. When the computer restarts and you have logged on as the administrator a Restoration Complete page will appear, click on OK to complete the process.

Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#3 screamerUSA

screamerUSA
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:03:01 PM

Posted 26 February 2009 - 11:52 AM

I got this solved. I had to reset the writer states of all the VSS-aware applications. Then there were a few files missing that needed to be replaced & re-registered.

ShadowProtect looks for the VSS in several locations. It successfully accessed the API from STC provider.

btw: the reason I did not do a system restore was that I only keep 2% in Max DiskPercent. That's enough for two restores. One available was today, and obviously that restore was already dirty. And the other was yesterday, and that was the reason I was doing the maintenance in the first place. I normally use FD-ISR and never mess with SysRestore, but w/o VSS FD-ISR will not work. In any case, all's well.

Thanks,

...screamer

...
Cisco 851 + DIR-655 as Firewall NOD32 2.70 MalwareDefender2.0.5
Life Savers - FD-ISR & ShadowProtect

XPS 600, Pentium D "950" 3.4Ghz, 2GB Ram, 1 TB Seagate Barracuda + 2 160GB Seagate HDD, Dual nVidia GeForce 7800GTX

#4 wooGz

wooGz

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:07:01 AM

Posted 27 January 2011 - 02:53 AM

Big Ups for this!
I had this problem plague me for days also..
Netbackup was failing with the following;
Error bpbrm(pid=3728) from client %server%: ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.INF - EXIT STATUS 69: invalid filelist specification

vssadmin list writers returned Error 0x8000ffff
vss error investigation followed the usual ms kb channels.
Reregister dll's, com + errors, even sysvol owner, and local security policy permissions, etc.
None of which actually helped

I was led to this as a result of microsoft documentation documentation telling me to look for the following registry key - which did not exist.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlset\Control\ContentIndex\Catalogs
I exported mine and out of interest googled "A4790B72-7113-4348-97EA-292BBC1F6770 5 REG_SZ 31,500,1,1", (which showed up in my reg export)
And that led me to this post..
That said I'm not sure you that actually deleted these keys, (They were missing on my target machine also - with no possibility of tampering) and its worthwhile checking that they actually exist.
If not the reg file above will do the trick

Coulda saved me days!
Thanks..




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users