View Issue Details

WikiJump to Notes
IDProjectCategoryView StatusDate SubmittedLast Update
0006690mantisbtbugtrackerpublic2006-02-09 12:272008-08-12 09:35
Reporterlmorton Assigned Tograngeway  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionno change required 
Product Version1.0.0 
Summary0006690: Mantis install page will not setup my MYSQL 5.0 database properly
Description

I have installed the Mantis install in my IIS5.0 web server running on WIN2k. I am able to reach the http://localhost//mantis/admin/install.php web page in my browser but when I try to create the database I get a "BAD" error in the "Checking PHP support for database type " check. The error message says
"database is not supported by PHP. Check that it has been compiled into your server."

I am running MYSQL 5.0. DO I have to compile the PHP to run with MYSQL? Is there an easy way to fix this?

Thanks,

Les Morton Jr.
Manager of Web Services
Order Management Project Manager
Associated Wholesalers Inc.
(717) 854-1505 ext. 8286

TagsNo tags attached.

Relationships

Relationship GraphDependency Graph
has duplicate 0006691 closedthraxisp Mantis install page will not setup my MYSQL 5.0 database properly 
has duplicate 0006951 closedthraxisp Database is not supported by PHP 

Activities

thraxisp

thraxisp

2006-02-09 13:40

reporter   ~0012120

Yes. The mysql interface is a loadable module. It needs to be compiled in, or linked.

If you run phpinfo() and see MySQL loaded, please add a note to this issue, as something is wrong with the code.
allied

allied

2006-04-18 12:39

reporter   ~0012613

How was this resolved?
thraxisp

thraxisp

2006-04-18 13:34

reporter   ~0012614

On windows, I believe that the loadable modules are added through the php.ini file. If I recall correctly, there is a prototype "extension" directory that needs to be uncommented. On Unix, the modules are loaded automagically from a specific directory.
allied

allied

2006-04-19 16:11

reporter   ~0012625

That seams to be my problem. When I run phpinfo() the Configuration File (php.ini) Path says C:\WINDOWS when I moved it to the D:\PHP folder like suggested. Also, noticed in the PHP Core section of the config, that the include_path is set to .;C:\php5\pear when in my php.ini file I have it set to D:PHP\EXT It appears this php.ini file is not being read. FYI, there is not a php.ini in my C:\WINDOWS folder. How can I tell PHP and or Mantis where I moved the php.ini file? I already have the path set in Windows 2003 Server system variables.
thraxisp

thraxisp

2006-04-19 16:58

reporter   ~0012628

As far as I know, the location of the php.ini file is compiled in to the php binary. Its location is shown in the phpinfo() output.
allied

allied

2006-04-19 17:06

reporter   ~0012629

Are you saying that the PHP.INI file must stay in the C:\WINDOWS folder?
thraxisp

thraxisp

2006-04-19 23:07

reporter   ~0012632

Yes, as far as I know, without recompiling PHP.
bkinder

bkinder

2007-06-06 17:15

reporter   ~0014695

I had this same problem and and solved by setting the extension_dir=D:PHP\EXT instead of include_path.

Hope it helps.

Bruno
teknophile06

teknophile06

2007-09-06 13:50

reporter   ~0015585

In my case, I had to enable "extension=php_mysql.dll" in php.ini. Also, I noticed that while phpinfo() does list the configuration path to be C:\windows, it does use whatever location you use, as long as you enter it into the PATH environment variable in windows.
grangeway

grangeway

2008-05-02 16:22

reporter   ~0017734

Thank you for taking the time to report a problem with mantis.

Since this problem report was originally made, a number of releases have occurred.
It appears that this issue has either been fixed, or may not be a relevant report for the current release.

Unfortunately you are not using the latest version and the problem might already be fixed. Please download the latest release from http://www.mantisbt.org/download.php

If you are able to reproduce this bug in the current release, or have some more information on how this feature could be improved in the current release. Please either change the mantis version on this bug report
to the version you tested and change the status back to "Open", or open a new issue report wit more information.

Again, thank you for your bug report and your continued support.
Paul