10/17/2014 10:22 PM | |
Joined: 10/3/2010 Last visit: 10/17/2024 Posts: 1562 Rating: (192) |
thanks for your screenshots, although it didn't make me much wiser. I would add a gsc diagnostic window in your picture ( or run apdiag.exe & output window) on both server and client(s) to check possible script errors. It might be related to your sql-coding in vbscript... Just something to try. |
B r g d s , |
|
10/20/2014 6:52 AM | |
Joined: 10/3/2010 Last visit: 10/17/2024 Posts: 1562 Rating: (192) |
also check C:\Program Files\Siemens\WinCC\diagnose\ for possible errors in the log-files. You know, it's quite hard to guess what might be wrong. I assume that your internal tags are working just fine if you manipulate them without scripts? Seems to me that your script has access to your SQL-database when triggered from the client but not when triggered from the server? If your GSC windows doesn't display errors, apdiag sometimes can give extra info indeed. Otherwise, add some trace lines in your script at several places, this way you can monitor the script in GSC window to see if it goes through every critical part from start to finish. |
B r g d s , |
|
Follow us on