Hello,
I followed the instructions to install the latest Mantis to the letter and everything seemed to go smoothly. I use PHP 5.2.12 and SQL server 2005.
After install, the following config.inc.php is created:
<?php
$g_hostname = 'localhost';
$g_db_type = 'mssql';
$g_database_name = 'mantisBT';
$g_db_username = 'mantis';
$g_db_password = '<obfuscated>';
?>
When I try to log in using administrator / root, it denies log in with a message that either the password is bad or the account is locked. In the database, I verified that the account is not locked, and the password for it corresponds to the MD5 hash for the string 'root'.
At this point I am at a loss as to how to proceed further. Any help would be very much appreciated.
Thanks,
Philippe Damerval
Mantis BT version 1.2 not working
Moderators: Developer, Contributor
Re: Mantis BT version 1.2 not working
Hi, Philippe,
From what you say you seem to have 'sa' access to your database server. Can you check the following:
1) $g_hostname = 'localhost' implies that the database server is running on the same host as your webserver. Is this correct?
2) If you haven't already removed the 'admin' directory, try running '<mantisURL>/admin/check.php' from your browser and see if that reports any problems. Check particularly that the 'mantis' database user has all the required privileges to access the database (SELECT,INSERT,UPDATE,DELETE) from the webserver host.
3) What web server are you using, Apache, IIS or another? User access rights may be a problem although if you've completed the installation process then that seems unlikely. Did you run the install locally or from a remote machine via the web i.e. were you logged on to the mantis host at the time?
regards,
Robert
From what you say you seem to have 'sa' access to your database server. Can you check the following:
1) $g_hostname = 'localhost' implies that the database server is running on the same host as your webserver. Is this correct?
2) If you haven't already removed the 'admin' directory, try running '<mantisURL>/admin/check.php' from your browser and see if that reports any problems. Check particularly that the 'mantis' database user has all the required privileges to access the database (SELECT,INSERT,UPDATE,DELETE) from the webserver host.
3) What web server are you using, Apache, IIS or another? User access rights may be a problem although if you've completed the installation process then that seems unlikely. Did you run the install locally or from a remote machine via the web i.e. were you logged on to the mantis host at the time?
regards,
Robert
-
pdpdpdpdpd
Re: Mantis BT version 1.2 not working
Hi, thank you for your reply. Answers to your questions below.
1) Yes, the web server and the database are on the same machine
2) There were two "bad" and two warnings, about which it is unclear what I should do. Screenshot attached. "mantis" database user is dbo on the mantis database.
3) Using apache 2.2.14 on a windows machine. Install was done from the server itself, while remotely logged on to the Mantis/apache/sql server host using remote desktop. I don't have physical access to the server.
Thank you for your help!
Philippe
1) Yes, the web server and the database are on the same machine
2) There were two "bad" and two warnings, about which it is unclear what I should do. Screenshot attached. "mantis" database user is dbo on the mantis database.
3) Using apache 2.2.14 on a windows machine. Install was done from the server itself, while remotely logged on to the Mantis/apache/sql server host using remote desktop. I don't have physical access to the server.
Thank you for your help!
Philippe
- Attachments
-
- Clipboard01.jpg (214.59 KiB) Viewed 5146 times
Re: Mantis BT version 1.2 not working
Hi, Philippe,
Sorry for the delay in replying - I was on holiday for a few days.
Looking at the output from 'check' I would recommend the following to fix the errors. Although I don't think these will fix your overall problem it will at least be a step in the right direction:
1) BAD validate_email - As you can see PHP 5.3 or later is required for Windows installations if this option is ON so upgrade PHP to a current version e.g. 5.3.10 if possible or copy the $g_validate_email section from config_defaults_inc.php to your config_inc.php and change the value to OFF to disable it. PHP 5.2.12 is quite old even for the 5.2 branch.
2) BAD MantisBT upload file size - either change "upload_max_filesize" in php.ini OR customise your MantisBT setting by copying "$g_max_file_size" from config_defaults_inc.php into your config_inc.php and changing the value so that it is less than "upload_max_filesize".
3) WARN mssql textsize - unfortunately I'm using MySQL so I have no direct comparison. However, as the default value is 4096 it seems as though this has been changed somewhere - check php.ini to see where the value 1048576 comes from (it may be set as 1M). From what I've read this setting can affect both database connection and data retrieval. Some users have set both mssql.textsize and mssql.textlimit to the maximum value, 2147483647!!
4) Try writing a php script to check your database connection from PHP, bypassing Mantis.
Let me know if this helps,
Robert
Sorry for the delay in replying - I was on holiday for a few days.
Looking at the output from 'check' I would recommend the following to fix the errors. Although I don't think these will fix your overall problem it will at least be a step in the right direction:
1) BAD validate_email - As you can see PHP 5.3 or later is required for Windows installations if this option is ON so upgrade PHP to a current version e.g. 5.3.10 if possible or copy the $g_validate_email section from config_defaults_inc.php to your config_inc.php and change the value to OFF to disable it. PHP 5.2.12 is quite old even for the 5.2 branch.
2) BAD MantisBT upload file size - either change "upload_max_filesize" in php.ini OR customise your MantisBT setting by copying "$g_max_file_size" from config_defaults_inc.php into your config_inc.php and changing the value so that it is less than "upload_max_filesize".
3) WARN mssql textsize - unfortunately I'm using MySQL so I have no direct comparison. However, as the default value is 4096 it seems as though this has been changed somewhere - check php.ini to see where the value 1048576 comes from (it may be set as 1M). From what I've read this setting can affect both database connection and data retrieval. Some users have set both mssql.textsize and mssql.textlimit to the maximum value, 2147483647!!
4) Try writing a php script to check your database connection from PHP, bypassing Mantis.
Let me know if this helps,
Robert