SIMATIC WinCC
Error in WinCC CAS
Thread Starter: nmnogueira Started: 8/24/2011 2:06 PM Replies: 7
8/24/2011, 2:06 PM
|
Joined 3/15/2010
Last visit: 5/2/2013
Posts: 128
Rating:
![Rated: Excellent [4.4 out of 5 / rated 5 time(s)].](/forum/Skins/images/Star4Half.user.gif) (5)
|
![Rated: no ratings [0 out of 5 / rated 0 time(s)].](/forum/Skins/images/Star0.post.gif) (0)
|
Dear all
I have a problem with WinCC CAS. I have 2 redundant servers and one archive server, and the archiving is not working. The following message appears in the operation alarms:
Message number: 1012252
Event: "AM:SCADASERVER2:Backup:Error on writing to backup path"
Infotext: "Backup:invalid path for type TLG_F:\\Scadaserverhis\ArchiveDir\* !"
I can open the shared directory so the problem should be related to share permissions.
I had this working but now it's not working anymore, and I don't know why! 
Thank you
|
|
|
|
7/14/2012, 6:35 PM
|
Joined 7/14/2012
Last visit: 2/6/2013
Posts: 2
Rating:
![Rated: no ratings [0 out of 5 / rated 0 time(s)].](/forum/Skins/images/Star0.user.gif) (0)
|
|
(0)
|
Did you ever figure out what went wrong. Because I have just noticed the same problem
|
|
|
|
7/16/2012, 1:28 PM
|
Joined 3/15/2010
Last visit: 5/2/2013
Posts: 128
Rating:
(5)
|
|
(0)
|
I still have the same problem, and I am struggling with Siemens to get this solved. I managed to get remote assistance from Siemens Germany and apparently they came to the conclusion that it was because the WinCC servers had not finished synchronization successfully. Because at the time I only had one of the servers with me, I tried to test this by removing the redundancy in the project, and it worked correctly.
Now, after almost 1 year, I finally have the two servers and the archive server in the final configuration, and was able to test that theory. Unfortunatly it still doesn't work, and I still receive the same message even after the servers finish synchronizing  .
|
|
|
|
8/15/2012, 11:33 AM
|
Joined 5/29/2012
Last visit: 3/4/2013
Posts: 2
Rating:
(0)
|
|
(0)
|
We have the same problem on a system with redundant servers and CAS.
It looks like something to do with network shares or folder permissions.
In the archive configuration I added an alternative destination path and selected to backup to both paths.
If the alternative path is a folder on the local disk, the files are copied to that folder OK.
If the alternative path is a network share, the files are not copied and the same error message is logged for both paths
|
|
|
|
8/16/2012, 10:51 AM
|
Joined 3/15/2010
Last visit: 5/2/2013
Posts: 128
Rating:
(5)
|
|
(0)
|
My problem was probably different, because WinCC wouldn't even write to a folder in the same computer. I finally have it working, after installing the latest update to WinCC  .
To check the permissions try to manually create, from the server, a file in the backup path. Also make sure that you have the backup server name and IP defined in the Windows hosts file.
|
|
|
|
|
Thank you for this post from:
|
10/9/2012, 4:03 PM
|
Joined 3/15/2010
Last visit: 5/2/2013
Posts: 128
Rating:
(5)
|
|
(0)
|
My archive backup stopped working again about a month ago, without any good reason . Now, besides showing the "Error on writing to backup path", I don't even receive the messages from the CAS in the OS servers. Today I installed Update 8 to WinCC v7.0 SP2, but the problem still remains.
Note that if I manually copy the archive files to the CAS folder, the archives are processed and inserted in the CAS database.
Heeeeeelp!
|
|
|
|
10/29/2012, 3:09 PM
|
Joined 3/15/2010
Last visit: 5/2/2013
Posts: 128
Rating:
(5)
|
|
(0)
|
For the record, I managed to solve the problem. Apparently it was because I was using Remote Desktop to access the servers. Even if the server project started automatically, as soon as a RDP connection is established it "breaks" something in the server redundancy.
Now I use VNC to access the servers and it is working fine. Avoid Remote Desktop at all costs!
|
|
|
|
|
Thank you for this post from:
|
12/20/2012, 1:46 PM
|
Joined 5/29/2012
Last visit: 3/4/2013
Posts: 2
Rating:
(0)
|
|
(0)
|
Thanks nmnogueira. I did some tests and found that the copying of the data to the CAS starts working again if the local console is logged back in after the RDP session. Now I still use remote desktop but instead of just closing the RDP window I run a batch file on the server which logs the local console back in. The batch file includes:
tscon.exe 0 /dest:console /v
where 0 is the ID of the user which is normally logged in on the server.
Thanks again
Kenny
|
|
|
|
|
Thank you for this post from:
|
Actions
Print