dfmpurge on Windows generates runtime error BEX64

[WAFLHERDER]

Hi All,

I would like to clean up old events on an OCUMC / DFM version 5.1 server. I thought to use the dfmpurge utility, but at runtime it generates a Windows system error "BEX64".

According to some random technet link, BEX64 indicates a buffer overflow (/GS) or DEP exception on 64-bit versions of Windows.

The platform here is Windows 2008 R2 SP1 64 bit. The executable being run was downloaded as / extracted from a file called: dfmpurge_dfm-5.1x_windows_64.zip

The executable itself, dfmpurge.exe, has a size of some 31.5MB. Can that be correct?

Has anyone else experienced this problem, or has anyone any suggestions?

Thanks in advance!

Robb.

Problem signature:

  Problem Event Name:     BEX64

  Application Name:     dfmpurge.exe

  Application Version:     5.1.0.15008

  Application Timestamp:     50948889

  Fault Module Name:     MSVCR80.dll

  Fault Module Version:     8.0.50727.6195

  Fault Module Timestamp:     4dcdd833

  Exception Offset:     000000000003441c

  Exception Code:     c000000d

  Exception Data:     0000000000000000

  OS Version:     6.1.7601.2.1.0.274.10

  Locale ID:     1031

[adaikkap]

Hi Rob,

        All of the functionality and much more  of dfmpurge tool is already part of OCUM 5.2 which happens every-time during upgrade and restore of a db in 5.2 and later.

Regards

adai

[WAFLHERDER]

If only I was running 5.2 rather than 5.1!

Yours,

Robb.

[CASTROJSEC]

I am using 5.2.0.16214 (5.2RC1) but the dfm purge events -S Information does not seem to be working.  I've noticed that some of the other commands are not working as well.  Am I missing something?

[adaikkap]

Hi James,

     The clis mandatory parameter is the purge-interval

I was able to run the cli in 5.2 with out any issue.

The -s does the following "Shows the details of the events, without cleaning up them from DB"

C:\>dfm purge event -S Information -s 5d

Hisotry Event Counts

Event Type                   Count

cpu.load                     32

resource-group.modified      32

volume.growthrate            23

host.snmp_status             9

df.snapshot.kbytes           8

data-export                  5

df.kbytes                    4

host.nfs_service_status      4

traplistener-start           3

df.inodes                    2

respool.space                2

status.global                2

dfm.load                     1

qtree.kbytes                 1

dfm.free.space               1

disk.reconstruct             1

dfm.license.limit            1

volume.overcommit            1

database_backup.status       1

dfm.license.expiration       1

resource-group.created       1

Currrent Event Counts

Event Type                   Count

cpu.load                     32

volume.growthrate            23

host.snmp_status             9

df.snapshot.kbytes           8

data-export                  5

df.kbytes                    4

host.nfs_service_status      4

df.inodes                    2

respool.space                2

status.global                2

dfm.load                     1

qtree.kbytes                 1

dfm.free.space               1

disk.reconstruct             1

dfm.license.limit            1

volume.overcommit            1

traplistener-start           1

database_backup.status       1

dfm.license.expiration       1

resource-group.created       1

resource-group.modified      1

The cli without -s removed the above shown entires from the db.

C:\>dfm purge event -S Information  5d

Purged 135 events successfully in 0 seconds

One can also run with out the -S or -s just with interval.

C:\>dfm purge event 2d

Purged 4 events successfully in 0 seconds

Regards

adai

[CASTROJSEC]

Thank you.  This will not delete any performance data correct?

[adaikkap]

Hi Castro,

      This will only delete events from DFM database including performance events. But will not delete any of the performance data stored in the flat files.

Regards

adai

[pburcin]

Is there an answer to Rob's original question??  We are also attempting to run/use dfmpurge. We are also using DFM v5.1 and Windows Server 2008 R2 SP1.  Why does dfmpurge throw an error referencing MSVCR80.dll?