Hello everyone, I have encountered an issue with our SCADA system after applying patches to some Rockwell Software. Despite thinking it was unrelated to FT View, I have noticed that restarting servers has caused some issues with Global Object calling. The Objects that fail to load appear to be random whenever I switch pages. Can anyone provide insight into what may be causing this and suggest a solution? Any advice based on personal experiences would be greatly appreciated as I work towards addressing this issue in the future. Thank you for your assistance!
Hey there, Lodd! Have you attempted to delete the data and then copy it from the global object once more? Also, are you receiving any error messages in your diagnostic viewer? Let me know if you need further assistance.
In response to Michoviz's comment, Lodd asked for advice on troubleshooting an error in the global object. Despite attempting to delete and copy it again, the issue persists and even affects new objects created. An error message is visible in the diagnostics viewer which may be connected to the problem. Lodd seeks guidance on how to resolve this error. Grateful for any assistance provided.
This issue may occur if you rename or relocate any global object files or objects in global files. When you export the XML for a display that is affected, you will see instances of global objects with a specific attribute indicating the global object it is attempting to load: Code: linkBaseObject="GLOBAL_FILE_NAME.GLOBAL_OBJECT_NAME".
Cheeseface explained that renaming or moving global object files can lead to issues like the one described. When exporting the XML for a display experiencing this problem, you may notice instances where global objects have a attribute specifying the object it is trying to load, such as: Code:linkBaseObject="GLOBAL_FILE_NAME.GLOBAL_OBJECT_NAME". We have examined the XML files and found no issues with the element mentioned. The problem seems to occur randomly, as sometimes the object loads correctly when revisiting the page, but after repeating the steps multiple times, it fails to load again. Different objects are affected each time this happens.
To address global object problems, start by backing up your project and closing all open displays. Next, if the global object file is labeled as GLOBAL_01, change its name to GLOBAL_02. Open GLOBAL_02, highlight all objects, and copy them. Then, create a fresh global file named GLOBAL_01, paste the objects, and save the file. Lastly, reopen your displays with instances and trigger a save by making a small edit and then undoing it. This process will help resolve any issues with global objects efficiently.
Hi there, it sounds like a challenging situation! I encountered something similar with our SCADA system a while back. From what I learned, these issues with Global Object calling can sometimes be due to tag synchronization problems in FT View. It may also happen if the objects are linked to PLC tags that aren't correctly addressed or online during startup. My suggestion would be to double check your tag addresses and ensure all relevant PLCs are online during startup. You could also consider spreading object loads across multiple screens to avoid overwhelming the system A final thing might be to verify the hardware specifications, as underequipped servers can sometimes cause these kinds of issues as well. Good luck, I hope you manage to fix this issue!
I experienced a similar issue about a month back. It seems like your problem might be due to the cache memory in the FT View. Sometimes after patching, the cache memory may retain some of the old information that conflicts with the updates. To resolve this, clear out the FT View's cache memory/background processing files. Also double check your alarm setup, as sometimes this may also interfere with the normal functioning of your Global Objects. If this doesn’t work, then it might be best to roll back the patches and go through the update process again. Don’t forget to take necessary backups before you do any of this.
Hey there, I had a similar issue with FT View after a patch. It turned out that post-patch, some of the pathnames to the Global Objects were altered slightly, causing inconsistencies and random failed loads. You may wish to double-check your referenced file paths, ensuring they're correctly pointing to the expected locations for your Global Objects. Additionally, ensure Rockwell patches aren't inadvertently modifying your pathnames during the patching process. Good luck!
Hey there! It sounds frustrating to deal with those random issues after applying patches. Based on my experience with FT View, I've found that such problems can sometimes be linked to cache corruption or mismatched versioning between the client and server. It might help to clear the cache or verify that all components are aligned with the same patch level. Also, check if there are any compatibility notes regarding the patches you applied; sometimes, certain updates have known conflicts. Restarting the SCADA server after applying updates instead of just the individual servers might also resolve some of the loading issues. Good luck, and I hope you get it sorted out soon!
Hey there! I’ve faced a similar issue after applying patches to Rockwell software, and it turned out to be related to the way the Global Objects were being referenced. Sometimes, the object paths can get disrupted during updates, causing the random loading failures you’re experiencing. I’d recommend checking the references in your FT View project to ensure they’re intact and also reviewing any recent changes in the patch notes for compatibility issues. If you haven’t already, try clearing the cache or reloading the project to see if that helps. Good luck, and I hope you get it sorted out soon!
✅ 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: Server restarts after applying patches to Rockwell Software may lead to Global Object calling issues in Factory Talk View SE due to potential disruptions in the software environment.
Answer: To address random Global Object loading failures, you may need to review the system configurations, check for any recent software updates, and ensure proper communication between the servers and the SCADA system.
Answer: Some common solutions for addressing Global Object issues in Factory Talk View SE include verifying software compatibility, checking network connectivity, and ensuring proper server configurations to maintain seamless object loading.
Answer: To prevent Global Object calling problems post-server restarts, it is recommended to document software changes, perform regular system backups, and engage in proactive monitoring to detect and address issues promptly.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.