[ISS Support Case] MES Middleware Proxy configuration failure

Last updated: April 7th, 2025

Description

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.

Author: Kevin Modlin
Published: April 7th, 2025

Details:

Product: MES

Version: 2020

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

Date Created:	02/01/2023
Case:	83644

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 login

When attempting to login to the migrated MES Client, the correct account yields the following message at login attempt: OS user group is not configured. Also tried admin/admin and get: This user's authentication mode does not match the current security mode.

[ISS Support Case] ArchestrA Object Toolkit Errors

Client reached out as they were experiencing the issue outlined in Article 000022240. They are requesting Hotfix IMS-922621_2020 per the article. The ArchestrA Object Toolkit was used to develop the MES Application Objects: Operations Capability Object (OCO) Utilization Capability Object (UCO) Sample Recording Object (SRO) When using these objects in one of the above listed Application Server versions, errors can flood the log due to a defect in the ArchestrA Object Toolkit. Symptoms After making a change in the MES Operations Capability object, the following errors can occur repeatedly in the log after the subsequent deployment of that object: Get(417, 127, idxAttribPropQuality) failed caught : GetFailoverValue source : ArchestrA.Core message : Exception from HRESULT: 0x800003E9 stack : at ArchestrA.Core.IPrimitiveRuntimeSite.GetAttribute(AttributeHandle& pHandle, IMxValue pMxValue) at ArchestrA.Toolkit.AObjectBase.Get(Int16 attributeId, Int16 primitiveId, EATTRIBUTEPROPERTY propertyId) caught : JobExecution_RuntimeExecute source : ArchestrA.Toolkit.ArchestrAObjectSupport message : Object reference not set to an instance of an object. stack : at ArchestrA.Toolkit.RuntimeBase.GetFailoverValue(Int16 attributeId) at ArchestrA.Toolkit.RuntimeBase.CheckpointDynamicAttributeData() Action Root Cause: A defect in an ArchestrA Object Toolkit (AOT) component.

[ISS Support Case] MES Configurator error - Please install the BI Gateway hotfix 2172196

See attached image for the error configuring MES BI Gateway Reports I have already applied the hotfix mentioned. Please install the BI Gateway hotfix 2172196 which can be found in the BI Gateway Reports Folder of the MES application folder. BI Gateway Reports feature configuration has started. Executing script 'intelligenceMESViews.sql'... An error occurred while executing the script