I am currently facing an issue with my Phoenix Contact Industrial PC running FactoryTalk View ME Station V6.10.00.9(CPR 9 SR 4) at a customer's facility. The terminal was functioning properly at the machine builder's site but now it is unable to open any HMI files. While using FT Diagnostics Viewer, I identified an error message stating "Failed to load FactoryTalk Directory schema for scope "$Local"". This error is causing subsequent issues. I have attempted to create a new runtime but without success. I have the FactoryTalk View install disks available in the panel. Before resorting to uninstalling and reinstalling the software, I am considering exporting the local directory from a working terminal and importing it to the faulty one. I am not very familiar with FT directories and their functionalities, so any advice on this matter would be greatly appreciated. It appears that the issue may have occurred during the power down and shipping process, resulting in some corruption. All other HMIs on the machine are functioning correctly. Would transferring the directory from a working terminal be a viable solution? Thank you for your assistance. Sincerely, Mike
Hello, I encountered a similar issue with a Windows XP computer that had System Endpoint protection installed. Since it is no longer supported, it was causing issues with FactoryTalk. I uninstalled the program, reset the login, and was able to get everything working properly. - Josh
This Windows 7 terminal does not seem to have Endpoint Protection installed. The only software present is FactoryTalk and Microsoft SQL Server. Is there a way to confirm the absence of Endpoint protection on this system? The Windows Firewall is disabled, unlike other terminals where it is enabled. I attempted to completely turn off the firewall to address any potential issues. In the latest development, when I accessed the FactoryTalk Administration Console, an error message stated that the security feature could not run due to the FactoryTalk Local Directory not being configured. I then proceeded to run FactoryTalk Directory Configuration and encountered an error message "Exception from HRESULT: 0x8004206A" when trying to configure the local directory. Additionally, the configuration process failed at the step of setting up an administrator account, with the same error message appearing. A screenshot of the Directory Configuration error is provided. Any insights or solutions would be greatly appreciated. Thank you.
Hi Mike, I noticed the same issue with the System EndPoint icon in the task bar displaying as a green shield divided into quarters. This shouldn't be a problem for you since you're on Windows 7. I was on Windows XP, which is no longer supported. Please try logging back into FactoryTalk. You should find the option in the Rockwell Automation folder. I apologize for not being able to provide more details as I'm currently not at work. Let me know if you need further assistance. - Josh
I successfully accessed the Network Directory, however I encountered an issue when trying to login to the Local Directory, receiving an error message stating "local directory not configured." The Configuration wizard continues to display the same error as previously experienced.
Access the Network Directory and utilize the FactoryTalk Configuration Wizards for your ongoing tasks.
Hi Mike, from what you've described, it does sound like your directory could have been corrupted, possibly due to the power down and shipping process. Transferring a directory from a working terminal is definitely a viable solution. Just make sure to use FactoryTalk View Studio's Application Manager for the exporting/importing process to ensure everything is transferred correctly. If this doesn't solve the issue, a clean software reinstall might be the only recourse. Best of luck!
Hi Mike, It sounds like exporting the directory from a working terminal and importing it to the faulty one could potentially solve your problem. A local directory acts as the central repository for object definitions in FactoryTalk, and exporting/importing the local directory might restore the corrupted or missing information. However, before doing this, I would strongly recommend backing up the current local directory just in case anything goes wrong. If this doesn't work, then reinstallation might be your next best solution. Also, consider checking the network settings, as sometimes incorrect network settings can cause similar issues.
Hey Mike, sorry to hear about your predicament. Transferring the directory from a working terminal could indeed be a viable solution, assuming the configuration of the two terminals is identical. Corrupted FactoryTalk Directories can sometimes be fixed this way. However, before you proceed, I'd recommend backing up any important files just to be safe. Also, remember that communication setup could vary between terminals, so importing a directory might not necessarily fix the issue if it pertains to communication settings. As a side note, making sure your software is up-to-date could prevent similar issues in the future. Best of 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: - This error message suggests an issue with the FactoryTalk Directory schema for the specified scope, which could be causing the HMI files to fail to load.
Answer: - One of the troubleshooting steps could involve exporting the local directory from a working terminal and importing it to the faulty one to potentially resolve any corruption issues.
Answer: - While transferring the directory from a working terminal may be a viable solution, it is essential to consider other troubleshooting steps and ensure compatibility between the terminals before proceeding.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.