Could not locate core services" when opening Web Applications

How can we help you today?

"Could not locate Core Services" or "Server Error" when opening Web Applications

Issue

Web Applications does not start. The follow error message is displayed.

web applications error PME 8.x

In PME 2024 using Microsoft Edge:
web applications request error PME 2024
Following the review of the diagnostics information, the following exception is displayed in the Windows Application Event Log:

Exception Information Details:
======================================
Exception Type: System.ServiceModel.FaultException
Action: NULL
Code: System.ServiceModel.FaultCode
Message: Login failed for user 'AMUser'. Reason: The account is disabled.
Reason: Login failed for user 'AMUser'. Reason: The account is disabled.

Product Line
Power Monitoring Expert 7.2.x
Power Monitoring Expert 8.x
Power Monitoring Expert 9.x
Power Monitoring Expert 2020
Power Monitoring Expert 2021
Power Monitoring Expert 2022
Power Monitoring Expert 2023
Power Monitoring Expert 2024

Environment
PME Web Applications

Cause
1. Application Modules Core Services Host is not started
2. Incorrect settings on the Local Group Policy Editor

Resolution
1. Start the following services
ApplicationModules (CoreServicesHost) or ION Application Modules Core Services Host
ApplicationModules (DataServicesHost) or ION Application Modules Data Services Host
ApplicationModules (ProviderEngineHost) or ION Application Modules Provider Engine Host

Services stopped PME

2. Open "Local Group Policy Editor" or press Windows + R and type "gpedit.msc"

Expand the Administrative Templates folder under the Computer Configuration tab on the left pane.
Expand the Windows Components folder.
Press the Internet Explorer folder.

local policy group editor

Scroll down and enable the "Make proxy settings per-machine (rather than per user)"

Press on the folder titled Internet Control Panel after expanding the Internet Explorer folder.

Double-click the "Disable the Connections page" settings to open it in a new window. "Enable" it.

local policy group editor

Restart the server.

Note the comment "No" has no effect on the enabled state.

3. Ensure that the AMUSER is enabled and has the correct permissions setup.

Verify the user in SQL Server Management Studio, Security-->Log Ins--> Users. The AMUser should have the following settings as seen below.
Note: The AMUser password will be left blank because it is a unique password that will be added to the user during the installation.
The system will warn you that it is a risk, just ignore it and go through with creating the login.

SQL Server Management Studio