AVEVA MES Support Cases

[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 MiddleWare Service Fails to Start

MES Version6.2.2 The following services are failing to start. This is after migrating the VM to a new VM Platform. MES Workflow Connector Wonderware MES Middleware Host Wonderware MES Service

[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

[ISS Support Case] MES 7.0 Middleware CreateWOFromProcess Session ID invalid

After rebooting the MES Middleware server, started having issues with wo\job creation for jobs calling CreateWOFromProcess. Getting Session ID invalid errors in logs. Tried multiple ways to "fix" the middleware issue without success: Stop\restart Middleware service and reboot Rerun configurator Repair on MES middleware installation Deleted old session records from the sessn table Finally tracked down the issue to the following code which had worked for years to retrieve session ID: dim iSessId as integer; dim clientSession As aaFactMES.aaClientSession; dim aafResult as aaFactMES.Result; aafResult = aaFactMES.aaClientSession.GetInstance(); clientSession = aafResult.Value; iSessId = ClientSession.SessionId; As a workaround, we changed the scripts to run different API call to create the session ID using aaMES.Core instead of aaFactMES call. Result = aaMES.Core.aaSession.GetSessions( oNull, ClientType, userId );

[ISS Support Case] Login Failure Enterprise Console

Client called in as they were receiving an error message when trying to log into Enterprise console that states: "An error has occurred. See the Aveva work task log file or contact the system administrator for more details."

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

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:

[ISS Support Case] Intermittent Failed To Execute Workflow Pop Up Scanning Out of a Station

Possibly referencing case 86488 / SR 960389413 (unclear) When a user on the floor tries to scan out (finish a job) they are intermittently presented with a pop up: POP-UP FORM "WF_AddBarcodeNumbersScanOUT has failed to execute. Ensure the workflow exits and published". They close the pop up and scans out. Having to scan out twice Scan out the product in their station and the product moves to the next station. No discernible pattern different times, different stations different users. Suspicion is that the issue was present on Monday but definitely Tuesday of this week. Domain Environment

[ISS Support Case] Bi Gateway Reports Useable Reports Are Not Generating

Had a previous issue were middleware was consistently crashing. After a repair the system appeared to stabilize. Now they are seeing an issue with Bi-Gateway, useable reports are not generated due to missing data for some of the necessary dimensions. Client tried an un-deploy and the re-deploy of the BI-Gateway but and was met with an error. 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. if this field is blank

[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] 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 issue

Version 2014 R2 "Proxy failed to connect to middleware server" Seems like all the communications have stopped working. Did re-input username and password and hit configure again. MES is green in the configurator. Services started

[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] MES v7.0 Datalog

Recent upgrade to MES 2023 (v7.0) has changed the data_log table entries so that last_edit_comment field is now setting entry to "DataLog.Add" as the default for all records. We were using this field for data entry in prior versioin of MES and wondering if it's possible to eliminate the default entry "DataLog.Add"?

[ISS Support Case] MES downtime stopped working after upgrade

6/29/2023: -Waiting on SMC Log's. -Waiting to here back from customer to see if the MES Middleware Connection string are pointed to the DB server after the upgrade.

[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.