Would you be able to test the installation procedure using a nightly build from the master (1.3) branch ? Download from http://www.mantisbt.org/builds.php

Hi, With the latest "MantisBT-1.3.0dev-master-a6a3a13" version is the message obtained.

The base is created but contains only one table.

See the attached file!

thank you

Marking as Suspended

MSSQL support is currently known broken. We are going to be replacing the DB Layer in Mantis to fix this properly after the next release.

I'd strongly advise using MYSQL for now.

The new DB layer already contains the appropriate fixes for MS SQL Support.

We are having the same problems reported by sormiou, both with the stable version and with the latest nightly build.

When is the new release - the one including the needed fixes to the db layer - expected to be ready?

This is a bit difficult for me to check, as I not only do not use nor have access to an MSSQL instance, but also have limited knowledge with this db.

I think the error is due to the fact that Mantis is using unix timestamps internally, which needs to be converted to a format usable by the RDBMS. The ADOdb library converts that to an ANSI SQL standard date format 'YYYY-MM-DD HH:MM:SS', which is apparently not recognized as a date by your DB server.

1. Can you check what is the DATEFORMAT setting ? Please test if it works with if you change it to 'ymd'.

2. Alternatively, can you also check if it works if you make the following change in library/adodb/drivers/adodb-mssql.inc.php, line 79

   • var $fmtTimeStamp = "'Y-m-d H:i:s'";
   • var $fmtTimeStamp = "'Y-m-dTH:i:s'";

Let me know how it goes.

OK, the issue was fixed, but the line had to be adjusted this way:

var $fmtTimeStamp = "'Y-m-d\TH:i:s'";

Thanks

Sorry, forgot the "\".

I'll get that fixed upstream in ADOdb.

Fix committed upstream [1], will be included in ADOdb 5.19 and fixed in Mantis 1.3

[1] https://github.com/ADOdb/ADOdb/commit/09dd1b56bb3c3b006a965460fdce9f659306c063

MSSQL support is currently known broken. We are going to be replacing the DB Layer in Mantis to fix this properly after the next release.

I'd strongly advise using MYSQL for now.

The new DB layer already contains the appropriate fixes for MS SQL Support.

MantisBT currently supports Mysql and has support for other database engines.

The support for other databases is known to be problematic.

Having implemented the current database layer into Mantis 10 years ago, I'm currently working on replacing the current layer.

If you are interested in using Mantis with non-mysql databases - for example, Oracle, PGSQL or MSSQL, and would be willing to help out testing the new database layer, please drop me an email at paul@mantisforge.org

In the meantime, I'd advise running Mantis with Mysql Only to avoid issues.

Thanks
Paul

Definitely should be moved, fix for this is covered in pending pull request https://github.com/mantisbt/mantisbt/pull/181

Issue cloned back into Track DBAL replacement as requested.

My advice to end users is still to wait on upgrading to 1.3 for the new db layer which Victor has said we can do a release of within a month of 1.3

Paul

With ADOdb 5.19 now merged in master branch, this issue should be resolved.