I think the only way you can get this error is if you have an 'administrator' user with an id of 0 (zero). Since the installer creates this record with an id of 1, I'm not sure how this could happen. I suggest you check with mysql to confirm.

That being said, this warning message is displayed in a non-standard way, I'll have a look into improving that.

As a side note, you should also fix the timezone system warning.

The 'id' column of mantis_user_table has value = 1 for administrator user, as visible in the screen shot attached. Then also we are getting the same error.

I also would like to add that even before I can try to log in the error message appears. Which means that when the Mantis login page opens on the browser, page is looking for the administrator user and brings up the error.

mantis_user_table has value = 1 for administrator user, as visible in the screen shot attached

There is no screenshot.

when the Mantis login page opens on the browser, page is looking for the administrator

This is correct and normal, it's done as part of a security check to verify if the default administrator password has been changed

Looking at the code (login_page.php line 192), the only possibility of this error occuring, is if the user ID of the 'administrator' account is 0. Based on that, assuming you have checked the user table in the right database, I can think of only one alternative: are you using customized MantisBT code ?

This is due to to running MSSQL.

The current 1.2 release does not support MSSQL IMO

Paul

This is due to to running MSSQL.

So you're saying that user_get_id_by_name('administrator') fails to return the user ID on mssql ?

The current 1.2 release does not support MSSQL IMO

I know there are issues with it (several of which are in fact fixed in later releases of ADOdb), but that's really basic use...

I don't have access to MSSQL so can't test anyway

if your running mssql or sqlsrv [forget which] - pretty sure odbc_mssql works in this csae. OR, that's working with a mantis patched adodb library.

I know I saw this case when originally doing the mssql stuff years ago with stock drivers in certain setup's

This is hence why we'd be better stating that MSSQL is broken [IMO at least] and fixing it properly with some test setup in place for the next mantis release, rather then poking at the edges

Hi guys looking at the thread, I get to feel that Mantisbt can not be installed with MS SQL server database.... is this true?

Please suggest is there is any work around? Is there any other older version of Mantisbt that I need to try?

It would be helpful for me if I can get any references of those who may have successfully have deployed on MS SQL database. I could interact with them to get any help.

It will be difficult for me to help further. I don't think grangeway is interested in supporting/fixing 1.2 as he's focusing on a new version even though I believe he's the only core dev with good knowledge of mssql.

That said, I know of a few people who use Mantis successfully on mssql, but I am not sure which version, which driver, and if they have patched Mantis or the underlying adodb library to achieve that.

I suggest you search the tracker, check out the Forums, mailing list and IRC for support - if you're lucky someone will be able to help.

You can also try to use a more recent of adodb (see 0013713) or if all else fails, fallback to using MySQL.

If you manage to fix the problem, it would be nice of you to report your findings here.

5 years later I assume you've either resolved the problem or given up on it...