View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0020637 | mantisbt | db mssql | public | 2016-02-26 11:58 | 2025-05-01 02:31 |
Reporter | rp14385 | Assigned To | dregad | ||
Priority | high | Severity | major | Reproducibility | always |
Status | resolved | Resolution | no change required | ||
Platform | Windows | OS | windows 2008R2 | OS Version | 2008 |
Product Version | 1.2.19 | ||||
Summary | 0020637: Getting error while signup/login to Mantisbt | ||||
Description | I am getting error while login in mantis BT. Error "Database query failed. Error received from database was 0000207: SQLState: 42S22 | ||||
Steps To Reproduce | While login in | ||||
Additional Information | attached error screenshots. I am using IIS7.5, PHP5.6, MSSQL2012R2 | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
MSSQL does not work well with MantisBT 1.2.x. Is this a new install ? In any case, I would suggest you try with the latest 1.3.x nightly build. |
|
Hi Dregad, Im trying to upgrade from 1.1.1 to 1.2.19. so, is there any stable release in 1.3.x which supports MSSQL ? |
|
If you're not comfortable with testing using a nightly build, you can download the latest release candidate (1.3.0rc1). |
|
Hi Dregad, I tried upgrading using 1.3.0Rc1, but still I am unable to login, PFA error screenshot . |
|
Hi. I haven't been able to solve it either.
|
|
@Infoproyectos this issue was reported 9 years ago on version 1.2 which is no longer supported. I suggest you open a separate one with details about your specific problem. And please note that none of the core devs use MSSQL it may be difficult for us to help. |
|
@rp14385 considerkng the lack of activity on this for so many years, I assume you managed to fix the problem somehow. I'm resolving this issue as "no change required", because it was reported against an old version of MantisBT which is no longer supported. I recommend that you upgrade to the latest stable version [1]; if the problem persists after doing so, do not hesitate to reopen the issue. |
|