0009798: Unable to perform Mantis upgrade from 1.1.2 to 1.2.0a2 MSSQL(SQL 2005 Express) - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update
0009798	mantisbt	db mssql	public	2008-11-10 12:49	2014-05-16 15:00

Reporter	bkraul	Assigned To	grangeway
Priority	normal	Severity	crash	Reproducibility	always
Status	closed	Resolution	no change required
Platform	i386	OS	Microsoft Windows Server	OS Version	2003
Product Version	1.2.0a2

Summary	0009798: Unable to perform Mantis upgrade from 1.1.2 to 1.2.0a2 MSSQL(SQL 2005 Express)
Description	have tried unsuccessfully to upgrade my mantis installation from 1.1.2 to 1.2.0a2, using MSSQL (SQL 2005 Express) . None of the approaches I tried seemed to help.Upgrade did not work at all, erroring out when trying to run the database upgrade script, with syntax errors, etc. I even tried to do a clean MSSQL install, to no avail. Even when manually editing the SQL script generated by the upgrade to comply with MSSQL and running it, my installation keeps complaining with the following: APPLICATION WARNING #user_get_field() for NO_USER: WARNING: Admin directory should be removed. ERROR: The database structure appears to be out of date(config(databaseversion) is 0 and old upgrade tables do not exist). Please check that your database is running - we can not retrieve the database schema version. Config Table did not return a valid database schema version - please ask for support on the mantis-help mailing list if required.
Steps To Reproduce	1.Perform a clean 1.1.2 install using MSSQL. 2.Attempt to upgrade to 1.2.0a2 using MSSQL.
Additional Information	Is there anything special schema-wise in 1.2.0a2 that I need for getting this to work? Install with mySQL database works normally, but it seems MSSQL does not. I tried looking for answers in the forums, but could find no info. Mantis 1.1.2 has been working great with MSSQL, so I don't understand what has changed so radically in 1.2.0a2 that makes it not work.
Tags	No tags attached.

thraxisp 2008-11-10 13:48 reporter ~0019833	This could be similar to bug 0008846. How was the database originally created? There are instructions in the bug notes to all the missing record to the database.

bkraul 2008-11-10 14:03 reporter ~0019834	The database was originally created in a clean install of 1.1.2, with mssql. As stated, 1.1.2 runs fine, I have even upgraded to 1.1.4 since, and there are no problems whatsoever. But when it comes to 1.2.0a2, things seem to change, at least when using mssql, the upgrade scrips fail, saying that it could not find upgrade tables, scripts come up with syntax errors, and the result is that I am unable to log in. I took a look at the related issue you mention, and while I did encounter some of the errors that it talks about (and corrected them, making the SQL script run fine), mantis still kept telling me the schema does not match. Also, I noticed the related issue has no relationship to mssql, only mysql.

thraxisp 2008-11-10 14:31 reporter ~0019835	The problem seems to be a missing db record giving the database version. The workaround in the related issue (recreating the database record) should also work for you. INSERT INTO mantis_config_table ( value, type, access_reqd, config_id, project_id, user_id ) VALUES ('52', 1, 90, 'database_version', 0, 0 ); I wanted to see if we had fixed the root cause.

cbasset 2009-06-22 08:06 reporter ~0022216	I'm having the very same issue when trying to migrate from 1.1.5 to 1.2.0a3. I can't perform the suggested insert as there is already a value of '63' in the database.

cbasset 2009-06-22 08:09 reporter ~0022217	It may be specific to MS SQL Server as I'm also using this database engine. It's quite annoying as it disables the access to the admin tools and thus the migration tools.

bkraul 2009-06-22 10:05 reporter ~0022219	As a followup. I decided a while back to move back to using a mysql backend. Everything has been working OK since then.

grangeway 2012-02-05 14:24 reporter ~0031141	Doing a bit of tidyup on the issue tracker atm - 1.3.x when it gets released should have better support for mssql, especially now that MS have done some work on php.

grangeway 2014-05-16 15:00 reporter ~0040371	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