Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

Global Script Access Problem

Created by: sbosanquet at: 4/4/2008 11:32 AM (6 Replies)

Rating (0)

Thanks 0

7 Entries

4/4/2008 11:32 AM	Rate (0)
sbosanquet Posts: 2 Rating: (0)	Hello, I wonder if anybody has seen a problem i am having with WinCC and accessing global scripts. We have a client/server WinCC project created in WinCC 6.0 SP3a + HF14. We integrated our smaller WinCC project into a larger multiproject. After the integration the access to global scripts stopped working. Basically, we have a number of screens that access a number of VBS global scripts for database access. On our system smaller system everything was fine and tested. Once we integrated into the large master project access to the global scripts stopped. If we take the contents of these global scripts and paste them into the screens in place of the function call then everything works so it isn't a problem with the script content. We have tried to set up an environment back in the office to try and replicate the problem but unfortunately all the tests have worked without exhibiting the global script access problem. We even have the large multiproject to use for the tests. It has to be something to do with the way in which the Server/clients are configured but i am not sure what this could be. The system is set up with a Win2k3 server running as the WinCC server and the clients are all WinXP SP2. Both client and server are running the same version of WinCC except one is obviously installed as the client and one as the server respectivly. The server and clients all live in the same domain and login is provided by an active directory system. I have a feeling that it will probably turn out to be a permission problem but i am not sure where to go now with testing. On our test system the user has administrative priveleges but on the site system i am not sure what persissions are allocated as we have not set up the actual environment. Has anybody had any similar experiences? Any help is appreciated.
sbosanquet Posts: 2 Rating: (0)
Suggestion To thank Quote Answer

4/4/2008 11:59 AM	Rate (0)
aikona Posts: 487 Rating: (36)	This may not be related but ... We have 5 global scripts running on a 2s cycle .We noticed two problems 1- If we change this 2 s cycle to a 1s cycle then the scripts don't work properly anymore 2- If you change a script while the runtime is running ,the scripts stop working. In the second case we changed script 1 and script 2 stopped working. Even stopping and restarting the runtime did not help .we eventualy stopped WinCC and ( from the windows command line ) we executed the reset_wincc.vbs script and then our problem was solved. I presume that if your script stops working on a client then there could be a timing problem. Eric
aikona Posts: 487 Rating: (36)
Suggestion To thank Quote Answer

4/4/2008 1:47 PM	Rate (0)
Sydney Gold Member Joined: 1/4/2008 Last visit: 9/26/2024 Posts: 703 Rating: (96)	Hello, if the version is WinCC 6.0 SP3a it seems for me it's a part of PCS7 not single WinCC (unless it's Asia version). Anywaythe reason could bethat it's a multiclient project where normally you don't use global scripts from the server but the client has its own project containing system pictures and all the scripts.

Suggestion To thank Quote Answer

4/4/2008 2:31 PM	Rate (0)
sbosanquet Posts: 2 Rating: (0)	During the system test we did try copying the pictures and scripts local but that had the same results as running them on the server, i.e. no global script access.
sbosanquet Posts: 2 Rating: (0)
Suggestion To thank Quote Answer

4/10/2008 10:41 AM	Rate (0)
April Posts: 1776 Rating: (95)	Hi, do you got some informations in the diagnostic files? Maybe you use Tag-prefix and thats the problem?
April Posts: 1776 Rating: (95)
Suggestion To thank Quote Answer

4/10/2008 11:54 AM	Rate (0)
aikona Posts: 487 Rating: (36)	April Hi, do you got some informations in the diagnostic files? Maybe you use Tag-prefix and thats the problem? You can find the diagnostic files under your wincc/diagnostic directory usually "C:\Program Files\Siemens\WinCC\Diagnose" Eric
aikona Posts: 487 Rating: (36)
Suggestion To thank Quote Answer

3/6/2012 8:09 AM	Rate (0)
royIMT Posts: 1 Rating: (0)	Hi! We had a similar problem. We have Windows Server 2008 with three Windows 7 clients. We used the OS Editor to set the base for our project. We work under a company domain (active directory). We have a multi-user project, but we use it referenced (meaning that every client opens the WinCC Project that is stored in the Server i.e. \\<ServerName>\WinCCProjects\<WinCCProjectName>). The global scripts are stored in "SCRIPTFCT". As it turns out, the solution that we could come up with is this: 1) We have a Windows Local Group on the Server named "Developers" (and in WinCC User Adminstrator of our Project, of course). On this "Developers" Group, we included our Domain Users (the domain administrator had previously created Users for us in the domain) 2) We included the "Developers" group on the "Share permissions" tab of the "SCRIPTFCT" shared folder (i.e. Right click on Computer > Manage > Shared Folders > Shares > SCRIPTFCT > Share Permissions) 3) In each Client, the user that is logged in (both PC and WinCC log in) is a member of our "Developers" group and is a Domain User. Voila! The Global Scripts run on every client flawlessly. As I have read in the Documentation, if we had included the Domain Users in the "SIMATIC HMI" and "SIMATIC HMI Viewers" groups on the Server, we could have gained acces to the "SCRIPTFCT" folder as well, but I haven't tried it yet. Hope it helps :D
royIMT Posts: 1 Rating: (0)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Related topics by keywords:

WinCC Scripting

Follow us on