Gedi closing immediately

MattPaulissen · Post by **MattPaulissen** » Wed Jan 08, 2020 8:52 pm

I have a remote para license and have been working remotely through mxProxy for a while now with no issues. Recently, the customer gave me VPN access onto their network. I removed the mxProxy line from my remote config project, and it connects, but gedi just flashes up and immediately closes. Is there something I'm missing here? Here is all the log on my side says:

WCCOAui (1), 2020.01.08 13:39:26.217, SYS, INFO, 3, Trying to connect to (SYS: 0 Data -num 0 CONN: 1) @ xxx:4897
WCCOAui (1), 2020.01.08 13:39:27.711, SYS, INFO, 4, Connected to (SYS: 0 Data -num 0 CONN: 1) @ xxx
WCCOAui (1), 2020.01.08 13:39:36.357, SYS, INFO, 6, Initialization by Data Manager finished
WCCOAui (1), 2020.01.08 13:39:36.358, SYS, INFO, 3, Trying to connect to (SYS: 1 Event -num 0 CONN: 1) @ xxx:4998
WCCOAui (1), 2020.01.08 13:39:36.620, SYS, INFO, 4, Connected to (SYS: 1 Event -num 0 CONN: 1) @ xxx
WCCOAui (1), 2020.01.08 13:39:36.694, SYS, INFO, 102, Waiting for user names/passwords
WCCOAui (1), 2020.01.08 13:39:36.746, SYS, INFO, 103, User names/passwords initialized
WCCOAui (1), 2020.01.08 13:39:37.274, SYS, INFO, 0, , MAN: (SYS: 1 Event -num 0 CONN: 1), SHUT_DOWN_MANAGER received
WCCOAui (1), 2020.01.08 13:39:39.359, SYS, INFO, 181, Closing connection to (SYS: 1 Data -num 0 CONN: 1)
WCCOAui (1), 2020.01.08 13:39:39.359, SYS, INFO, 181, Closing connection to (SYS: 1 Event -num 0 CONN: 1)
WCCOAui (1), 2020.01.08 13:39:39.392, SYS, INFO, 39, Connection lost, MAN: (SYS: 1 Data -num 0 CONN: 1), Connection closed
WCCOAui (1), 2020.01.08 13:39:39.407, SYS, INFO, 39, Connection lost, MAN: (SYS: 1 Event -num 0 CONN: 1), Connection closed
WCCOAui (1), 2020.01.08 13:39:39.443, SYS, INFO, 2, Manager Stop

and on the server side:

WCCILdata (0), 2020.01.08 14:39:27.769, SYS, INFO, 4, Connected to (SYS: 1 Ui -num 1 CONN: 1) @ xxx(::1)
WCCILdata (0), 2020.01.08 14:39:29.097, SYS, INFO, 0, , Manager (SYS: 1 Ui -num 1 CONN: 1) initialised
WCCILevent (0), 2020.01.08 14:39:36.675, SYS, INFO, 4, Connected to (SYS: 1 Ui -num 1 CONN: 1) @ xxx(::1)
WCCILevent (0), 2020.01.08 14:39:37.066, PARAM,INFO, 0, , Terminate manager (SYS: 0 Ui -num 1 CONN: 1)
WCCILdata (0), 2020.01.08 14:39:39.394, SYS, INFO, 39, Connection lost, MAN: (SYS: 1 Ui -num 1 CONN: 1), Connection closed
WCCILevent (0), 2020.01.08 14:39:39.410, SYS, INFO, 39, Connection lost, MAN: (SYS: 1 Ui -num 1 CONN: 1), Connection closed

leoknipp · Post by **leoknipp** » Thu Jan 09, 2020 8:32 am

Which WinCC OA version and patch are you using?

The problem possibly is that your client is not allowed to connected (Device Management) and therefore the UI gets the stop signal from the server.

Best Regards
Leopold Knipp
Senior Support Specialist

MattPaulissen · Post by **MattPaulissen** » Thu Jan 09, 2020 3:32 pm

Currently they're both on 3.16 patch 12. I thought device management only really applied to the desktop and mobile UIs? I'm using a thick client on my side running -localLicense so I can use my para to configure the server. I was using the same machine before but with mxProxy and it worked fine.

leoknipp · Post by **leoknipp** » Fri Jan 10, 2020 9:16 am

Did you check the settings in the Device Management?
If the script webclient_http.ctl is running the script checks if the running user interfaces are allowed to connect. Clients which are not allowed to connect are stopped and then the log messages are written which occured in your case.

Best Regards
Leopold Knipp
Senior Support Specialist

MattPaulissen · Post by **MattPaulissen** » Fri Jan 10, 2020 11:58 pm

Thanks. I'll go check that as well.

Bugs / Problems