Good afternoon, Earlier today, I was working on FTView Studio and making adjustments to a client's settings. After changing the horizontal position animation of an object, I encountered an error message when trying to reopen the client: 'Files missing or not installed'. Despite multiple attempts, the client only loaded properly on the third try, but subsequent attempts resulted in the same error message. Event Viewer did not show any errors, except for two warnings related to the ActiveX file for alarms being the wrong version. These errors were present before the client stopped working, so it's unclear if they are connected to the issue. The alarms and events server is still functioning, and other clients on different PCs are operating normally. The issue seems to be isolated to this particular client on one desktop. Thank you for any assistance.
In order to resolve technical issues with your HMI system, start by restarting both the HMI Server and HMI Client. If the problem persists, consider troubleshooting by either repairing or uninstalling the client software before reinstalling it.
Thank you for your response. We may need to temporarily shut down in order to address this issue, so we are hoping to find an alternative solution.
Hey there! It certainly sounds like you're dealing with a layered issue. If other clients are functioning normally, I'd first ensure that the version used on the problematic desktop matches those in the stable environments. Consider reinstalling FTView Studio on that particular desktop. Regarding the ActiveX file, even though the warning appeared before your current issue, it could still be partially responsible. Try updating or reinstalling it. Sometimes, these vexing problems are just due to temporarily corrupted files. Finally, double-check the path of the missing files. If they’ve been moved or renamed, it could well cause an error message like the one you're seeing.
From your description, it sounds like there may be a problem with the file version or with the installation itself on that particular desktop. Try reinstalling FTView Studio on the affected desktop, ensuring that you have the correct and latest version. You could also check if the ActiveX file is correctly installed and updated since you did receive a warning related to it. Sometimes, even when the Event Viewer does not directly indicate an error, interrelated issues can throw off the software's functionality. It's always worth ruling out.
I experienced a similar issue a couple of months ago and realized it happened due to certain files being blocked by my antivirus software. If you have any installed, try to temporarily disable it and see if the problem persists. Such software can sometimes identify and block certain files connected to FTView Studio during an update or settings adjustment. Also, ensure your ActiveX file for alarms is updated to the correct version. The problem might seem unrelated, but it could be affecting other operations as well.
It sounds like a frustrating situation! Since you're getting that error specifically on one client, it might be worth checking the configuration files for any corruption or mismatched versions, especially since the warnings regarding the ActiveX file could indicate a versioning issue. Additionally, have you tried clearing any temporary files or caches related to FTView Studio? Sometimes, leftover files from previous sessions can cause strange behaviors. If the client only works sometimes, you might also want to check your permissions and make sure there aren’t any restrictions affecting that specific desktop. 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 error could be caused by missing or improperly installed files related to the client's settings or configuration.
Answer: Answer: You can start by checking the installation of necessary files, verifying the configuration settings, and ensuring compatibility with ActiveX components.
Answer: Answer: While the warnings about the ActiveX file for alarms being the wrong version may not directly cause the client loading issue, it's recommended to address any discrepancies in file versions to prevent potential conflicts.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.