Event Log Consolidatior

Can you provide some more environmental details?

What operating system did you install it onto?

What operating systems are running on your monitored servers?

I installed on a Dell Vostro i5 3rd gen , 8GB, Samsung SSD 128GB W7 Pro  Servers, two 2K8 R2 standard, and one 2K3 standard

Is that a Windows 7 x64 installation, or an x86 (32-bit) installation?

The reason I ask goes to the question of memory management. From a previous conversation in this forum, the application stores all data in memory. By default it reads 30 days of history, and this may be a significant amount of memory consumption depending on the specific target servers and the level of activity on those servers. (It may even be too much for a 32-bit operating system.)

You can disable the historical collection of event data. In the EventLogConsolidator.exe.config file and change this value to False and then restart the application.

<setting name="IsHistoryEnabled" serializeAs="String">

    <value>True</value>

</setting>

I would suggest trying that as a diagnostic step, and see if that eliminates the crash.

The loss of the server configuration information is a function of the crash itself, as the configuration does not get saved.

64bit. Sorry about that.

I will give that a try. I noticed it was hanging on loading historical data. Thank you!

Lawrence:

Thank you!! That worked.

Best,

Colette

Hi Lawrence:

I just had this happen. The Event Log Consolidator just crashed. This is the event viewer log.

I was only running at 3.79GB, not the full 8GB. Any ideas why?

0

CLR20r3

Not available

0

eventlogconsolidator.exe

1.0.0.108

4f27d79a

mscorlib

2.0.0.0

5265d021

1ec

0

System.OutOfMemoryException

C:\Users\cocoloco\AppData\Local\Temp\WER85A0.tmp.WERInternalMetadata.xml

C:\Users\cocoloco\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_eventlogconsolid_abf7f84b5eab6517ab7623311be23d5c839b8934_13d98d7c

0

878f6365-cfd0-11e3-8125-d067e52708eb

1

System.OutOfMemoryException I was only running at 3.79GB,

It's a 32-bit application. Running out of memory at 3.8GB makes perfect sense.