View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0022634 | mantisbt | db mssql | public | 2017-03-31 14:00 | 2017-04-30 14:48 |
Reporter | dharmangp25 | Assigned To | dregad | ||
Priority | high | Severity | major | Reproducibility | unable to reproduce |
Status | closed | Resolution | no change required | ||
Product Version | 2.2.2 | ||||
Summary | 0022634: Application Error 0000401 on page my_view_page.php | ||||
Description | I am trying to use mantis on windows server with mssql database. It was really hard to install it but I managed to install it. Most of the stuffs works great but when I login as a reporter, I cannot see anything on my_view_page.php. I can just see title. When I login as an administrator, I can see a SQL error which I am pasting below Database query failed. Error received from database was #0: for the query: SELECT * FROM mantis_bug_history_table WHERE mantis_bug_history_table.bug_id IN ( SELECT mantis_bug_table.id FROM mantis_bug_table JOIN mantis_project_table ON mantis_project_table.id = mantis_bug_table.project_id WHERE mantis_project_table.enabled = ? AND ( mantis_bug_table.project_id = 1 ) ) AND date_modified >= ? AND date_modified < ? ORDER BY mantis_bug_history_table.date_modified DESC, mantis_bug_history_table.id DESC. Our main project is up and running and we want this to be working great as soon as possible. I will really appreciate any help. Thanks | ||||
Tags | No tags attached. | ||||
First of all, please note that none of the team members have access to MSSQL, so helping you will likely be difficult.
What gave you trouble, and what did you do to make it work ? What happens when you run this query manually against your DB ? Do you have any data in the history table ? To get a better understanding of what is happening, you may want to set
WARNING - SECURITY RISK: the 'show_detailed_errors' config can cause MantisBT to display sensitive information about your system. We recommend to restrict its activation to a Test environment, only for as long as necessary. If possible, do not turn it ON globally, instead limit it for specific user(s) using the Manage Configuration page.
If the output does not help you resolving the issue and you need further assistance,
|
|
It may not be related to the error you're getting, but since you mentioned issues with installation, maybe you should to take a look at 0022063 - @obmsch's patch, which i merged a few minutes ago, resolves a blocking issue with the installer on MSSQL. |
|
I have tested a mssql install and can't reproduce this error, with v2.2.2. or current master with DB version: |
|
dharmangp25, You did not provide any feedback; I am therefore resolving this issue as "no change required". Feel free to reopen the issue at a later time and provide the requested information. |
|