Hello everyone,
We have a weird client proj directory since we update our winccoa servers patch.
We use the webClient entry clientProjExt = 1, to difference our differents servers in the client side but, since we update the server patch, our clients are using a single directory with the name: projectName_-1
We update our winccoa 3.17P12 servers to 3.17P30, maybe this is a known behaivor and we are missing something?
clientProjExt bug when update patch
Search
Re: clientProjExt bug when update patch
I did a test with WinCC OA 3.17 and I get an error when using the config entry clientProjExt = 1.
WCCOActrl (2), 2023.12.28 12:53:01.374, CTRL, WARNING, 73, Variable not defined, C:\WinCC_OA\versions\3.17\scripts\webclient_http.ctl Line: 84, Cannot find value from previous execute, (forgotten return in eventHost?)
WCCOActrl (2), 2023.12.28 12:53:01.375, CTRL, WARNING, 76, Invalid argument in function, C:\WinCC_OA\versions\3.17\scripts\webclient_http.ctl Line: 84, eventHost()
WCCOActrl (2), 2023.12.28 12:53:01.375, CTRL, WARNING, 73, Variable not defined, C:\WinCC_OA\versions\3.17\scripts\webclient_http.ctl Line: 84, Cannot find value from previous execute, (forgotten return in eventHost?)
Can you please check if you get the same error in your project.
The error might be the cause why the project name is not correct.
I have fixed the bug which causes the log messages. The bugfix will be included in a future patch for WinCC OA 3.17.
Newer WinCC OA versions are not affected.
Best Regards
Leopold Knipp
Senior Support Specialist
WCCOActrl (2), 2023.12.28 12:53:01.374, CTRL, WARNING, 73, Variable not defined, C:\WinCC_OA\versions\3.17\scripts\webclient_http.ctl Line: 84, Cannot find value from previous execute, (forgotten return in eventHost?)
WCCOActrl (2), 2023.12.28 12:53:01.375, CTRL, WARNING, 76, Invalid argument in function, C:\WinCC_OA\versions\3.17\scripts\webclient_http.ctl Line: 84, eventHost()
WCCOActrl (2), 2023.12.28 12:53:01.375, CTRL, WARNING, 73, Variable not defined, C:\WinCC_OA\versions\3.17\scripts\webclient_http.ctl Line: 84, Cannot find value from previous execute, (forgotten return in eventHost?)
Can you please check if you get the same error in your project.
The error might be the cause why the project name is not correct.
I have fixed the bug which causes the log messages. The bugfix will be included in a future patch for WinCC OA 3.17.
Newer WinCC OA versions are not affected.
Best Regards
Leopold Knipp
Senior Support Specialist
-
- Posts: 42
- Joined: Mon Jan 27, 2020 1:42 pm
Re: clientProjExt bug when update patch
Yes, same log warning messages here.
-
- Posts: 42
- Joined: Mon Jan 27, 2020 1:42 pm
Re: clientProjExt bug when update patch
Hello again,
Could that bug also affect to the clients connection with the event manager? Since the update, we are experimenting also a randomly expired connection error when we try to open web or desktop client. Only restarting the winccoa server the clients are able to connect again.
This is the log messages, where the IP was modified.
WCCOAui (0), 2024.01.25 10:51:06.991, SYS, INFO, 1, Manager Start, PROJ, Principal_-1, V 3.17 - 3.17 platform Windows AMD64 linked at Oct 4 2023 00:06:39 (236ad6fc707)
WCCOAui (0), 2024.01.25 10:51:07.131, SYS, INFO, 3, Trying to connect to (SYS: 0 Data -num 0 CONN: 1) @ 1.1.1.1:4897
WCCOAui (0), 2024.01.25 10:51:13.049, SYS, INFO, 4, Connected to (SYS: 0 Data -num 0 CONN: 1) @ 1.1.1.1 (1.1.1.1)
WCCOAui (2), 2024.01.25 10:51:13.165, SYS, INFO, 6, Initialization by Data Manager finished
WCCOAui (2), 2024.01.25 10:51:13.167, SYS, INFO, 3, Trying to connect to (SYS: 1 Event -num 0 CONN: 1) @ 1.1.1.1:4998
WCCOAui (2), 2024.01.25 10:51:14.534, SYS, INFO, 4, Connected to (SYS: 1 Event -num 0 CONN: 1) @ 1.1.1.1 (1.1.1.1)
WCCOAui (2), 2024.01.25 10:51:15.961, SYS, INFO, 0, , Connection from 1.1.1.1 expired
WCCOAui (2), 2024.01.25 10:51:15.963, IMPL, FATAL, 5, Connection not possible, WCCILevent
WCCOAui (2), 2024.01.25 10:51:18.093, SYS, INFO, 181, Closing connection to (SYS: 0 Data -num 0 CONN: 1)
WCCOAui (2), 2024.01.25 10:51:18.095, SYS, INFO, 39, Connection lost, MAN: (SYS: 0 Data -num 0 CONN: 1), Connection closed
WCCOAui (2), 2024.01.25 10:51:18.096, SYS, FATAL, 63, Connection error, Lost connection to data during initialization, exiting...
Could that bug also affect to the clients connection with the event manager? Since the update, we are experimenting also a randomly expired connection error when we try to open web or desktop client. Only restarting the winccoa server the clients are able to connect again.
This is the log messages, where the IP was modified.
WCCOAui (0), 2024.01.25 10:51:06.991, SYS, INFO, 1, Manager Start, PROJ, Principal_-1, V 3.17 - 3.17 platform Windows AMD64 linked at Oct 4 2023 00:06:39 (236ad6fc707)
WCCOAui (0), 2024.01.25 10:51:07.131, SYS, INFO, 3, Trying to connect to (SYS: 0 Data -num 0 CONN: 1) @ 1.1.1.1:4897
WCCOAui (0), 2024.01.25 10:51:13.049, SYS, INFO, 4, Connected to (SYS: 0 Data -num 0 CONN: 1) @ 1.1.1.1 (1.1.1.1)
WCCOAui (2), 2024.01.25 10:51:13.165, SYS, INFO, 6, Initialization by Data Manager finished
WCCOAui (2), 2024.01.25 10:51:13.167, SYS, INFO, 3, Trying to connect to (SYS: 1 Event -num 0 CONN: 1) @ 1.1.1.1:4998
WCCOAui (2), 2024.01.25 10:51:14.534, SYS, INFO, 4, Connected to (SYS: 1 Event -num 0 CONN: 1) @ 1.1.1.1 (1.1.1.1)
WCCOAui (2), 2024.01.25 10:51:15.961, SYS, INFO, 0, , Connection from 1.1.1.1 expired
WCCOAui (2), 2024.01.25 10:51:15.963, IMPL, FATAL, 5, Connection not possible, WCCILevent
WCCOAui (2), 2024.01.25 10:51:18.093, SYS, INFO, 181, Closing connection to (SYS: 0 Data -num 0 CONN: 1)
WCCOAui (2), 2024.01.25 10:51:18.095, SYS, INFO, 39, Connection lost, MAN: (SYS: 0 Data -num 0 CONN: 1), Connection closed
WCCOAui (2), 2024.01.25 10:51:18.096, SYS, FATAL, 63, Connection error, Lost connection to data during initialization, exiting...
-
- Posts: 42
- Joined: Mon Jan 27, 2020 1:42 pm
Re: clientProjExt bug when update patch
And this is what happends if we comment the config entry clientProjExt = 1
WCCOAui (0), 2024.01.25 16:33:01.557, SYS, INFO, 1, Manager Start, PROJ, Principal, V 3.17 - 3.17 platform Windows AMD64 linked at Oct 4 2023 00:06:39 (236ad6fc707)
WCCOAui (0), 2024.01.25 16:33:02.743, SYS, INFO, 3, Trying to connect to (SYS: 0 Data -num 0 CONN: 1) @ 1.1.1.1:4897
WCCOAui (0), 2024.01.25 16:33:08.709, SYS, INFO, 4, Connected to (SYS: 0 Data -num 0 CONN: 1) @ 1.1.1.1 (1.1.1.1)
WCCOAui (2), 2024.01.25 16:33:08.870, SYS, WARNING, 227, DpType Container file cache C:\Users\user\.wincc_oa-cache\Principal\data\ui_DpMsgTypeContainer.bin not found. Requesting the DpType Container from Data-Manager.
WCCOAui (2), 2024.01.25 16:33:09.204, SYS, INFO, 6, Initialization by Data Manager finished
WCCOAui (2), 2024.01.25 16:33:09.207, SYS, INFO, 3, Trying to connect to (SYS: 1 Event -num 0 CONN: 1) @ 1.1.1.1:4998
WCCOAui (2), 2024.01.25 16:33:10.570, SYS, INFO, 4, Connected to (SYS: 1 Event -num 0 CONN: 1) @ 1.1.1.1 (1.1.1.1)
WCCOAui (2), 2024.01.25 16:33:11.998, SYS, INFO, 0, , Connection from 1.1.1.1 expired
WCCOAui (2), 2024.01.25 16:33:12.000, IMPL, FATAL, 5, Connection not possible, WCCILevent
WCCOAui (2), 2024.01.25 16:35:03.935, SYS, INFO, 181, Closing connection to (SYS: 0 Data -num 0 CONN: 1)
WCCOAui (2), 2024.01.25 16:35:03.936, SYS, INFO, 39, Connection lost, MAN: (SYS: 0 Data -num 0 CONN: 1), Connection closed
WCCOAui (2), 2024.01.25 16:35:03.938, SYS, FATAL, 63, Connection error, Lost connection to data during initialization, exiting...
WCCOAui (0), 2024.01.25 16:33:01.557, SYS, INFO, 1, Manager Start, PROJ, Principal, V 3.17 - 3.17 platform Windows AMD64 linked at Oct 4 2023 00:06:39 (236ad6fc707)
WCCOAui (0), 2024.01.25 16:33:02.743, SYS, INFO, 3, Trying to connect to (SYS: 0 Data -num 0 CONN: 1) @ 1.1.1.1:4897
WCCOAui (0), 2024.01.25 16:33:08.709, SYS, INFO, 4, Connected to (SYS: 0 Data -num 0 CONN: 1) @ 1.1.1.1 (1.1.1.1)
WCCOAui (2), 2024.01.25 16:33:08.870, SYS, WARNING, 227, DpType Container file cache C:\Users\user\.wincc_oa-cache\Principal\data\ui_DpMsgTypeContainer.bin not found. Requesting the DpType Container from Data-Manager.
WCCOAui (2), 2024.01.25 16:33:09.204, SYS, INFO, 6, Initialization by Data Manager finished
WCCOAui (2), 2024.01.25 16:33:09.207, SYS, INFO, 3, Trying to connect to (SYS: 1 Event -num 0 CONN: 1) @ 1.1.1.1:4998
WCCOAui (2), 2024.01.25 16:33:10.570, SYS, INFO, 4, Connected to (SYS: 1 Event -num 0 CONN: 1) @ 1.1.1.1 (1.1.1.1)
WCCOAui (2), 2024.01.25 16:33:11.998, SYS, INFO, 0, , Connection from 1.1.1.1 expired
WCCOAui (2), 2024.01.25 16:33:12.000, IMPL, FATAL, 5, Connection not possible, WCCILevent
WCCOAui (2), 2024.01.25 16:35:03.935, SYS, INFO, 181, Closing connection to (SYS: 0 Data -num 0 CONN: 1)
WCCOAui (2), 2024.01.25 16:35:03.936, SYS, INFO, 39, Connection lost, MAN: (SYS: 0 Data -num 0 CONN: 1), Connection closed
WCCOAui (2), 2024.01.25 16:35:03.938, SYS, FATAL, 63, Connection error, Lost connection to data during initialization, exiting...