Author Topic: Don't update Crossover to v. 17 if you use MySQL  (Read 138 times)

jleecbd

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Don't update Crossover to v. 17 if you use MySQL
« on: December 08, 2017, 06:52:07 am »
I upgraded to Crossover 17 the other day.  Although the ODBC connection tests successfully, when you try to connect to the DB within EA, you get a generic 0x80004005 error and you can't connect.  I've submitted this to both Sparx and Codeweavers.  I'll update if I actually get a response from either.  I deleted all of my bottles and completely reinstalled everything in 17, but no change.  Downgrading to 16 has resolved the problem so that is where I'm stuck for now.


Simon M

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 6200
  • Karma: +47/-5
    • View Profile
Re: Don't update Crossover to v. 17 if you use MySQL
« Reply #1 on: December 08, 2017, 08:28:03 am »
I'd be curious if you have the same issue using Wine directly.

I don't have any recent experience using Crossover, but I know that if I update Wine I always need to run winetricks --force mdac28 before ODBC connections will work for me. (That's on the latest stable versions)
Simon

support@sparxsystems.com

jleecbd

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Re: Don't update Crossover to v. 17 if you use MySQL
« Reply #2 on: December 09, 2017, 05:04:23 am »
Sparx support suggested that I add a library override for library mtxdm to native.  This requires that you reinstall MDAC.  That appears to have fixed the problem.