View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0029262 | mantisbt | installation | public | 2021-11-10 09:24 | 2021-12-26 07:01 |
Reporter | boardhead360 | Assigned To | dregad | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | closed | Resolution | unable to reproduce | ||
Product Version | 2.25.2 | ||||
Summary | 0029262: Schema step 168: DropColumnSQL ( mantis_sponsorship_table ) BAD | ||||
Description | during install of database, message appears and stops installation: A check of the db shows that column doesn't exist, last_update_int exists | ||||
Tags | No tags attached. | ||||
I guess this is not a major issue. The tables get created, so I was able to continue the installation without the script. I did run into issues with schema steps beyond 168, where the commands were not implemented and I had to manually add some columns. |
|
Is this a new install or an upgrade ? If the latter, from which version ? FYI: Schema step 168 is part 3 of 4, of an operation to convert the last_updated column's type from date/time (used in MantisBT < 1.2) to integer:
I can't offer any explanation for the missing column, especially if step 167 was successful... it does not make sense. Did you run the upgrade script twice ? Executed some SQL directly against the DB ? Encounter any other errors during the installation process ? |
|
This was a new install. I did add the field manually, which got me going for a little bit, then ran into the same missing field issue on another table. So it appears that some of the scripts executed correctly, while others did not. As a result, I'm not sure I can actually fix the tables myself. But I will try and report back. |
|
I'm surprised to hear the installation process failed on a brand new install. I've never seen this happen before.
So you installed by generating the SQL script and executing that manually ?
You should not. Chances are you'll screw up somewhere without noticing at first, and end up with problems down the line. Without further information leading to a reproducible case, I don't think I would be able to help much. You need to figure out why the column does not exist at that stage. |
|
I'm not trying to run the installation manually. I was trying to understand why it stopped specifically at that error. 500 - Internal server error. I then go back to the administration page and try to run the installation again, that's how I get an error from the mantis install script indication that it is trying to delete a field that doesn't exist. I've repeated the procedure through Chrome with the same result |
|
This likely explains your problem. You need to check your php error log for details about what happened.. |
|
You did not provide any feedback; I am therefore resolving this issue. Feel free to reopen itat a later time and provide the requested information. |
|