Mantis Bug Tracker - Forums

Hi Folks,

regarding this guide:
http://www.mantisbt.org/manual/manual.i ... rading.php

i get this error message after proceed point 6 in the manual (admin/install.php)

------------------
APPLICATION ERROR #401

Datenbankabfrage fehlgeschlagen. Die Reportmeldung lautet #1264: Out of range value for column 'date_order_int' at row 1 für die Abfrage: UPDATE mantis_project_version_table SET date_order_int=?
WHERE id=?.

Bitte benutzen Sie die „Zurück“-Taste Ihres Browsers, um auf die vorhergehende Seite zurückzukehren. Dort können Sie den hier angezeigten Eintrag korrigieren oder eine andere Aktion ausführen. Über das Menü können Sie auch direkt zu einer anderen Aktion wechseln.
------------------

The whole thing runs on my testsystem (xp-sp3, latest Apache,PHP,MySQL). The Import of the .sql dumpfile works without problems. everything looks fine in 1.1.7.
What can i try to solve the problem and run this update flawlessly?

yours sincerly
Heinrich

hi,
sry but, no idea's?!?
Pls help
yours sincerly
heinrich

Is here any mantis pro?

Hi, do have any idea? I would give you any information you need. thx

Check in our old 1.1.7 version the project management page.
Have a closer look at the versions listing. Is there any curious date entry?

hi, thx for your help. Where can i found "project management page" to check the dates?

In our test environment i get this error too:
APPLICATION ERROR #401

Datenbankabfrage fehlgeschlagen. Die Reportmeldung lautet #1265: Data truncated for column 'last_visit' at row 1 für die Abfrage: UPDATE mantis_user_table
SET last_visit= '2010-06-21 11:06:52'
WHERE id='1'

Pls help
thx
Heinrich

Heinrich wrote:Where can i found "project management page" to check the dates?

Click link "Manage" -> "Manage Projects" and select one of the projects in list.

I am wondering about your last post where the following statement is included.
UPDATE mantis_user_table SET last_visit= '2010-06-21 11:06:52' WHERE id='1'

For version 1.2.1 I expect something like the following statement because date format has been changed since version 1.2.0
UPDATE mantis_user_table SET last_visit= 1277150755 WHERE id=1

Please post user_api.php line 1148
Furthermore some more information about your environment maybe will help (Operating system, database version, PHP version)

hi,
i viewed every project under "Manage" -> "Manage Projects". And i found some strange dates in the Version Tables of the projects.
For example: "1901-12-13 21:45 CET" or "2032-02-07 21:35 CET". Could this be a problem?

I am wondering about your last post where the following statement is included.
UPDATE mantis_user_table SET last_visit= '2010-06-21 11:06:52' WHERE id='1'

this was an output of my testenvironment installation 1.1.7.

Please post user_api.php line 1148
Furthermore some more information about your environment maybe will help (Operating system, database version, PHP version)

Line 1148: return true;
here you can find the complete file:
http://www.heypasteit.com/clip/KUL
Apache 2.2.4 runs on an Linux version 2.6.18.8-0.5-default (openSUSE 10.2 (i586))
MySQL 5.1.30-community run on Windows Server 2008 Standard x64 SP1 (with latest Windows-Updates)
PHP Version 5.2.4

yours sincerly
Heinrich

You are confusing me because I don't know when you are talking about 1.1.x and when about 1.2.x
Do you try running 1.1.x and 1.2.x connected to one database? This will not work.

Be aware that PHP Version 5.2.4 is not a real good one! You should update to a newer version of 5.2.x (for example one of my 1.1.x installations is running very stable with 5.2.6, one of my 1.2.x installations is stable running with 5.2.12)
At the moment I don't recommend to update to 5.3.x (at least not to 5.3.0 or 5.3.1)

Hi,
the core problem is the upgrade 1.1.7 --> 1.2.1.
My first test environment had installed the newest php version (5.2.xx). same error.

Heinrich

I'm seeing this problem too - we're going from 1.0.5 (which is ridiculously old) to 1.2.1, but get the exact same error message reported during the update script "#1264: Out of range value for column 'date_order_int'"

Looking at the state of the table, it appears that the script attempts to change a column which has a value of 1 to a very large number that looks a bit like a null value.

I've tried the 1.2.0 upgrade script but this does the exact same thing too.

Any help in upgrading, would be much appreciated - I've had to reinstate my 1.0.5 installation to continue work for the time being.