Following software updates, we upgraded our systems to FactoryTalk Service Platform 6.31 and applied a patch roll up on Dec 22. Our network-connected Alarm and Event DB, which has been functioning without issues for years, started experiencing problems after the update. While active alarms are working as expected, the alarm history stopped logging after the upgrade from FTSP 6.30 to 6.31. An error message in the event viewer appears every couple of minutes indicating an issue with executing SQL statements. This problem is affecting both older FTView SE ver 12 Network Station HMI's and newer FTView SE Network Distributed HMI systems. Although we have reviewed relevant Knowledgebase articles, we have not found a solution specific to our version of FTSP (6.31) or the error message we are encountering. If anyone has encountered similar issues following software updates, we would appreciate any insights or suggestions.
Encountering database connectivity issues? Make sure to review the paths. If you're unfamiliar with Alarms and Events, navigating to the communications tab in the project and runtime settings, similar to FT View Studio, is a good place to start troubleshooting the path verification.
I have confirmed that the settings in the admin console connections, alarm and events server settings, and SQL database settings remain unchanged after the updates.
Have you found a solution?
I've had a similar issue after upgrading to FTSP 6.31. Based on my experiences what really helped was tweaking some SQL Server settings. Ensure that your SQL Server instance is tuned properly - in particular, check if the database Auto-Growth property is set properly and that autogrow is not taking too long due to disk limitations. Apart from that, you might want to look at FTSP log files and Event Viewer for further clues. If you're still stuck, reaching out to Rockwell Automation technical support could be a useful step, they've been really helpful for me in past crisis situations.
It sounds like a classic case of an update causing issues with an established system. In my experience, such issues sometimes arise due to conflicts between software versions or compatibility aspects not yet fully resolved by the software provider. Since you are getting an error message related to SQL execution, I'd recommend checking the SQL Server settings post-update. Additionally, you may want to cross-verify if there are any altered database schemas or changes in the database properties. For FTSP specifically, I'm not entirely sure about version 6.31, but I've dealt with a similar situation in version 6.20 where the alarm log service needed to be restarted. I understand you've already searched in Knowledgebase articles, but perhaps reaching out to Rockwell Automation support directly might provide more comprehensive assistance. Hope this helps a bit and do share any progress or solution you find!
I've experienced similar issues when upgrading FTSP in the past. It sounds like you might have a problem with the SQL statements, causing the error message and preventing your alarm history from logging. Try troubleshooting the SQL statements first. Also, have you checked whether the most recent patch roll-up is fully compatible with the version of FTSP you're using? I'd suggest double-checking that aspect as well. Lastly, when you did the upgrade, ensure you have followed each step accurately and not missing out on any minor detail. Sometimes, a seemingly insignificant skipped step can cause havoc too.
It sounds like a frustrating situation, especially after relying on the system flawlessly for so long! Have you checked the SQL server connectivity and permissions since the update? Sometimes, patches can inadvertently alter configurations or permissions that affect database access. Also, it might be helpful to look for any logs generated by the database itself for clues on what's causing the execution errors. If the issue persists, reaching out to Rockwell Automation support directly could yield insights specific to the patch and version you're using. Good luck!
It sounds frustrating to deal with those issues after an update, especially considering how long the system had been stable. Given the SQL error messages you're seeing, it might be worth revisiting the database connection settings or checking user permissions since those can sometimes get reset or altered during updates. Also, you might want to see if there's a compatibility patch or an additional hotfix released specifically for FTSP 6.31, as such updates often follow major releases to address bugs like the one you're experiencing. In the meantime, reaching out to Rockwell's support could also provide some direct insights, as they might have encountered this with other users. 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: It seems like the upgrade may have caused a problem with executing SQL statements, resulting in the history logging issue. You may need to troubleshoot the SQL execution error and possibly check for compatibility issues with the new version.
Answer: While there might not be a specific solution documented for FTSP 6.31, you could try reaching out to Rockwell Automation's support for assistance. They may have insights or workarounds for the issue you are facing.
Answer: Ensuring compatibility between the HMI systems and the upgraded FTSP version is crucial. You may need to check for any known compatibility issues, update drivers or software components if necessary, and verify configuration settings to ensure smooth operation.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.