Warning dialog on logout (after OA update)

Discussions about product bugs & problems!
Note: This is no replacement for the Official ETM Support!
2 posts • Page 1 of 1
GrahamRA
Posts:6
Joined: Wed Dec 09, 2020 12:46 pm

Warning dialog on logout (after OA update)

Post by GrahamRA »

Howdy,

We're developing a multi-user touchscreen WinCC OA application which should support a user logging out so another user can log in.

The application is intended to run in single-application "kiosk" mode with the only input being from the touchscreen.

The functionality for this was working correctly until I installed the latest v3.17 release (P012) on our Red Hat Enterprise Linux 8 testing rig; now when the user logs out, a warning dialog is generated which reads:
You have no permission to display this panel: StartPanel !
NB: StartPanel is the top panel in our panel topology.

The warning dialog seems to appear when calling the STD_LogoutCurrentUser() function.

I've confirmed that the problem occurs on P012 on my Windows 10 development machine, however the problem does not occur on P005 (Also Windows 10).

I'd try to narrow it down as to which patch causes the issue but I can't see where to download patches P006 to P011.

Obviously displaying such a warning is an issue for our users, what's worse is that the dialog appears behind the main application, which means it cannot be dismissed, and since it's a modal dialog it blocks use of the rest of the application—so it is a big issue for us.

If anybody has any ideas why this might be happening, I'd appreciate some help!

With thanks,
Graham

leoknipp
Posts:2928
Joined: Tue Aug 24, 2010 7:28 pm

Re: Warning dialog on logout (after OA update)

Post by leoknipp »

In the WinCC OA Portal only the newest patch for every version is available. There is no possibility to download older patches.

I have tested it on my local machine and I did not get this dialog when selecting the option for the logout.
The displayed panels do not change and the user is logged out.

Can you reproduce the behaviour in any project running WinCC OA 3.17 P012?

Best Regards
Leopold Knipp
Senior Support Specialist

2 posts • Page 1 of 1