Mapp View Runtime stops responding after action execution errors (-1061090151)

Ask Questions HMI & Visualization
1

Hi,

We are experiencing an issue after upgrading to mapp View 6.8.

Occasionally the HMI stops responding to page navigation. The current page remains visible, but it is no longer possible to switch to other pages. In some cases the only recovery method has been a PLC restart.

The following error is logged when the problem occurs:

Error
ID: -1061090151
mapp View Server
Problem executing action “clientSystem.Action.LoadContentInArea”
in context “MainMenu180”

The error may be followed by messages such as:

Information
ID: 1086398273
Client action “clientSystem.Action.LoadContentInArea” was canceled.

and:

Warning
ID: -2134803125
Client in loading phase:
Page or piece of content “Robots_System” not loaded.

The issue is not limited to a single page or content. We have observed the same error while navigating to different pages and menus.

We have also observed the same error code (-1061090151) for actions other than LoadContentInArea, for example:

Problem executing action “opcUa.NodeAction.SetValueNumber”
in context “PackLidGripCalibrateAxisZ_200”

This makes us wonder if the error code represents a more general action execution problem rather than a page-specific issue.

Additional observations:

The same HMI project has been running for several years without any occurrences of error -1061090151.
Searching the complete logger history shows that all occurrences of this error code appeared only after upgrading to the latest software versions approximately one week ago.
The issue has now been observed on two separate machines.
During one occurrence, another active HMI client refreshed and later closed its session. After that, page navigation started working again, which may indicate a runtime or session-related issue.

Has anyone seen similar behaviour, or knows what conditions can trigger error -1061090151 in mapp View?

Thanks!

2

Hi Rickard,
the issue that you describe is common. It typically happens when you try execute an action in a wrong context. The most common scenario is a page where you have multiple contents like a side bar, footer and main page. If you use the page load event from the side bar to load a main content this may fail because the default main content was not finished loading. If you then try to load a new content into the main area while its loading you will see the error that you describe. The issue depends on the timing, so it can work 9 out of 10 times but the one time the main page loads a little bit slower and then you run into this error. You should be able to see the issue in the server backend when you trace the events while the issue happens.

Events and actions

Stephan

3

Hi Stephan,

Thank you for your reply.

When searching the forum, I found several older posts describing very similar issues. What I find interesting is that we only started seeing this behavior after upgrading to the latest mapp View version. We have not changed our EventScripts or navigation logic for a very long time, so perhaps the newer runtime is more sensitive to timing issues than previous versions.

One additional question: is it common for the mapp View Server to end up in a bad state after such an error? In our case, page navigation stopped working completely and the only way we found to recover was to restart the PLC. Is there any other way to recover the runtime without rebooting the controller?

Thanks, Rickard