6/20/2024 11:09 AM | |
Joined: 7/6/2020 Last visit: 10/2/2024 Posts: 3 Rating: (0) |
Hello, we are facing a simillar problem. Has anyone perhaps found a solution? Regards, BBurski ------------------------------------------------------------------------------------------ |
Last edited by: Jen_Moderator at: 06/27/2024 12:04:04New subject after splitting |
|
6/27/2024 8:41 AM | |
Joined: 7/6/2020 Last visit: 10/2/2024 Posts: 3 Rating: (0) |
Yes, of course. Our application has two redundant servers using WinCC V7.4 +SP1 + Upd10. The redundancy seems to be working OK, when switching between servers we have the same data on both. The problem arises when a new tag package is generated: In the Archive Manager a new package is generated, the last one gets its name updated: However in SQL Management we see that the name is not updated and the logs show that the server is trying to access the DB by the old name: The database is attached correctly when we move it to the Common Archiving and data is available. What we tried: - Restarting the servers which sometimes additionally results in the necessity to download the entire project (after restarting one of the servers cannot access the WinCC database). After stopping one of the runtimes we saw that some of the database were offline and not disconnected - Downloading the project once again on both servers - actions described here and here: Detach blocking SQL databases after WinCC failure - ID: 109818900 - Industry Support Siemens As both servers are on virtual machines we will try to increase the available memory. |
Last edited by: bjburski at: 06/27/2024 08:42:58Last edited by: Jen_Moderator at: 06/27/2024 12:07:41Links optimized. |
|
7/11/2024 7:40 AM | |
Joined: 7/6/2020 Last visit: 10/2/2024 Posts: 3 Rating: (0) |
Hello Murof, Waiting did not fix the issue, the SQL server tried to access a nonexisting database (due to name change after segment is closed). Our PCS7 (v9.0) is no longer supported so no Service Request was opened, nevertheless we managed to fix the issue. Turns out the problem was not with WinCC, but with the SQL Server and available resources. If anyone has a similar problem in the future this are the steps that helped us: Firstly we increased the total RAM in our servers to 16 GB - 20 GB, depending on the server. Then we followed this instruction for increasing the total available memory and increasing the reserved memory pool: https://support.industry.siemens.com/cs/us/en/view/109812306 Turns out that our SQL servers are so memory hungry that the moment a disruption requiring more resource usage occurred they couldn't do routine tasks. Thanks for your support! bjburski |
Last edited by: Wit_Moderator at: 07/12/2024 12:16:47Link optimized |
|
Follow us on