Solved

wrdata folder



Show first post

88 replies

Userlevel 7
Open WSA > System Tools > Reports > Clear Log.
Userlevel 7
Badge +55
That is correct you can't delete anything in that folder the only way for now is to do a clean reinstall to clean it up, hopefully they will have a better solution in time!
 
TH
Userlevel 7

@TripleHelix wrote:

@Baldrick wrote:
Hi Brad
 
I am looking forward to it.
 
Regards, Baldrick

Sorry but I have no interest with his cleanup tool and you know me I'm a realist and Brad could be breaking Webroot's EULA in some way and would not recommend anyone to use his tool if it ever comes to be and @nic should check with the internal staff on this @BradW @Shawn. Also we know it's on the Webroot's Developers list to make WSA clean it's own old files.
 
Just my opinion,
 
Daniel

You make some valid and relevant points there Daniel, and it's difficult to envisage how Webroot could do other than advise against its usage.
 
Userlevel 7
Badge +56
Brad has reached out to me, and I will take his utility and run it by the folks here.  We actually have lots of folks on our support team who do similar workaround utilities to fix issues, and they sometimes get incorporated in the product.  So who knows - maybe we'll end up doing the same with your utility Brad!
Userlevel 2
Well after much coding and finger crossing, I have a utility:
 


 
And more importantly, I have 185 GB of unwanted dbNNN.db files in my Recycle bin :)
 


 
...and WebRoot came back up without any errors.
 
I need to put a few finishing touches on the util (along with a short write-up); if anybody is intereseted, I'll put it up for download in a day or so.
Userlevel 2
I'd be happy to let you check it out in a couple of days; however, I just ran it on my Windows 7 test machine and found a couple of bugs:
  • It didn't handle a network file path correctly (i.e. "\WIN8BOXShareScadaPhoneInstall.exe"); When the exclude list contained a network path, my app would not delete anything; when I removed the \WIN8BOX items from the list of excluded folders, it worked.
  • After running this on my Windows 7 test computer and finishing a long sequence of db file recycling, my app coughed-up an "out of memory" error and subsequently saved the WRLog.log as a file of zero bytes (oops).
I made backups when I ran it on my primary machine (no probs there), but I did not make backups on my Win7 test machine... So now I have no historic WRLog.log file data from which I can make the EXE to NNNN association (without being able to decode the db file).
Userlevel 2
P.S. This utility is really targeted for programmers who have massive amounts of data accumulating in the WRData folder due to repetitive creation of EXE files (every time we compile a new version of our software). General-purpose users will not really need this, but on my system, the dbNNNN.db files were taking up nearly 20% of my 1TB drive.
 
I intend to continue using WSA, so this will be an ongoing issue for me. That's why I'm doing this.
Userlevel 2
Badge +3
Ok ,,last post on this subject,,,
 
I asked support about uninstalling and reinstalling the software to get rid of the bloat,,,,This is the last answer I got from webroot tech.
 
 
 
Yes if you reintsall the software the folder gets replaced, but do not do anything to the actual folder unless we tell you to as you will break the Webroot software. Please reinstall and let me know if that helps.

Thanks,
Webroot Support Team
 
Snake
Userlevel 2
Badge +3
Hi,,
Its been awhile since I posted, but I have learned not to reinstall or install over the top of a beta program,,,simply check for updates and let the program update itself. This will not increase the siae of the wrdata foldeer contents.
snake
Userlevel 7

@TripleHelix wrote:
Hi snake,
 
Sorry ProTruckDriver that will not decrease the info in that folder the only thing that you can do is uninstall WSA reboot and install again because if you just delete the files it could cause issues with WSA!
 
HTH,
 
TH

Misunderstood the question. I thought snake was talking about just clearing the logs of WSA. Sorry. :$
Userlevel 7
Badge +55
Hi snake,
 
Sorry ProTruckDriver that will not decrease the info in that folder the only thing that you can do is uninstall WSA reboot and install again because if you just delete the files it could cause issues with WSA!
 
HTH,
 
TH
Userlevel 7
Badge +55
Not a problem buddy! :D I know as my WRData Folder is 89MB ATM and I don't have that many U related files in my scan log!
 
TH
Userlevel 7
Badge +55
Hi snake please let us know how it goes!
 
Thanks,
 
TH
Userlevel 7
Badge +55
Again the best thing to do is Unistall WSA reboot and install again to clean up WRData Folder! Make sure you have a copy of your license before doing so!
 
Cheers,
 
TH
Userlevel 7
Badge +55
There's been a discussion about it here: http://www.wilderssecurity.com/showthread.php?t=305319 just to let you know your not alone!
 
TH
Userlevel 7
Badge +55

@vango44 wrote:
My WRData folder is now over 3GB!!
 
Almost all of the bulk is in "dbxxxx.db" files.
The largest is 1.5GB
If it helps, ALL these dbxxxx.db files are "blue" in windows explorer (compressed?)
All the other files are "black"
 
This is on SecureAnywhere Antivirus but this topic looks active here so I posted here.
 
Is a re-install the only way to solve this issue?
 
vango44
 

The best thing for now is to do a clean reinstall! Uninstall reboot and reinstall and make sure you have a copy of your license key! Here is the link to download a copy of WSA http://anywhere.webrootcloudav.com/zerol/wsainstall.exe  If you find it getting big again then it would be best to contact the WSA support inbox and they will be happy to help you: Submit a Support Ticket
 
HTH,
 
TH
 
EDIT: And welcome to the Webroot Community Forums!

Userlevel 7
Have scanned my machine and can find no trace of a folder called "wrdata".  Is this normal?  Should I be concerned?  WRSAE is working perfectly...as far as I can see.
 
:S
 
EDIT:  FOUND IT...it was lurking but I couldn't see! :$
Userlevel 7
Uninstalled & then reinstalled WRSAE and that seems to have sorted out the issue as has been advised both here & at Wilders. :D
 
Small tip, if not already mentioned elsewhere; export settings BEFORE uninstall and then import them back AFTER reinstall.  Has no effect on wrdata folder size and saves you a lot of time trying to remember & returning the settings to as they were (and how you liked them). ;)
 
Balders
Userlevel 7
Hi snake
 
No problem.  We must trust in Joe (PrevxHelp) & his team to resolve the issue.  They always have and I am sure that if there is a way for them to do so without compromising WRSA's effectiveness, etc., then they will. :D
 
Balders
Userlevel 7
Hi nebula
 
I have posted this before but cannot find the thread to direct you to so I will repost the information here.
 
If you are technical (and I believe that you are) then are there are other ways that avoids the uninstall/reinstall, which involves the review of the 'dbnnnn.db files in the C:ProgramdataWRDATA folder, and then the deletion of selected ones of this file type. But I should stress at the outset that you need to be careful when employing these approaches.
 
The first is not ideal but it does avoid the uninstall/reinstall and also preserves to some extent the rationale for those files; as you may have surmised from the thread these files are the journal files produced when WSA sets a file/app to 'Monitor' and so are important in case WSA has detected a suspicious or an as yet undetermined (in terms of goodness/badness) file/app and then determines it is bad and then needs to roll back its activities, etc., in which case the relevant 'dbnnnn.db' file is required.
 
The problem is that we cannot easily tell which 'dbnnnn.db' relates to which file/app in the system (there is a way by looking in the Registry but I have lost my notes on that...must try to find them) so the best thing to do is to (i) check all places in WSA where files could be set to 'Monitor', decide whether they are OK or not (and if in doubt leave them as such), (ii) try to work out roughly when a file/app that is set to 'Monitor' was so set & (iii) then go to the C:ProgramdataWRDATA folder and carefully delete all 'dbnnnn.db' files that are either prior to a certain period, i.e., say more than 2 weeks old, on the basis that WSA should have been in a position to sort out if the journal is required or not, or delete everything except for the 'dbnnnn.db' files that are circa the dates that you believe that you 'Monitored' files/apps may have started to be monitored, etc.
 
The above may seem more convoluted that an uninstall/reinstall, but I have found that it seems to work well, and does give you a better chance of keeping 'dbnnnn.db' files that may be needed; after all an uninstall/reinstall should clear all the files in that folder regardless of whether they are needed or not.
 
A second, alternative way which may be more accurate but takes longer is to run Save a Scan Log and from the text file produced do a search for ‘(nnnn)’ (without the ‘’ marks) where ‘nnnn’ is the ‘nnnn’ portion of the ‘dbnnnn.db’ file(s) found in the C:ProgramdataWRDATA folder.  This should find an entry in the Log from which you can identify the application/file that is being monitored and to which the journal file concerned belongs;
 
Sat 12-09-2015 10:21:40.0098         Monitoring process C:BrowsersMaxthonPortableBinMaxthon.exe [63D4BC1DABF35B13C94A9FAE02D7C0FF]. Type: 3 (1235)
 
relates to file ‘db1235.db in the C:ProgramdataWRDATA folder.
 
Of course, this is not ideal in terms of dealing with many ‘dbnnnn.db’ files but if one can identify the largest of these files and start with those then one can reduce (safely) the size of the folder.
 
Hope that helps you with your space issue and the size of your WRData folder.
 
Regards, Baldrick
Userlevel 7
Hi Nebula
 
Completely understand where you are coming from. Hopefully things will improve in that area in the future as I believe that the Development Team are looking at this whole area.
 
I try to temper things by remembering that the .db files in the WRData folder forma a valuable part of the insurance that WSA provides should an unknown fiel/app be found on your system and then prove to be malicious. ;)
 
Regards, Baldrick
 
 
Userlevel 7
Obviously I land with TH on this.. but all is good as long as given an "OK" after being reviewed.  As for becoming a part of the product... that would be... pretty doggone cool if it works well and is polished enough to not remove rollback data that is still needed!
 
 :)
Userlevel 2
I think the observation about new apps causing the extreme growth of the WRData folder is correct... I'm a (really busy) programmer, and my WRData folder contains 189 GB... Oddly, the Size On Disk is 177 GB (I guess that's the compression).
 


 
I'm going to try that uninstall/reinstall suggestion, but it sure would be nice to be able to clear this in a more civilized manner.
Userlevel 2
I had a look in the WRLog.log and saw that the bulk of the activity is centered around the repeatedly changing EXE files in my working folders (every time I compile a new EXE, more activity). 
 
The perfect solution to this problem would be to allow me to specify my working folder tree to be off-limits to WSA scans; I never install 3rd party software into my working folder tree and some days I recompile my apps dozens of times.
 
Is there a way to specify an off-limits folder?
 
Thanks
Userlevel 2
I think I see what I need to do; I'm going to write a clean-up app to automate this process.
 
Let me know if you think the following steps sound OK:
 
  1. Load the WRLog.log file
  2. Scan for all of the 'Monitoring process' lines
  3. Extract the EXE path and (NNNN) information into a data table
  4. Compare EXE path info to Off-Limits-Folder list (to build list of NNNNs to delete)
  5. Delete all dbNNNN.db files in deletion list.
 

Reply

    Cookie policy

    We use cookies to enhance and personalize your experience. If you accept or continue browsing you agree to our cookie policy. Learn more about our cookies.

    Accept cookies Cookie settings