InnoDB error- new install on Windows 10 Home

Sage50 Pro 2013

I am currently using a laptop, and trying to move to a desktop.

The laptop was purchased new 9 months ago - was Vista "refurbished" to Windows 10 Home 64-bit before I purchased it.

I installed the program with the offline installer download from this site because the laptop is without  an optical drive. It installed perfectly - and I have had NO ISSUES WHATSOEVER with any data files moved from my crashed old laptop, nor creating a new company to test with, nor with opening any sample data.

Now I am trying to get Sage working on the new desktop (the laptop is being demoted to personal use and will uninstall Sage from it once it's working in desktop)

The desktop was purchased new from Microsoft came with/is also running Windows 10 Home 64-bit. This machine did not exist prior to Windows 10, so it has never had any other OS on it.

It seems to install okay, it seems to restore from my backup okay - I can see the SAI and SAJ folder, but it will not open the company.
I also can not create a new company.
I first installed with the same offline installer download from this site.
I then uninstalled and pulled out our CD and obtained a portable CD drive and installed it from the original CD.
Same error, I then ran "repair" from the CD.

NO Luck!
I've have allowed all the programs in firewall and opened the ports, I have turned off the firewall completely.
I have verified DB connection manager service is running

InnoDB: Operating system error number 87 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: dev.mysql.com/.../operating-system-error-codes.html
InnoDB: File name .\ib_logfile0
InnoDB: File operation call: 'aio read'.
InnoDB: Cannot continue operation.

Is there something from Microsoft for MySQL I am missing or is the Sage50 install (2103, remember) is "self-contained" with its own version of MySQL ? I've found references online re: error 87 to add code to flush the database into my.ini but I can find no such file on the entire computer.

  • 0
    OKAY! I found my answer I couldn't find initially after several hours of looking and dozens of unintall/reinstall attempts all week-end; I even deleted all users and personal data and reset Windows to no avail. The trial 2017 version worked, and I've learned the database functionality is not the same as 2013.

    My post asked about where the my.ini was - I was indeed on the right track!

    Your KB article 21704 dealing with "database engine reported an error"...
    Your "method VII" gave us the answer where it spoke about "Windows Server and the C:\ drive is RAID"
    I was seeing the exact same error and also suspected it had to do with the specific drive, but in my case it's not in RAID.

    In my case it's a Kangaroo Pro - which runs a flash eMMC as the primary drive!
    I woke up this morning with an epiphany - my next test would have been to try to move the restored company (it restored but wouldn't open it) to the secondary dock drive (which *IS* a spinny HDD).

    Pleased to report that "innodb_flush_method=normal" was the solution now that I know where it goes! This allows me to keep my current company data on the primary drive. I am just as !!!Happy-as-a-Clam!!! that I won't need to lug the larger storage drive/dock around all the time!

    So there you go - maybe you wish to add to your database in case this wave of teeny Windows machines catch on...
    Method 7 may also work for data on eMMC (flash) drives.
  • 0 in reply to JJD
    Just out of curiosity, is the primary hard drive larger than 2 TB in size and or formatted as a GPT partion, if so then this article may be of help to you or others with similar problems

    bugs.mysql.com/bug.php

    Just to clarify this is a MYSQL issue and is not related to any software problems with Microsoft or Sage
  • 0 in reply to Ginkgo Bike
    ROFL! No, it's a mere 32 GB (and only 2GB RAM) - chosen for ultra portability.
  • 0 in reply to JJD
    Here's an odd thing though -
    MySQL docs say "Prior to MySQL 5.1.24, the default innodb_flush_method option was named fdatasync"

    How is this option having any effect then if 2013 uses a 5.0.x version ?