Hey there, I'm experiencing issues with ODBC communication on Windows 11 while using FactoryTalk V14.0. I've gone through various forum topics related to this problem. Previously, I had my application running on Windows 7 with FactoryTalk V6.10, which is a local application. I have Datalog models set up with an MS Access MDB ODBC, the same as in V6.10. I've tried using both the 32-bit and 64-bit ODBC versions located in the sysWOW64 and sys32 folders respectively, but none of them seem to be working. I keep receiving error messages like - "Warning: The latest Datalog set 'OdbcDB' in model '****' is inaccessible" and "Unable to access ODBC data source (Failed to connect to data source)." I would appreciate any help in resolving this issue. Thank you in advance.
In order to utilize ODBC datalogs, a DSN must be created using the odbcad32 tool as mentioned. If the Access driver is being used, a database needs to be created as well. To do this, go to the System DSN tab and click "Add." If the Access driver is not available, Microsoft Office or SQL Server Express may need to be installed. After selecting the Access driver, click "Create" to either create a new data source name (DSN) or select an existing one. The DSN serves as the identifier for factorytalk.
Hello Cheeseface, thank you for your input. I have already followed the steps you provided by selecting the existing access *mdb of the project. However, when I try to log in, I encounter an error stating "unable to access ODBC." This issue is quite perplexing and requires further investigation.
It sounds like you're experiencing a tricky yet common issue when transitioning to a new version! Checking on the Windows 11 compatibility with FactoryTalk V14.0 and ODBC could be a good place to start. Also, have you ensured that the right ODBC drivers installed? Sometimes, even when we switch between the 32-bit and 64-bit versions, it may just be a case of the wrong ODBC drivers installed. Remember, your Access database and FactoryTalk need to be running on the same bit version. Finally, you might want to check your ODBC Data Source names to see if they match up with what your application is using. If not, you could adjust accordingly to see if this resolves the issue. Good luck!
Hey there, from what you've described, it seems like you might be experiencing compatibility issues. Have you ensured your system's regional settings are correct? Often, this can impact the ODBC. If that doesn't help, I would recommend you to try reestablishing your ODBC connection from scratch. Uninstall current drivers, reboot your system, and then reinstall and set up the connections again. Windows 11 might have specific requirements for ODBC communication that differ from Windows 7. Also, consider checking if there's an updated version of FactoryTalk compatible with Windows 11, or see if installing any available patches for your current version makes any difference.
From your description, it really sounds like a compatibility issue between FactoryTalk V14.0 and Windows 11. Before diving deep into it, I would recommend checking the Rockwell's compatibility matrix, it is possible that V14.0 may not be fully compatible with Windows 11. Further, ensure that all necessary drivers are updated and properly installed, and permissions are granted where necessary. If you are migrating from a 32-bit system to a 64-bit system, there could be potential issues with the ODBC connections. Also, though you might have already done this, do cross-check if your DSN is set up correctly both in FactoryTalk and in Windows. Another thing that can cause similar issues is a mismatch between the version of Access and ODBC driver, so that's something you may want to look into as well. Good luck!
Hi there! It seems like you've tried a lot of solutions already. Running into ODBC errors like these after updating to Windows 11 from 7 can be tricky to solve. From experience, I can suggest that you check the compatibility of your FactoryTalk version with Windows 11. You might also want to verify that the database file location from your V6.10 setup hasn't changed if you migrated data. If you're assured that everything's compatible and correctly configured, I'd recommend reaching out to Rockwell Automation support for further instructions. FactoryTalk setup can sometimes be intricate and their professional assistance might just do the trick. Hope this helps!
It sounds really frustrating to deal with those ODBC connection issues, especially after a smooth experience on Windows 7. Make sure that the ODBC data source is configured correctly in the ODBC Data Source Administrator; since you’re using Access, double-check that the 32-bit or 64-bit version matches the version your FactoryTalk application is running. Also, try running FactoryTalk as an administrator to see if that helps with the permissions. If all else fails, it might be worth reinstalling the ODBC drivers or checking for any Windows updates that could resolve compatibility problems. 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: To resolve ODBC communication issues, ensure that you are using the correct 32-bit or 64-bit ODBC version located in the sysWOW64 or sys32 folders respectively. Verify the configuration settings for the Datalog models and MS Access MDB ODBC connections.
Answer: Answer: These error messages can indicate issues with the configuration settings, compatibility of ODBC versions, or access permissions to the data source. Check the settings, permissions, and compatibility to troubleshoot and resolve these errors.
Answer: Answer: The changes in operating systems and software versions may require adjustments in ODBC configurations and compatibility. Ensure that the ODBC settings are correctly configured for FactoryTalk V14.0 on Windows 11 to avoid communication issues.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.