15 Replies Latest reply on Jan 12, 2015 3:36 PM by Lester Grant

    SEUM-User-# using up disk space

    Fred Lipton

      I've got three players spun up on Amazon with modest but sufficient resources to do the job.  So far I've got 6 monitors assigned to each player.  I've noticed that the seum-user-# subdirectories grow larger than the cache settings allow in the browser settings which suggests the cause is not temporary IE files.  More than once they've consumed nearly the entire disk space.  The culprit folder appears to be C:\users\seum-user-#\appdata\local\microsoft\windows but the contents of that folder do not add up to what the file browser says should be in there [with the hidden file attribute set to display].  The first couple of seum-users seem to be the bigger disk-hogs.


      It's a relatively vanilla set up.  Amazon provides Win08R2 plain Jane instances, I've added only the Player executable.


      I've read other threads where it was suggested to stop the player service and delete the accounts or delete the temporary files folder [which doesn't appear to be the problem folder].  The better solution is to not have these user account folders over-grow their banks at all.  I'm not the OS maven I hoped to be and looking for advice/clues/commiseration.



        • Re: SEUM-User-# using up disk space

          Hello Fred,

          mentioned folder "C:\users\seum-user-#\appdata\local\microsoft\windows" and especially its subfolder "WER" is used to store application crash report when any application crashes. If this folder grows for SEUM users, it probably means that WPM player processes are crashing. We've seen some websites that were able to crash the process by using an ActiveX component that does not work under WPM process.

          Can you please open a support ticket so that we can look what is happening with your installations?


          You can also disable Windows Error Reporting that is responsible for this growing folder. Here are some ways how to do that: Disable WER on Windows - My IT projects or How to disable Windows Error Reporting - 4sysops

            • Re: SEUM-User-# using up disk space
              Fred Lipton

              Hi jiri.tomek;


              When you mentioned the WER folder I perked up because I noticed that one but didn't have a clue what it was for.  Looking in the user subdirs today there's a folder I didn't notice yesterday,C:\users\seum-user-1\appdata\local\microsoft\windows\WebCache which is over 1GB mostly in one file: WEbCacheV01.dat.  Similar files/folders in other seum-user subdirectories.


              IE settings for data is limited to 250MB which doesn't jive with that 1GB .dat file so I'm missing something.


              Do you still recommend opening a support ticket?  I'm willing.  Thnx...Fred

                • Re: SEUM-User-# using up disk space

                  I am also starting to have this happen with the WEbCacheV01.dat file.  I stopped all services and deleted the profiles and restarted them, I am waiting to see if it comes back.  I am interested to see what happens with this, let us know if you find anything - if mine comes back, I'll post anything I find.

                  • Re: SEUM-User-# using up disk space

                    I've been dealing with this since updating to IE10.   I've tried adjusting the Internet Explorer settings to limit the size of this file but hadn't had any luck.   In normal use this wouldn't be a problem, since in most cases, you have one user on a box and one webcache file, so a few gig isn't that big of a deal.  But with WPM and 8 or so users all creating these files, it becomes a problem.  My default NT verts only have 15GB available after the OS and app is installed.  My only solution so far has been to create a powershell script that stops the player service at night, deletes the webcache files for each WPM user and then restarts the player process.   I also have it clean up the WPM log directory at the same time.  I'm spend most of my time in Unix and had no powershell experience, but would be happy to share what I have so far (and would certainly appreciate any suggested improvements)...



                    script so far...


                    Stop-Service -displayname "SolarWinds WPM Playback Player"

                    Start-Sleep -s 10

                    Stop-Process -Name dllhost* -Force

                    Start-Sleep -s 10

                    If (Test-Path C:\Users\SEUM-User-1\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.dat) {

                      Remove-Item C:\Users\SEUM-User-1\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.dat


                    If (Test-Path C:\Users\SEUM-User-2\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.dat) {

                      Remove-Item C:\Users\SEUM-User-2\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.dat


                    If (Test-Path C:\Users\SEUM-User-3\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.dat) {

                      Remove-Item C:\Users\SEUM-User-3\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.dat


                    If (Test-Path C:\Users\SEUM-User-4\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.dat) {

                      Remove-Item C:\Users\SEUM-User-4\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.dat


                    If (Test-Path C:\Users\SEUM-User-5\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.dat) {

                      Remove-Item C:\Users\SEUM-User-5\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.dat


                    If (Test-Path C:\Users\SEUM-User-6\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.dat) {

                      Remove-Item C:\Users\SEUM-User-6\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.dat


                    If (Test-Path C:\Users\SEUM-User-7\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.dat) {

                      Remove-Item C:\Users\SEUM-User-7\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.dat


                    If (Test-Path C:\Users\SEUM-User-8\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.dat) {

                      Remove-Item C:\Users\SEUM-User-8\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.dat


                    Remove-Item C:\ProgramData\SolarWinds\Logs\SEUM\AgentWorker_*.log

                    Start-Service -displayname "SolarWinds WPM Playback Player"

                      • Re: SEUM-User-# using up disk space

                        you can also edit c:\Program Files (x86)\SolarWinds\Orion\SEUM\Player\SolarWinds.SEUM.Agent.Service.exe.config and change numWorkerProcesses to lower the number of profiles it creates.

                          • Re: SEUM-User-# using up disk space
                            Fred Lipton

                            romeyde and netlogix: interesting approaches and they both could be helpful, short-term fixes but they seem like band-aids.  This is a simple set up [Windows boxes with no other tasks to perform] and ought to work without having to frequently ride herd on these player PCs, taking them off-line every night [albeit briefly] or compromise their performance by restricting processes.


                            Here's another option that occurred to me that may want to consider: disk quotas; set and forget.  I don't know what the effect will be when an seum-user-# object hit that mark.  Will it stop working?  Hose up the computer?


                            The search for a solution continues....

                              • Re: SEUM-User-# using up disk space
                                Fred Lipton

                                I opened a support ticket and got this advice which does have a positive effect on the issue: reduce the history days saved from the default of 20.  I chose 2 days and let it run for more than a few days.  Each SEUM-User-# object uses about half to two-thirds than previously and appears to be stable.  I'd call this a solution as it appears long lasting and doesn't require scheduled tasks or scripted processes to run.


                                On a side note, these instances are running IE10.  To maintain compatibility with the monitored websites at least one of the three players we've spun up has been downgraded to IE8, which may open a completely different can of worms.  Or not.  We'll see and I'll post my findings.

                      • Re: SEUM-User-# using up disk space

                        I went ahead and paid to opened a support case with Microsoft to try to work on this issue (as the issue is essentially the lack of ability to control the size of this WebCacheV01.dat file). They basically told me that there is absolutely no way to control the size of this cache. You'd think that they would provide a way to control this via a local policy or at least in IE being that Microsoft is all about granular control in products such as Group Policy.


                        I ended up coming up with a solution that works pretty well. If you deny each user permissions to their own Webcache folder, the browser simply doesn't write to cache. I left the player running like this with 250+ transactions for a few weeks without any trouble (transactions going unknown, etc). All you need to do is run the below script once after the player builds all user accounts. This way you don't need to keep running scripts to clean the cache.


                        icacls "C:\Users\SEUM-User-1\appdata\Local\Microsoft\Windows\WebCache" /deny "SEUM-User-1":(f) /t /c

                        icacls "C:\Users\SEUM-User-2\appdata\Local\Microsoft\Windows\WebCache" /deny "SEUM-User-2":(f) /t /c

                        icacls "C:\Users\SEUM-User-3\appdata\Local\Microsoft\Windows\WebCache" /deny "SEUM-User-3":(f) /t /c

                        icacls "C:\Users\SEUM-User-4\appdata\Local\Microsoft\Windows\WebCache" /deny "SEUM-User-4":(f) /t /c

                        icacls "C:\Users\SEUM-User-5\appdata\Local\Microsoft\Windows\WebCache" /deny "SEUM-User-5":(f) /t /c

                        icacls "C:\Users\SEUM-User-6\appdata\Local\Microsoft\Windows\WebCache" /deny "SEUM-User-6":(f) /t /c

                        icacls "C:\Users\SEUM-User-7\appdata\Local\Microsoft\Windows\WebCache" /deny "SEUM-User-7":(f) /t /c


                        Hopefully this can be of use.





                          • Re: SEUM-User-# using up disk space

                            Here is the solution I implemented after the SEUM-User-# profiles filled my disk space twice (3 months apart), delete the profiles weekly. The profiles are automatically re-created when the transaction is played and unmanaging your WPM transactions is optional.


                            Schedule the following 2 tasks in Windows Task Manager:

                            • Unmanage WPM Transactions - Sunday from 4:55am - 5:10am
                            • Run the following PowerShell Script - Sunday at 5:00am


                            # Delete_WPM_SEUM_Profiles.PS1

                            # 07/17/2014 Mark Tellier

                            # WPM SEUM profiles will grow until all disk space is consumed

                            # Schedule PowerShell to run once per week to delete profiles

                            # This script runs in parallel across all players defined


                            # Define all players here

                            $wpmPlayer = @("wpm-play1", "wpm-play2", "wpm-play3")


                            # Stop WPM Service

                            icm -cn $wpmPlayer -ScriptBlock {Stop-Service "SWSEUMAgentSvc"}

                            icm -cn $wpmPlayer -ScriptBlock {

                                # Delete WPM Profiles - SECU-User#

                                $Profiles = Get-WMIObject -Class Win32_UserProfile | Where-Object {$_.LocalPath -like 'C:\Users\SEUM*'}

                                ForEach($p in $Profiles){





                            # Start WPM Service 

                            icm -cn $wpmPlayer -ScriptBlock {Start-Service "SWSEUMAgentSvc"}



                            Hope this helps,



                          • Re: SEUM-User-# using up disk space



                            Has this issue been resolved in the latest WPM?