Hello, I am currently using FT View version 12 to receive alarms from my PLC system. Initially, everything was working smoothly and the Alarm and Event History server was populating correctly. However, there seems to be an issue now. While my FT application and the separate WIN-911 system are both detecting active alarms, the Alarm and Event History server is not updating with the new data. I am unsure if the problem lies with FT View not writing the alarms properly or if the SQL server is not reading them in. I have made sure that the Alarm and Event History feature is still enabled in the FT application. Can anyone offer insight on what might be causing this issue or provide guidance on troubleshooting it effectively?
I am facing the same problem, have you discovered a solution for it yet?
An update on the issue at hand: Upon monitoring the SQL service activity on my alarm and event server, it was identified that no insert queries were being written to the SQL database. Following a re-build of the server, it is now functioning flawlessly.
User mony9909 provided an update on the issue at hand. Upon monitoring the SQL service activity on their alarm & event server, there were no insert queries being written to the SQL database. Following a rebuild of the server, the issue has been resolved and everything is now functioning correctly. Can you please provide a step-by-step guide or share a screenshot on how to do this?
Hey there, you've got a fine puzzle on your hands. It could very well be a case of a corrupted database or indexing issue with the Alarm and Event History server resulting in it not updating. However, an inconsistency between FT and SQL client protocols may also cause such problems. One approach you could take is to ensure both FT and SQL are using common protocols. You can also consider repairing or rebuilding the database on the Alarm and Event History server to fix any potential corruption. Logs can also be resources of invaluable information when troubleshooting these issues. Good luck and let us know how it goes, or if you need more help, we're here.
This might be due to a delay or miscommunication between your FT View and SQL server, which might result from network instability or a high workload in either of the servers. Start by checking the data logs to see if there is any error message during the period the alarms stopped getting updated, this might point you straight to the problem. Then, check the connection status between the PLC system, FT View, and SQL server. Also, try to restart the Alarm and Event History server to see if the problem persists. Additionally, it might be beneficial to streamline your SQL server and check if it’s properly optimized to handle high volume data. If everything looks fine, I'd consider reaching out to Rockwell's technical support. They can probably guide you through more advanced diagnostic procedures.
It sounds like you're dealing with a frustrating issue! One thing you might want to check is the configuration of your Alarm and Event server to ensure that it’s properly set to log events in real time. Sometimes, filters might be applied that prevent certain alarms from being logged. Additionally, look into the SQL Server connection settings; if there's a connectivity issue or something misconfigured there, it could prevent the data from being written correctly. You could also enable any relevant logging within FT View to see if any errors are being reported when alarms are triggered. This might give you a clearer picture of where the breakdown is happening. Good luck!
It sounds frustrating to deal with that! Since the FT View application is detecting alarms but the Alarm and Event History is lagging, it might help to check if there are any connection issues between FT View and your SQL server. Sometimes, a simple restart of the SQL server can refresh the connection. You should also look into your event filter settings; if they were inadvertently changed, it could affect what gets logged. Lastly, checking the logs for any error messages on both ends might give you more clues about where the breakdown is happening. Good luck!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: Answer: The issue could be related to FT View not writing the alarms properly or the SQL server not reading them in. Further troubleshooting may be required to pinpoint the exact cause.
Answer: Answer: To effectively troubleshoot this issue, you can start by verifying if the Alarm and Event History feature is still enabled in the FT application. Additionally, checking the communication between FT View, the PLC system, and the SQL server for any potential errors or misconfigurations could help identify the root cause.
Answer: Answer: It is important to ensure that all components, including FT View, the PLC system, and the SQL server, are properly configured and communicating seamlessly. Checking for any recent updates or changes that might have affected the system's functionality could also be beneficial in resolving the issue.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.