Hello, I recently updated my FTV ME file by adding an "ack-all" button and then downloaded it to my PVP. Since then, I have been encountering an error message during the application startup process. The error states: "Application RSLinxNG.exe has encountered a critical error and needs to close." After the error message, the application loads up, initially showing the main screen, but then automatically switches to the alarm history screen. This issue has occurred despite not making any other modifications to the application. I have attempted to resolve the error by deleting the application, recreating the .mer file, and re-downloading it, but the problem persists. Even reverting the change and re-downloading the file does not resolve the issue. Is anyone familiar with this error and has encountered it before?
Make sure you have the "replace communications" option checked when downloading. If it's not already selected, be sure to check the box before downloading the file again. This simple step can help ensure seamless communication integration within your system.
Yes, I will attempt to recreate the entire link tree structure. Let's rebuild the entire network of links.
I rebuilt the entire link hierarchy from the ground up in both design and runtime, avoiding the use of the 'copy to runtime' button due to potential issues it may cause. This decision was made to prevent any problems that could arise, as I have observed it to be the possible culprit in these situations.
Tried re-flashing the firmware once more, but unfortunately, there was still no improvement.
When creating a .mer file, it's important to ensure it is at the same revision level as the original to avoid potential crashes. I remember encountering a similar issue years ago with RSLinx when uploading a v7 file and converting it to v9 or v10 for a panel with that firmware. Recreating the file at the original lower revision level helped resolve the problem efficiently. Remember to double-check revision levels to prevent compatibility issues.
It sounds like you've tried a comprehensive set of solutions already. The issue could be related to a missing or corrupt .dll file associated with the RSLinxNG.exe executable. I would suggest trying to repair or reinstall the Rockwell Automation software. If that doesn't work, backup your configurations and try a fresh installation of the software. Do remember to update directly from Rockwell's website to ensure you have the most recent and stable version. It's quite odd that the application doesn't crash but switches screens - it might be a good idea to engage Rockwell's technical support if the problem persists. Just remember to document everything you've done so far, it would make troubleshooting much easier for the support team.
✅ 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: The error could be related to the recent update made to the FTV ME file, such as adding the "ack-all" button. It's possible that this modification triggered the critical error during the application startup process.
Answer: You can try resolving the error by deleting the application, recreating the .mer file, and re-downloading it to the PVP. Additionally, reverting the recent change made to the FTV ME file and re-downloading the file might help troubleshoot the issue.
Answer: The automatic switch to the alarm history screen after initially loading the main screen could be a symptom of the critical error encountered during the application startup process. This behavior might be related to the root cause of the issue.
Answer: It's possible that other users have encountered similar errors on their PVP devices. Sharing experiences and potential solutions within relevant forums or
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.