[ISS Support Case] Login Failure Enterprise Console

Last updated: March 6th, 2025

Description

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

Author: Kevin Modlin
Published: March 6th, 2025

Details:

Product: MES

Version: 6.1

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

Date Created:	03/01/2024
Case:	86488

Give feedback about this article

Recommended articles

[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 );