MySQL was developed from the Unix/Linux Open Source world, and generally requires direct (SCSI) access to its disk storage. It can work with most filesystems, or even with raw, unformatted disk space, but it's not surprising to me that it doesn't work with a new Microsoft disk system.

This:

http://www.independent-software.com/mysql-error-1067-windows-error-87-error_invalid_parameter/

and this:

http://bugs.mysql.com/bug.php?id=28913

suggest that adding this:

1	innodb_flush_method=normal to the database configuration file may help.

(This is a peer support forum, and I am not connected with Sage software in any way.  You can try this, but the standard Open Source warranty applies -  if something breaks, you keep both pieces.)

MySQL was developed from the Unix/Linux Open Source world, and generally requires direct (SCSI) access to its disk storage. It can work with most filesystems, or even with raw, unformatted disk space, but it's not surprising to me that it doesn't work with a new Microsoft disk system.

This:

http://www.independent-software.com/mysql-error-1067-windows-error-87-error_invalid_parameter/

and this:

http://bugs.mysql.com/bug.php?id=28913

suggest that adding this:

1	innodb_flush_method=normal to the database configuration file may help.

(This is a peer support forum, and I am not connected with Sage software in any way.  You can try this, but the standard Open Source warranty applies -  if something breaks, you keep both pieces.)

Thanks for the reply. Where do I find the database configuration file in Sage Simply Accounting (I am using Simply 2011 pro)?.
Thanks

What version of Sage 50 are you running, some of the earlier versions did not like large drives (1 TB and larger), the more recent versions now have no problem with them. This was due to some sort of issue in the MySQL database engine that was used.