• Announcements

    • turbofandude

      Proper Problem Reporting for the TFDi Design 717   07/09/2017

      Folks, As the user count is increasing, it is becoming more of a task for us to stay on top of problem reports. We are also receiving an increasing amount of incomplete reports that we are unable to follow up on (which frustrates everyone, us included). On that note, we are going to be enforcing a stricter formal problem reporting system. There are a few main points that need to be addressed. ALL problem reports must be submitted via the Bugs and Suggestions system. Open discussion on the forums is fine, but our team simply cannot respond to every single comment (especially when the majority of doing so is asking for information the Bugs and Suggestions system already asks for). Incomplete reports will be ignored. This means reports like "my FPS is bad" will not be given weight. This isn't because we don't care. It is because a report like that does absolutely nothing for anyone - we can't fix it based on that. Please include EVERYTHING you can possibly think of regarding the problem and take as many steps as you can to isolate it. Prepar3D v4, despite what you have heard, can still be unstable. Yes, it is definitely possible to fly flights without issues. But it is still relatively new, as are most of the addons available for it. Please refrain from attacking us or other developers because of this. We have already had one scenario where a 717 CTD was resolved by an update to Prepar3D itself. This is likely not the only time that will be the case. You are still free to report the crashes, as it may help whoever the developers of the faulting code are solve the issue. Duplicate reports will be deleted/merged. For the sake of sanity for us trying to prioritize and evaluate issues, if we discover multiple reports of the same thing, we may merge/delete the duplicates. We strongly encourage you to search and see if your problem has been reported before. Thank you all in advance. This may seem overbearing, but this is the only way we are going to be able to stay on top and continue heading in the direction we, and the community, want.
Sign in to follow this  
pjr191

Unable to load odbcji32.dll

Recommended Posts

Just updated to the latest version and I am now getting the following error,

Unable to load odbcji32.dll

When will this issue be finally fixed ?

Many thanks.

Share this post


Link to post
Share on other sites

No the solution did not help, I am still getting the same errors. The registry key for the value mso.dll is not present before or after the install of the 64-bit AccessDatabaseEngine_X64.exe  in passive mode.

Share this post


Link to post
Share on other sites

Here is how I managed to fix the above issue, maybe it will work for someone else too.

To repair the Microsoft Access Database Engine 2010 component

Go to Control Panel --> Programs and features

Search for Microsoft Access Database Engine 2010

Right-click on it and select the option Repair

Share this post


Link to post
Share on other sites

All was fine with me until the latest update to 1.09.15.

 

Now getting this error.  The 'repair' solution above did not resolve the issue.

I also did a complete uninstall / reinstall of the 717 and the Addon Manager and that did not fix the problem either.

Share this post


Link to post
Share on other sites

Any luck with this Rich?  I;m in the same boat.  I've done the repair steps with the passive switch multiple and still have the odbcji32.dll message on startup.  Not certain where to go from here.  Used to love to fly the 717, since the last update its grounded:(

Share this post


Link to post
Share on other sites

I got it going.  Secret for me was to be certain no 32-bit office app was run before removing the registry entry at the end of the fix instructions.  If you try to run word or excel, a setup will want to run and that little setup breaks the 64-bit access run-time.  So first, uninstall the Access 2010 run-time and then follow all the steps in the instructions above before you do anything with any 32-bit office app.  If you do mistakenly run an office app, you have to uninstall the access run-time again and start over with the fix instructions.

John

  • Thanks 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this