Skip to main content

Hi.

We have several windows  servers with a lot of big dump files in a universe subfolder called "minidump".

Is there a way to avoid  this kind of dumps, in order to prevent disk filling?

Thanks in advance.

p.d.

A sample from eventlog:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

- <System>

  <Provider Name="UniVerse" />

  <EventID Qualifiers="49152">1004</EventID>

  <Level>2</Level>

  <Task>0</Task>

  <Keywords>0x80000000000000</Keywords>

  <TimeCreated SystemTime="2021-02-12T03:35:21.000000000Z" />

  <EventRecordID>11202874</EventRecordID>

  <Channel>UniVerse</Channel>

  <Computer>XXXXXXXXXXX</Computer>

  <Security />

  </System>

- <EventData>

  <Data>Unhandled Exception raised at address 0xD43953DF : Access violation. Attempted to read from address 0x81567BA0. Exception file: c:UVUVminidumpexception_33900_0212_033521.txt Min dump file: c:UVUVminidumpu2dump_33900_0212_033521.dmp</Data>

Regards.

--

Augusto Alonso

Hi.

We have several windows  servers with a lot of big dump files in a universe subfolder called "minidump".

Is there a way to avoid  this kind of dumps, in order to prevent disk filling?

Thanks in advance.

p.d.

A sample from eventlog:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

- <System>

  <Provider Name="UniVerse" />

  <EventID Qualifiers="49152">1004</EventID>

  <Level>2</Level>

  <Task>0</Task>

  <Keywords>0x80000000000000</Keywords>

  <TimeCreated SystemTime="2021-02-12T03:35:21.000000000Z" />

  <EventRecordID>11202874</EventRecordID>

  <Channel>UniVerse</Channel>

  <Computer>XXXXXXXXXXX</Computer>

  <Security />

  </System>

- <EventData>

  <Data>Unhandled Exception raised at address 0xD43953DF : Access violation. Attempted to read from address 0x81567BA0. Exception file: c:UVUVminidumpexception_33900_0212_033521.txt Min dump file: c:UVUVminidumpu2dump_33900_0212_033521.dmp</Data>

Regards.

--

Augusto Alonso

Augusto,

I suggest setting up a Windows task scheduler job to purge older files - e.g. over 2 weeks. It would be worth however digging into why these are happening and purge any old files. Once a few new files have appeared, run a 'uvdiag' as soon as a few new ones have appeared and open a  Support ticket,

  1. Open task scheduler.
  2. Click on “Create Basic Task.”
  3. Name the new task - e.g. 'Purge old UniVerse minidumps'
  4. Click “Next”.
  5. Select a trigger.
  6. Configure selected trigger.
  7. Select “Start a program.”
  8. Type “powershell” in the Program/Script field.
  9. Paste the below command in the “Add arguments” field. Replace the folder path and number of days with local options..
    -Command "Get-ChildItem -Path 'c:u2uvminidumps' -File -Recurse -Force | Where-Object {($_.LastWriteTime -lt (Get-Date).AddDays(-14))}| Remove-Item -Force"
  10. Click “Next”.
  11. Click “Finish”.
Adjust the path (c:u2uvminidumps) and the age (14 days) to match your requirements. I set my example to run weekly at Friday at 16:00 for example, though the trigger can be anything as can the frequency.  I also set the task properties to 'Run whether the user is logged on or not' and to run 'Hidden' so as to perform the task regardless of whether I am present and to avoid a pop-up powershell window on the console as it executes.

The task can be tested immediately using 'Run now' in the task scheduler.
​
Terms & ConditionsAccessibility statement