1/9/2019 2:42 PM | |
Joined: 5/27/2015 Last visit: 3/25/2024 Posts: 60 Rating: (26) |
Dear sarke73, You wrote that you have changed the system name to the old server name. Have you changed that in your project or have you changed the computer name? Because this would not be allowed, see therefore also the FAQ: https://support.industry.siemens.com/cs/ww/en/view/5708281 "You should no longer change the computer name after installing WinCC and after the first call of the SQL server. If you do nevertheless change the computer name afterwards, then you must uninstall the SQL server and re-install it" But it could also be, that you have a defect Alarm Logging segment. I would create a service request and sent the defect project to Siemens so that they can check it. Best Regards |
Last edited by: while(1<2) at: 1/9/2019 3:21:40 PM |
|
1/9/2019 3:54 PM | |
Posts: 3 Rating: (2) |
Hi while thanks for your answer, I did change the name of the server but I did it from the computer properties window of wincc, just clicked "use local computer name" and the error disappeared. Should I reinstall the SQL server because of that or it's just when you change the name of the computer? Regarding the main topic, I tried running the runtime without alarm logging runtime and tag logging runtime and the scada loaded up perfectly. I have a problem with the tag logging runtime too. You say I have a defective alarm logging segment, is there a way to see which one it i or how to fix it? |
1/9/2019 4:17 PM | |
Joined: 5/27/2015 Last visit: 3/25/2024 Posts: 60 Rating: (26) |
Hi If you only changed the computername in the WinCC project then everything is fine and you don't have to reinstall anything. You could check within the project folder the files under: ArchiveManager >> TagLoggingFast >> TagLoggingSlow >> AlarmLogging Within these folders there are the single Segments of your archives. Normally the file names have two time stamps in it. The beginning time and the end time. If you have files which have only one time stamp then this maybe can be a hint that they are corrupt. They also have only one time stamp if WinCC is still writing in these files. What you could do: - Make a backup of your project - Go into the AlarmLogging Editor - Right Click on "Messages" and select >> Archive Configuration >> Reset - Go to the Tag Logging Editor and right click on "Archives" and select: Archive Configuration >> TagLogging Fast >> Reset Archive Configuration >> TagLogging Slow >> Reset Then try to restart your Runtime with Active TagLogging and AlarmLogging. Does this work? !!! Attention !!! the above steps will delete all the archive data of this project. Therefore the backup. If your project will work after these steps then there was a corrupt segment. Best regards |
This contribution was helpful to1 thankful Users |
1/9/2019 9:24 PM | |
Posts: 3 Rating: (2) |
I did the reset on the archive configuration and the the taglogging fast and slow but it didn't work. Before doing this I checked the archive manager folders and found files with only one time stamp, both the .mdf and .ldf files. The good news is that I found the solution at last: even though the Microsoft Message Queuing was installed it wasn't running, I tried activating it manually but it didn't work, so I uninstalled it from Control Panel> Windows Programs and then re-installed it again. Sounds simple, but I was stuck there for 2 and a half weeks. I guess I'll take a rest now. Thanks while(1<2) for giving me a hand, you were of great help. Best regards sarke73 |
This contribution was helpful to3 thankful Users |
Follow us on