Troubleshooting AssetCentre Initialization Issue with FactoryTalk Directory Backup

Question:

Hello everyone, I have been working on setting up AssetCentre to back up FactoryTalk View SE. In order to do this, I restored a backup from an application and during the process, I selected the option to copy the FactoryTalk Directory. However, it seems that choosing this option has caused an issue in the AssetCentre Client, as I keep receiving an error message when trying to open it. I am unsure how to resolve this issue. Thank you for your help.

Top Replies

If you are seeing an error message stating your client computer is not connected to the same FactoryTalk Directory as your AssetCentre server, it could be because the Client is running on a different PC than the server. Alternatively, if they are on the same PC, restoring may have removed all existing FactoryTalk credentials. To resolve this issue, run the Specify FactoryTalk Directory Location tool on the Client PC. This tool will help connect your client computer to the same FactoryTalk Directory used by AssetCentre.

No, that is not the situation. Both the server and client are running on the same computer. I plan on using the Specify FactoryTalk Directory Location Tool tomorrow to determine the outcome. Thank you for your assistance.

If you are using the same PC, the tool may not be needed. It seems like the FactoryTalk credentials on your PC were replaced when you restored your View SE application. I recommend running the FactoryTalk Directory Configuration Wizard and choosing both Local and Network Directories. When asked for a username, be sure to enter the Windows account username with Admin privileges and its password. If you choose both options, you will need to enter the username and password again. This is the step I suggest taking. OG

Operaghost recommended running the FactoryTalk Directory Configuration Wizard to resolve issues with overwritten FactoryTalk credentials in View SE application. Ensure to select both Local and Network Directories and input the Windows admin account's username and password. If prompted again, re-enter the same information. It's worth trying this troubleshooting step.

Operaghost suggests that if you are using the same PC, you may not need the tool. It is possible that the FactoryTalk credentials on your PC were overwritten when you restored your View SE application. To resolve this issue, try running the FactoryTalk Directory Configuration Wizard and select both Local and Network Directories. Input the user name and password for the Windows account with Admin privileges when prompted. If you select both Local and Network directories, you will be asked to enter the user name and password again. If this doesn't resolve the issue, it may be necessary to troubleshoot further.

Hi there! It does sound like a tricky situation you're in. This issue might be related to a corruption in the FactoryTalk directory or some linking discrepancies after you copied it during the restoration process. Have you tried restoring the backup without copying the FactoryTalk Directory to check if the problem is specifically related to that action? If that resolves the issue, you might need to manually re-establish the connections within your AssetCentre Client instead of copying the directory. Some cleaning of your restored project files might also be necessary. Remember checking the Event Viewer for more specific error messages which might help you dive deeper into this problem.

Hi there! It sounds like a tricky situation you're in. If I understand correctly, you're getting an error in AssetCentre Client after attempting to restore a backup from an application that included a copy of the FactoryTalk Directory. One possibility that comes to mind is that there might have been conflicting information or existing files in the directory that are causing the error. Maybe you could try restoring the backup without selecting the FactoryTalk Directory option to see if the issue persists? If it does work, you'll probably have to manually reconfigure the FactoryTalk Directory, but it could help narrow down where the problem is coming from. Hope this helps and do keep us all updated so we can help you troubleshoot further.

It sounds like there may be a conflict or compatibility issue between AssetCentre and FactoryTalk Directory. To rectify this, you might want to try disabling the copy FactoryTalk Directory option during the backup restoration process, then manually add the required components to AssetCentre. Also, ensure that both software versions are up-to-date as this issue could also arise from version discrepancies. If the problem persists, consider contacting Rockwell Automation's technical support for further assistance.

I've had a similar issue with AssetCentre before. It sounds like the issue might be due to an incorrect configuration during the backup restoration. The FactoryTalk Directory should not normally block the AssetCentre Client from opening. I recommend double checking your restoration steps and the AssetCentre Client configurations. And don't forget to ensure that all required services are running correctly. You could also try re-installing the AssetCentre Client if everything else fails. Let me know if this helps!

More Replies →

Streamline Your Asset Management
See How Oxmaint Works!!

✅   Work Order Management

✅   Asset Tracking

✅   Preventive Maintenance

✅   Inspection Report

We have received your information. We will share Schedule Demo details on your Mail Id.

To add a comment, please sign in or register if you haven't already..   

Frequently Asked Questions (FAQ)

FAQ: 1. What could be causing the AssetCentre Client error after selecting the option to copy FactoryTalk Directory during backup restoration?

Answer: The error in the AssetCentre Client may be a result of a conflict or misconfiguration caused by copying the FactoryTalk Directory during the backup restoration process.

FAQ: 2. How can I troubleshoot the AssetCentre initialization issue related to FactoryTalk Directory backup?

Answer: To troubleshoot the issue, you can try verifying the configuration settings, checking for any conflicting configurations between AssetCentre and FactoryTalk Directory, and ensuring that all necessary components are properly integrated.

FAQ: 3. Is there a specific resolution to fix the error message in AssetCentre Client after backing up FactoryTalk View SE?

Answer: Resolving the error message may involve reviewing the backup and restoration process, examining the settings related to FactoryTalk Directory integration, and possibly reconfiguring AssetCentre to ensure proper initialization.

FAQ: 4. Are there any best practices to follow when setting up AssetCentre for backing up FactoryTalk View SE to avoid initialization issues?

Answer: Best practices may include carefully selecting backup options, verifying compatibility between AssetCentre and FactoryTalk Directory, documenting the configuration process, and testing the backup and restoration procedures to prevent potential issues.

Ready to Simplify Maintenance?

Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.

Request Demo  â†’