SiePortal

The integrated platform for your product selection, buying and support workflow - bringing together Industry Mall and Online Support.

SiePortalDeutsch

Home
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menu temporary not available
- Menue temporary not available
- {{item.title}}

Products & Services
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
MySiePortal MySiePortal
{{(apiData.MySiePortal | filter:{'rank':1}:true)[0].title}} MySiePortal
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Cart ({{apiData.CartCount}})

Navigation

SCADA WinCC7.4 SP1 UPD23 - Spend 1 hour to restart

Created by: Willybong at: 11/27/2024 9:13 AM (2 Replies)

Rating (0)

Thanks 0

3 Entries

11/27/2024 9:13 AM	Rate (0)
Willybong Silver Member Joined: 2/11/2015 Last visit: 9/3/2025 Posts: 510 Rating: (36)	Hi everybody, I've an SCADA WinCC 7.4 SP1 UPD 23 that spends 1 hours to stop-start. Any solution? It have too much values and tagloogings ?¿ What could I do? Thanks in advance, Guillem
	Last edited by: Willybong at: 11/27/2024 09:15:02
Suggestion To thank Quote Answer

11/27/2024 10:45 AM	Rate (0)
ElonksuM_SN_BN Regular Expert Joined: 5/6/2022 Last visit: 7/10/2025 Posts: 589 Rating: (123)	Hi Willybong, In this case, the system may be overloaded with too many values and tag records. Here are some points that can be checked as a first step: - Check memory availability: Make sure that there is enough memory available on the hard disks. Lack of memory can cause the Runtime environment to crash or take a long time to start. -> "Why does SIMATIC WinCC Runtime not start or crash in the startup routine?" - Try to optimize performance: You can use performance variables to monitor and optimize WinCC performance. This can help to identify whether the system is overloaded due to hardware limitations or incorrect script programming. -> "Diagnosing the WinCC system with performance variables" - Check Windows services: Make sure that the "Message Queuing" service is started and set to "Automatic" for the startup type. This service is crucial for the correct functioning of the tag and alarm log. -> "How do I prevent WinCC Runtime from ending after the start screen has loaded?" - Check for corrupted databases: If there are corrupted template databases or inconsistent configuration files, Runtime may crash or take a long time to start. You can follow the steps below to delete and regenerate these files. -> "WinCC Runtime activation hangs during alarm or label logging" These come to mind as first checks. I hope it can help you get started.
	If this Information really helps, you could use the Rate function Thank you.
Suggestion To thank Quote Answer

11/28/2024 11:56 AM	Rate (0)
Murof Platinum Expert Joined: 8/3/2009 Last visit: 9/3/2025 Posts: 16322 Rating: (1930)	Hello Willybong often if the RT start and stop takes very long the SQL Server is taken too long to attach all database segments of ALG and TLG. This means every single segment has to be arrachted or detached at start and stop. If you have too much single segments in your project configured or to large ones this could lead to performance issues of SQL Server. Check https://support.industry.siemens.com/cs/ww/en/view/34473263 also check how many single segments you have in alarm logging and taglogging fast and slow. alkso do not copy anything to common archiving folder. this will attach additionally segments and if not needed this should not be used Bye Murof
	If this Information really helps, you could use the Rate function
Suggestion To thank Quote Answer