[ISS Support Case] MES Middleware repeatedly crashing Proxy failed to connect to Middleware

Last updated: April 7th, 2025

Description

Seeing a lot of errors in the logger (other software can no longer use the middleware proxy) and middleware keeps crashing As an immediate workaround Windows was configured to restart the service every time it crashes. The BI Gateway SSRS reports are missing data for some of the necessary dimensions so no usable reports can be generated. Client tried an un-deploy and the re-deploy but recieved an error (see BI Gateway error jf 4.png) (SEE BOX). As a result client abandoned the original BIGateway_DataStore and created a new DB called BIGateway. Unfortunately the issue persists. Provided screenshot of the Utilization State (SSRS > Home > MES Reports > UtilizationByEntity) which is blank. A report can not be generated if this field is blank. SMC Messages (from photos): - Connection information missing for the Datasource MESRDBMESDB - In order to deploy or undeploy MESRDBXXXX, dependent objects must be undeployed first Windows Event Viewer: Faulting application name: FactMES.Server.Host.exe, version: 2523.112.1367.1, time stamp: 0x63c0871c Faulting module name: ucrtbase.dll, version: 10.0.17763.1490, time stamp: 0x51d4b57a Exception code: 0xc0000409 Fault offset: 0x000a5b3b Faulting process id: 0x4930 Faulting application start time: 0x01da6f0375960407 Faulting application path: C:\Program Files (x86)\Wonderware\MES\Middleware\FactMES.Server.Host.exe Faulting module path: C:\Windows\System32\ucrtbase.dll Report Id: fbf0edf9-51ba-4a3a-95b2-7a870f80b6cd Faulting package full name: Faulting package-relative application ID:

Author: Kevin Modlin
Published: April 7th, 2025

Details:

Product: MES

Version: 2023

Solution: [Solution is visible below when you're logged in and have a current subscription]

Date Created:	03/07/2024
Case:	86547

Give feedback about this article

Recommended articles

[ISS Support Case] Middleware stops running after a few weeks

They have rerun the MES configurator to get it going again.

[ISS Support Case] MES Middleware Proxy configuration failure

Ive installed the MES 2020 software and am stuck in the thrall of the post-configuration. Got to the Middleware Proxy and keep getting this: Attempting to configure WWMES2020 Middleware Proxy getting Error: Service Unavailable (503). This server is DB24, but back in September of 2022, when we did the initial install on DB21 this configured with no issues. I went back and looked. Same configs. Any ideas what could be different on this server compared to the other? Not saying that we didnt have issues at the time, but they are resolved now and Im stuck as to where to look next. Check the following: the MES middleware host is valid, accessible, and configured with a fully qualified name if required for the certificate; the HTTPS port is valid and it matches the web port configured for the System Management Server on the MES middleware node. Make sure to reconfigure the DB/MW Communication component and try again if the web port on the MES middleware node has changed.

[ISS Support Case] MES Error

Worked up until last Thursday and other reports are fine only one displays this behavior Mes report builder: "An error has occurred during report processing about report processing SQL server 2019

[ISS Support Case] MES 2020 14 day repeating schedule assistance needed

On MES 2020, upgraded from 2014. They have a 14 day schedule, in the Shift Schedule they need to add 4 shifts. Instead of 7 day repeating schedule, it is a 14 day repeating schedule. Need to be able to have 14 days of non repeating entries. Currently only option is to only do 7 days and then repeat.