Lampholder BC with safety skirt 16mm conduit thread

Yes , the part number is 503e-we
For more information on batten holders please visit the Clipsal web site on the link provided https://www.clipsal.com/Trade/search-results?q=batten%20holders

Issue
When trying to access the application webpage, the following error occurs:
                   
The following error is seen in Windows Application Event Viewer:
                   
                    The Module DLL HipISSEngineStub.dll failed to load. The data is the error.

Product Line
Power Monitoring Expert 7.2.x

Environment
IIS 7
McAfee Anti Virus
HipISSEngineStub.dll

Cause
Upon checking Application Pools in IIS Manager, it turns out the application pool has stopped.  However, the problem cannot be resolved by simply re-starting the application pool.  By doing so and accessing the web page, it will stop again.
                   

If McAfee has recently been uninstalled, updated, or changed the installation somehow, there is probably still a reference to it in the ISAPI settings.  Refer to the following link for more information:

          kc.mcafee.com/corporate/index
          https://kc.mcafee.com/corporate/index?page=content&id=KB72677&actp=LIST

Resolution
Remove the reference to the MfeEngine in the applicationHost.config:

1.  Navigate to: %windir%\system32\inetsrv\config

2.  Open the file applicationHost.config as Administrator for editing in Notepad.

IMPORTANT: make sure a copy of the original file is available before making any changes.

3.  Edit the  globalModules section and remove the following line:
          <add name="MfeEngine" image="%windir%\System32\inetsrv\HipIISEngineStub.dll" />;

4.  Edit the modules section and remove the following line:
          <add name="MfeEngine" />;

5.  After editing the applicationHost.config file, save the file, then restart the IIS server using iisreset or by restarting the system.
 

Issue:
DL1BA024 life expectancy

Product Line:
Push Buttons and Operator Interface

Environment:
30 mm push button

Cause:
Product Features

Resolution:
All incandesent lamps have an estimated life of 2000 hours.

 

Issue
The customer is receiving an "HTTP 503. The service is unavailable" error message when selecting the 'Reports' tab through Web Applications.



Product Line
Power Monitoring Expert 7.2.x / 8.x / 9.x / 2020

Environment
Web Reports

Cause
If Microsoft Monitoring Agent with .Net Application monitoring is installed, the 'WebReporterAppPool' Application Pool within Internet Information services is not started and crashes if started manually.

Resolution 1
This resolution does not require removing Microsoft Monitoring Agent. Instead, it is uninstalled, then reinstalled via the command line using a switch that prevents the .Net Application monitorng from being installed.

To do this:

1. Uninstall Microsoft Monitoirng Agent from Control Panel -> Programs and Features
2. Start a command prompt in the directory that includes the Microsoft Monitoring Agent installer (it's called MOMAgent.msi)
3. Run MOMAgent.msi NOAPM=1

Resolution 2
Windows updates will install a tool named the "Microsoft Monitoring Agent".  This tool applies a policy to the application pool that causes it to crash.  Uninstalling the tool through Add/Remove programs will allow Web Reports to function as expected.

Issue:
LA2KT2E and LA2KT2U contacts

Product Line:
Tesys K Line Contactors

Environment:
IEC Contactor Accessories
 
Resolution:
This module has one form C contact.
One normally open and one normally closed with a shared common.  Instructions are attached.

Issue
When opening Web Applications, "503 Service Unavailable" error is displayed. 

Product Line 
Power Monitoring Expert 9.0

Environment
Web Applications
IIS Manager

Cause
A potential cause for this error is when an application or a process is using port 80 (HTTP) or port 443 (HTTPS). This results in the Default Website in IIS being stopped, and when starting it manually the following error is prompted.


Resolution
1. following netstat commands can be used in command prompt to retrieve the Process ID (PID) of the application/process that is using port 80 or 443. In this example, the PID of the process that is using port 80 is 5484
netstat -aon | find ":80"
netstat -aon | find ":443"

2. The result will be something like the below:

In this example, the PID of the process that is using port 80 is 5484.
3. The process associated with this PID can be found in Task Manager, Details tab (can be ordered by PID). In this example, this PID belongs to Skype.

4. Once the process/application is identified, (if possible) it can be temporarily ended from Task Manager (right-clicking and selecting End Task), to examine if the Default Website in IIS Manager can now be successfully started which then results in Web Applications to return to normal operation. If this is the case the identified application (in this example Skype) needs to be configured to deploy another port.