New Error When Opening MES

Here’s a new one for me when opening MES. It happened twice in a row, then twice it didn’t occur, then it happened again. Any thoughts?:

Application Error

Exception caught in: System.ServiceModel

Error Detail 
============
Message: This OperationContextScope is being disposed out of order.
Program: System.ServiceModel.dll
Method: PopContext

Client Stack Trace 
==================
   at System.ServiceModel.OperationContextScope.PopContext()
   at Epicor.ServiceModel.Channels.ImplBase`1.HandleContractFinally(String methodName, String returnTypeStr)
   at Ice.Proxy.BO.GenXDataImpl.GetList(String whereClause, Int32 pageSize, Int32 absolutePage, Boolean& morePages)
   at Ice.Lib.Framework.GenXObject.GetList(SearchOptions opts, Boolean& MorePages

Followed by:

Application Error

Exception caught in: Ice.Lib.EpiClientLib

Error Detail 
============
Message: Object reference not set to an instance of an object.
Program: Ice.Lib.EpiClientLib.dll
Method: customLayersUpToDate

Client Stack Trace 
==================
   at Ice.Lib.Customization.CustomLayeringManager.customLayersUpToDate(DataSet dsCLI, Boolean overrideCheck)

Followed by:

Application Error

Exception caught in: System.Data

Error Detail 
============
Message: Cannot find table 0.
Program: System.Data.dll
Method: get_Item

Client Stack Trace 
==================
   at System.Data.DataTableCollection.get_Item(Int32 index)
   at Ice.Lib.Framework.GenXObject.GetLayerVersionsDataSet(String uiNameKey, String userID)
   at Ice.Lib.Framework.FormFunctions.GetGenXLayerVersionsByKeys(Object sender, String fromNameKey, String userID)

then upon closing:

Application Error

Exception caught in: Ice.Lib.EpiClientLib

Error Detail 
============
Message: Object reference not set to an instance of an object.
Program: Ice.Lib.EpiClientLib.dll
Method: preCheckForLayers

Client Stack Trace 
==================
   at Ice.Lib.Customization.CustomLayeringManager.preCheckForLayers(DataTable dtVersions)
   at Ice.Lib.Customization.CustomLayeringManager.customLayersUpToDate(DataSet dsCLI, Boolean overrideCheck)

and:

Application Error

Exception caught in: Ice.Lib.EpiClientLib

Error Detail 
============
Message: Invalid request -- object Sender must be Core.Session or implement ILaunch
Program: Ice.Lib.EpiClientLib.dll
Method: GetSessionFromSender

Client Stack Trace 
==================
   at Ice.Lib.Framework.FormFunctions.GetSessionFromSender(Object sender)
   at Ice.Lib.Framework.FormFunctions.ReadDataSet(Object Sender, DataSet ds, String FileName, String Type, XmlReadMode mode, String& FilePath)
   at Ice.Lib.Customization.CustomLayeringManager.LoadCustomizationPersonalization(String custLayerInfoName, String custFileName

and:

Application Error

Exception caught in: Ice.Lib.EpiClientLib

Error Detail 
============
Message: Object reference not set to an instance of an object.
Program: Ice.Lib.EpiClientLib.dll
Method: getCompositeCustomizeDataSet

Client Stack Trace 
==================
   at Ice.Lib.Framework.EpiUIUtils.getCompositeCustomizeDataSet(String formNameKey, Boolean& customize, Boolean& respin, Boolean& cancel)
Application Error

Exception caught in: Ice.Lib.EpiClientLib

Error Detail 
============
Message: Object reference not set to an instance of an object.
Program: Ice.Lib.EpiClientLib.dll
Method: Execute

Client Stack Trace 
==================
   at Ice.Lib.Framework.EpiUIUtils.Execute(DataSet 
Application Error

Exception caught in: Ice.Lib.EpiClientLib

Error Detail 
============
Message: Object reference not set to an instance of an object.
Program: Ice.Lib.EpiClientLib.dll
Method: BindNConfigureControls

Client Stack Trace 
==================
   at Ice.Lib.Framework.EpiUIUtils.BindNConfigureControls()
   at Ice.Lib.Framework.EpiUIUtils.Execute(DataSet dsMenuItem, Boolean& respin)

Is this a customized screen? (Does it happen on base?)

Not sure yet. If I open with MESC and choose either base or custom it does NOT occur. If I open just MES it does (or can) occur. I have made a customization to the base MES form but I don’t think I’ve quite figure out how to default it yet so I assume it is just the base.

It could just be bad cache… clear your cache

Of course I cant get the issue to happen now for the life of me. How do I clear the Epicor cache? :bow:

Does this apply? Just delete c:\programdata\epicor?

That or open Epicor (Regular Menu) and go to Actions (or is it options? tools? something…) -> Clear Cache

1 Like

@josecgomez It’s base form, cache clearing both manual and via menu didn’t help! Argghh!! Big dog and pony show in front of CEO Tuesday!

@aidacra @Bart_Elia Where is the grovel emoji :clap:

Is it happening in other computers? I’ve never seen that before…

What are you groveling?

Grovelling for some help :blush:

It is also happening on another PC. Too bad I cant reset my own app pool…

man you need to get some power… your co-workers over there are like gollum

1 Like

My boss will get a kick out of that meme - wonder how the CEO will take it? :skull_crossbones:

For what it’s worth - I have a strange sense that this has something to do with the System Report Monitor.

Have you tried clearing the entire programdata directory. I have a batch file for users that they will run it kills all old dlls that may interfere with a new change.
It is

rd /S /Q c:\ProgramData\Epicor

Greg,

Thanks for the advice. I did try wiping that whole dir with no effect.

The problem has (at least temporarily) stopped. I am not sure if the reset the app pool or if something else has changed.

Resetting the app pool also did not solve the issue. :frowning:

Hi Chris, i had an issue similar to this one,
in my case it had to do with the shift select, i had an issue where my shift was from 0.00 till 24.00 when selecting this shift, the issue did occur, adjusting the shift to 0.01 till 23.59 did solve this issue.

regards,

Jos

1 Like

If I get the pop up messages at login that say:

Downloading from Database
then:
Caching layouts

I get NO errors.

The errors occur when I don’t see those messages

Hey Chris, did you ever get this resolved?

Hi Mach, sorry, I dont recall what we ever determined the issue to be (in reality, I dont think we discovered the cause, and the problem just went away at some point)

1 Like