Power Monitoring Expert - Reports are not working properly - the w3wp.exe service is crashing

How can we help you today?

Issue
This problem will occur if McAfee antivirus is installed and the Host Intrusion Protection Service is being used.

1. The report tree will load - although it may be very slow to appear if you are running a browser on a client machine.
2. When you go to select a report, or immediately after clicking 'Generate Report' the application will hang - again this is the behavior you will see if running a browser on a client rather than on the server.

In the Windows Application Log on the server, you will likely see the following errors:

#1.

Faulting application name: w3wp.exe, version: 8.5.9600.16384, time stamp: 0x52157ba0
Faulting module name: LMBrickX.dll_unloaded, version: 11.13.1.5, time stamp: 0x57380ea6
Exception code: 0xc0000005
Fault offset: 0x0001ea40
Faulting process id: 0x39c8
Faulting application start time: 0x01d29ce87b03e205
Faulting application path: C:\Windows\SysWOW64\inetsrv\w3wp.exe
Faulting module path: LMBrickX.dll
Report Id: 9e7d9168-08de-11e7-80c6-782bcb57a066
Faulting package full name:
Faulting package-relative application ID:

#2.

Faulting application name: w3wp.exe, version: 8.5.9600.16384, time stamp: 0x52157ba0
Faulting module name: KERNELBASE.dll, version: 6.3.9600.18340, time stamp: 0x5736541b
Exception code: 0xe0434352
Fault offset: 0x00014878
Faulting process id: 0x39c8
Faulting application start time: 0x01d29ce87b03e205
Faulting application path: C:\Windows\SysWOW64\inetsrv\w3wp.exe
Faulting module path: C:\Windows\SYSTEM32\KERNELBASE.dll
Report Id: a17d4cad-08de-11e7-80c6-782bcb57a066
Faulting package full name:
Faulting package-relative application ID:

Product Line

Power Monitoring Expert 8.x

Cause
The cause is an interaction between McAfee and the Schneider Licensing brick. The affected versions of the Licensing brick are:

PME 8.1 w/LMBrick 1.9.4 (released December 2016)
PME 8.2 w/LMBrick 1.9.10 (to be released March 31, 2017)

Resolution
There are a couple of workarounds:
Within the McAfee UI
1. Add w3wp.exe to the list of Low-Risk Processes
2. Add w3wp.exe to the exclusion list

(see attached documents for screen caps)