Kontaktieren Sie uns

Article ID: 291589

Question

CHECKLIST - Webclient does not work

Answer

​ Web​ client does not work​

 

  1. Have you set the "Network active" and have you set the appropriate "Server" in your zenon project?

  2. Is the zenon runtime also correctly running on the PC which is configured to be the runtime server?

  3. Were the Runtime Changeable Data files created before the first start?

  4. Verify the global_vars.js for syntax errors: Is the project and server name correct? Is a semicolon (;) or an quotation mark (") missing, are there essential lines commented? Is HTTP tunnelling enabled per accident?  FQDN are not required.

  5. Is the name resolution to the configured servers in the global_vars.js in the network working correctly? (a ping by must always return the identical name (Case sensitive!) on all PCs) (you may also need to check the hosts file and its entries!).

  6. Is it possible to ping the PC with the zenon runtime as a server by it's name from the PC with the Webserver? 

  7. If the globa_vars.js on the Web Server was changed and the Web Client still trys to connect to defaults or an old config (RUNTIME SERVER NAME, PROJCET NAME) clear the browser cache on the WebClient and try again. Therefore, go to 'C:\Users\Currentuser\AppData\Local\Temp‘ (Use system environment variable %temp% in the address line of the windows explorer). Here delete the folder: ‚zenWebCli‘. The folder might also be located in '...\Temp\Low\zenWebCli'.

  8. Are there any Firewalls between Web client and Web server (Port 1102), and Web server and Runtime server? (Port 1100)?

  9. Is there an antivirus software / internet security software active, which is blocking content, the plugin start or the ports? '
  10. Which zenon version is in use on the runtime server? Which zenon version has the Web Client? Make sure, that the Web Client and the RT server are compatible.

  11. Is the zenAdminSrv.exe running as a Service (since 6.21)? Is zenAdminSrv.exe started?​ Also verify the runtime & net services!

  12. Does the PC name where the Web Client is started, appear in the list of active clients (Control panel -> zenon Web Server)?

  13. Does the PC name where the Web Client is started, appear in the CEL of the Runtime server ? (client connected...) 

  14. Has the start page for the web client been added to the secure zone in Internet Explorer? (If not, the web client might work but dialogs are blocked)

  15. Is the "Protected Mode" in Internet Explorer for the Internet zone or local Intranet zone inactive?

  16. When instead of the server name the standby server name is used in the configuration file, a message appears "server names have changed, please restart" each time the Web client is started and after runtime files have been synchronized. Attention! After executing the function "redundancy switch", server / standby server name may be switched permanently in the project.

  17. In version 7.0 the same issue (crash) occurred again, as the setup installed the zenon6.ini again with the following entries: "VBA=1 VSTA=1". If you disable this entries, the Web client should not crash.

  18. Incompatibility with the Data Execution Prevention (DEP) function - Check the user HELP documentation at  Manual -> zenon Webserver and zenon Webserver Pro -> zenon web client -> Browser and follow the steps described there (pasted under):

Attention! when the web client does not load projects, and the black page with green text does not show ( red cross icon top left) then the web client was either not installed or not registered correctly. Try reinstalling it with the .exe provided on the index page. ​

 

Don't forget to run IE as administrator to set the ne​w properties in IE and to run the web client!

 

 

19. DEP in Internet Explorer 10 on Windows 8 x86 - The option "enable memory protection to mitigate online attacks" can no longer be disabled by starting IE as an Administrator. In order to disable, use either the group policy editor (gpedit.msc) or regedit, to add a DWORD value "DEPOff" with the value "1" in "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Interne t Explorer\Main"

 

20. By default with the zenon 7.00 webclient, VSTA ON=1 is set, and VBA EIN=0 is set. When only the VBA 6.3 setup is executed and VBA EIN=1 is set, internet explorer crashes on startup of the browser. Either install also VSTA from the setup DVD (trin_aide.msi), or set VSTA ON=0.

 

Manual registration: 
Go to web client installation folder and open CMD, then type regsvr32 zenWebCli.ocx

 
 

VBA on the Web client can not be executed!

  1. Did you install the web client setup or the webclient_small setup? Attention only the web client setup includes support for VBA/VSTA!
  2. Is VBA + Events in the zenon6.ini activated? -> [VBA]EIN=1/EVENT=1
  3. IE8) on execution of a macro an exception was thrown - > Deactivate "IE->Tools->Internet Options->Advanced->Enable memory protection to help mitigate online attacks ".

 VSTA on the Web client can not be executed

 

1. Following zenon6.ini entries must be set:
[VSTA]
ON=1
CSHARP=1
[VBA]
EIN=1
EVENT=1
2. Is the .NET Framework 3.5 SP1 and VSTA installed?

General Messages in the zenwebsrv.txt logfile 

 

If the following message appears in the webserver log file, a webclient was able to connect to the PC with the webserver, but the PC with the webserver was not able to connect to the PC with the zenon runtime: (firewall or runtime not running)

17.03.09 18:21:30 | NetSrv Info Accept Client IP:10.1.22.146 Ok
17.03.09 18:21:32 | NetSrv Info Client Connection New LAN:CLIENT:CDSBG109.SBG.COPADATA.COM Prio:0 Connection Run RoutePath to Server:CX_004C52 !
17.03.09 18:21:32 | NetSrv Client Connection To Server:CX_004C52 Prio:0 Connect Start!
17.03.09 18:21:34 | NetSrv WINSOCK ERROR--Init Client Socket Failed Connect error #10061
17.03.09 18:21:34 | NetSrv Client Connection To Server:CX_004C52 Prio:0 Connect WaitForReConnect ms:30000!
17.03.09 18:21:40 | NetSrv Client:CDSBG109.SBG.COPADATA.COM Prio:0 Connection closed!
17.03.09 18:21:40 | NetSrv Client Connection Send Endeblock To Server:CX_004C52 Prio:0 !
17.03.09 18:21:41 | NetSrv Disconnect ClientProxy Client:CDSBG109.SBG.COPADATA.COM#CX_004C52 !
If the following message appears in the webserver log file, a webclient was able to connect to the PC with the webserver, but the webserver could not resolve the name of the PC with the zenon runtime: (check name resolution in the network, HOSTS file)

17.03.09 18:19:02 | NetSrv Client Connection To Server:CDSBG016.SBG.COPADATA.COM Prio:0 Connect Start!
17.03.09 18:19:02 | NetSrv WINSOCK ERROR--GetHostByName Failed Server:CDSBG016.SBG.COPADATA.COM Port:1100 GetHostByName error #11004
17.03.09 18:19:03 | NetSrv WINSOCK ERROR--GetHostByName Failed Server:CDSBG016.SBG.COPADATA.COM Port:1100 GetHostByName error #11004
17.03.09 18:19:04 | NetSrv WINSOCK ERROR--GetHostByName Failed Server:CDSBG016.SBG.COPADATA.COM Port:1100 GetHostByName error #11004
17.03.09 18:19:05 | NetSrv WINSOCK ERROR--GetHostByName Failed Server:CDSBG016.SBG.COPADATA.COM Port:1100 GetHostByName error #11004
17.03.09 18:19:06 | NetSrv WINSOCK ERROR--GetHostByName Failed Server:CDSBG016.SBG.COPADATA.COM Port:1100 GetHostByName error #11004
17.03.09 18:19:07 | NetSrv WINSOCK ERROR--GetHostByName Failed Server:CDSBG016.SBG.COPADATA.COM Port:1100 GetHostByName error #11004
17.03.09 18:19:08 | NetSrv WINSOCK ERROR--GetHostByName Failed Server:CDSBG016.SBG.COPADATA.COM Port:1100 GetHostByName error #11004
17.03.09 18:19:09 | NetSrv WINSOCK ERROR--GetHostByName Failed Server:CDSBG016.SBG.COPADATA.COM Port:1100 GetHostByName error #11004
17.03.09 18:19:09 | NetSrv Client:CDSBG109.SBG.COPADATA.COM Prio:0 Connection closed!
17.03.09 18:19:09 | NetSrv Client Connection Send Endeblock To Server:CDSBG016.SBG.COPADATA.COM Prio:0 !
17.03.09 18:19:10 | NetSrv WINSOCK ERROR--GetHostByName Failed Server:CDSBG016.SBG.COPADATA.COM Port:1100 GetHostByName error #11004
17.03.09 18:19:10 | NetSrv Disconnect ClientProxy Client:CDSBG109.SBG.COPADATA.COM#CDSBG016.SBG.COPADATA.COM !
If the following message appears in the webserver log file, a webclient was able to connect to the PC with the webserver, but the webserver was not able to connect to the PC with the runtime server, or the designated project on the PC with the runtime server is not declared a server project, or the runtime is not running.

28.05.09 18:39:45 | NetSrv Info Accept Client IP:192.168.61.103 Ok
28.05.09 18:39:47 | NetSrv Info Send Client:W7-ULTIMATE Prio:0 Access to Write !
28.05.09 18:39:47 | NetSrv Info Client Connection New LAN:CLIENT:W7-ULTIMATE Prio:0 Connection Run RoutePath to Server:CDSBG109 !
28.05.09 18:39:47 | NetSrv Client Connection To Server:CDSBG109 Prio:0 Connect Start!
28.05.09 18:39:48 | NetSrv WINSOCK ERROR--Init Client Socket Failed Connect error #10061
28.05.09 18:39:50 | NetSrv WINSOCK ERROR--Init Client Socket Failed Connect error #10061
28.05.09 18:39:50 | NetSrv Client Connection To Server:CDSBG109 Prio:0 Connect WaitForReConnect ms:600000!
28.05.09 18:39:55 | NetSrv Client:W7-ULTIMATE Prio:0 Connection closed!
28.05.09 18:39:55 | NetSrv Client Connection Send Endeblock To Server:CDSBG109 Prio:0 !
28.05.09 18:39:56 | NetSrv Disconnect ClientProxy Client:W7-ULTIMATE#CDSBG109 !

 

21. There was an issue in older Webserver configuration sites, when a newer IE browser was used. The reason was a missing " in the javascript code. 
The .htm page, which the web clients call, contained the following line : 

document.write (' classid=clsid:2A3BC66B-03D7-11D4-991A-080009ABB492"'); 
This causes a syntax error. after the = and before clsid a " must be inserted. After editing, the line should show like this: 

document.write (' classid="clsid:2A3BC66B-03D7-11D4-991A-080009ABB492"');

22. Make sure that the webclient and the webserver are both configured either for TCP or for HTTP tunnelling. A web client configured for HTTP tunnelling (global_vars.js, HTTP =1) with a webserver configured for TCP, will result in the web client failing to connect and log an error message. "Error during ID-Acquisition"