0013905: Application Error #401 on summary_page.php - MantisBT - Signup temporarily disabled due to spam

ID	Project	Category	View Status	Date Submitted	Last Update

0013905	mantisbt	db mssql	public	2012-02-16 10:21	2015-03-15 19:58

Reporter	portalsoft	Assigned To	dregad
Priority	normal	Severity	crash	Reproducibility	always
Status	closed	Resolution	fixed
OS	Windows Server 2008	OS Version	R2 Enterprise
Product Version	1.2.9
Target Version	1.3.0-beta.2	Fixed in Version	1.3.0-beta.2

Summary	0013905: Application Error 0000401 on summary_page.php
Description	When Summary link on main menu is clicked, the following error message appears: APPLICATION ERROR 0000401 Database query failed. Error received from database was #0: [Microsoft][ODBC SQL Server Driver]Invalid parameter number for the query: SELECT b.id, b.date_submitted, b.last_updated, MAX(h.date_modified) as hist_update, b.status FROM mantis_bug_table b LEFT JOIN mantis_bug_history_table h ON b.id = h.bug_id AND h.type=0 AND h.field_name='status' AND h.new_value=? WHERE b.status >=? AND project_id=1 GROUP BY b.id, b.status, b.date_submitted, b.last_updated ORDER BY b.id ASC.
Steps To Reproduce	Login to Mantis Report two issues Go to Summary page (main menu -> Summary link) -> Application Error 0000401
Additional Information	Environment: Windows Server 2008 R2 (build 7601: service pack 1) IIS 7.5 (7.5.7600.16385) MSSQL Server 2008 PHP 5.3 (php-5.3.10-nts-Win32-VC9-x86) PHP MSSQL driver (SQLSRV20) mantis 1.2.8-master (mantisbt-1.2.8-master-1.2.x-5e9ead3)
Tags	No tags attached.

herick.marques 2012-12-11 07:18 reporter ~0034527	Same error here. APPLICATION ERROR 0000401 Database query failed. Error received from database was #-1:ERROR: column "b.category_id" must appear in the GROUP BY clause or be used in an aggregate function" para a consulta: "SELECT COUNT(b.id) as bugcount, c.name AS category_name, category_id, b.status FROM mantis_bug_table b JOIN mantis_category_table AS c ON b.category_id=c.id WHERE b.project_id=1 GROUP BY c.name, b.status ORDER BY c.name" Environment: Ubuntu 12.04 LTS Postgres 8.4 PHP 5.3.10 Mantis 1.2.12

grangeway 2014-02-17 13:26 reporter ~0039440	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.

grangeway 2014-03-27 19:12 reporter ~0039766	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.

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

dregad 2015-03-14 14:02 developer ~0049222	Despite the fact that I am not actually able to test whether the problem is truly resolved since I don't have access to a MSSQL server setup, I'm marking this issue as fixed in 1.3.x on the grounds that the recent updates in ADOdb (which contain many improvements in the MSSQL driver) are likely to address it. Should the problem persist (using a nightly build or a version > 1.3.0-beta.1), feel free to reopen this issue or to create a new one.