Help with installation database errors

[TechGuy29]

Script URL: Local network
Mods for HESK version: 3.2.5
HESK version: 2.7.5
Hosting company: Local (Xampp, 3.2.2)
URL of phpinfo.php: Local
URL of session_test.php: local
What terms did you try when SEARCHING for a solution: Internal error, tried copy and paste of the error in the search...

Write your message below:
I have a live system of HESK in use version 2.6.8 with no version of MODS for HESK, however i'm making use of a backup database on my live system to try out the lastest versions of HESK and MODS for HESK.

I followed through as per instruction for each of the systems. I get HESK 2.7.5 to work with the imported data from my live system.
When i tried installing MODS for HESK 3.2.5 i got this error at first

An error occurred! (Error Code: 128)
Could not execute query: UPDATE `wpsupport_users` SET `autoreload` = `autorefresh` / 10. MySQL said: Unknown column 'autoreload' in 'field list'
"
An error occurred! (Error Code: 3)
"An error occurred: Undefined index: status in C:\\xampp\\htdocs\\WPSupport\\install\\migrations\\Pre140\\Statuses\\DropOldStatusColumn.php on 18""An error occurred: Undefined index: status in C:\\xampp\\htdocs\\WPSupport\\install\\migrations\\Pre140\\Statuses\\DropOldStatusColumn.php on 18""An error occurred: Undefined index: status in C:\\xampp\\htdocs\\WPSupport\\install\\migrations\\Pre140\\Statuses\\DropOldStatusColumn.php on 18""An error occurred: Undefined index: status in C:\\xampp\\htdocs\\WPSupport\\install\\migrations\\Pre140\\Statuses\\DropOldStatusColumn.php on 18""An error occurred: Undefined index: status in C:\\xampp\\htdocs\\WPSupport\\install\\migrations\\Pre140\\Statuses\\DropOldStatusColumn.php on 18""An error occurred: Undefined index: status in C:\\xampp\\htdocs\\WPSupport\\install\\migrations\\Pre140\\Statuses\\DropOldStatusColumn.php on 18""An error occurred: Undefined index: status in C:\\xampp\\htdocs\\WPSupport\\install\\migrations\\Pre140\\Statuses\\DropOldStatusColumn.php on 18""An error occurred: Undefined index: status in

... (just a series of the same error line continues, which i omitted purposefully)

Then i reverted back to a working HESK 2.7.5 and tried again, using the browsers debug mode and i hope this gives a far better understanding of the error produced on the second attempt.

Second attempt to upgrade to MODS for HESK 3.2.5

An error occurred! (Error Code: 128)
Could not execute query: UPDATE `wpsupport_users` SET `autoreload` = `autorefresh` / 10. MySQL said: Unknown column 'autoreload' in 'field list'


Error from Google Chrome's debug tool (F12)
---
/wpsupport/install/ajax/process-migration.php Failed to load resource: the server responded with a status of 500 (Internal Server Error)
install-script.js:132 Could not execute query: UPDATE `wpsupport_users` SET `autoreload` = `autorefresh` / 10. MySQL said: Unknown column 'autoreload' in 'field list'
error @ install-script.js:132
c @ jquery-1.10.2.min.js:4
fireWith @ jquery-1.10.2.min.js:4
k @ jquery-1.10.2.min.js:6
r @ jquery-1.10.2.min.js:6

Please assist i'm by no means a database guy, trying to learn a few things though?
Thank you in advance
TechGuy29

[TechGuy29]

I have decided to create a clean database using the HESK installation, that was successful.

On the MODS for HESK installation using the database validator i got all these failures

Failure

One or more columns / tables are not properly configured in your database. Please open a topic at the PHP Junkyard Forums with this information for assistance.
Results
Database Change Status
1.0.0 - 1.3.x
Table Exists: statuses Failure
Column Exists: statuses.ID Failure
Column Exists: statuses.TextColor Failure
Column Exists: statuses.IsNewTicketStatus Failure
Column Exists: statuses.IsClosed Failure
Column Exists: statuses.IsClosedByClient Failure
Column Exists: statuses.IsCustomerReplyStatus Failure
Column Exists: statuses.IsStaffClosedOption Failure
Column Exists: statuses.IsStaffReopenedStatus Failure
Column Exists: statuses.IsDefaultStaffReplyStatus Failure
Column Exists: statuses.LockedTicketStatus Failure
1.5.0
Column Exists: users.active Failure
1.6.0
Column Exists: users.notify_note_unassigned Failure
Table Exists: settings Failure
1.7.0
Table Exists: verified_emails Failure
Table Exists: pending_verification_emails Failure
Table Exists: stage_tickets Failure
2.2.0
Column Exists: statuses.IsAutocloseOption Failure
Column Exists: statuses.Closable Failure
2.3.0
Column Exists: service_messages.icon Failure
Column Exists: statuses.Key Failure
Column Exists: tickets.latitude Failure
Column Exists: tickets.longitude Failure
Column Exists: stage_tickets.latitude Failure
Column Exists: stage_tickets.longitude Failure
Column Exists: categories.manager Failure
Column Exists: users.permission_template Failure
Table Exists: permission_templates Failure
Column Exists: permission_templates.id Failure
Column Exists: permission_templates.name Failure
Column Exists: permission_templates.heskprivileges Failure
Column Exists: permission_templates.categories Failure
2.4.0
Table Exists: quick_help_sections Failure
Column Exists: quick_help_sections.id Failure
Column Exists: quick_help_sections.location Failure
Column Exists: quick_help_sections.show Failure
Table Exists: text_to_status_xref Failure
Column Exists: text_to_status_xref.id Failure
Column Exists: text_to_status_xref.language Failure
Column Exists: text_to_status_xref.text Failure
Column Exists: text_to_status_xref.status_id Failure
Column Exists: statuses.sort Failure
Column Exists: attachments.download_count Failure
Column Exists: kb_attachments.download_count Failure
Column Exists: tickets.html Failure
Column Exists: stage_tickets.html Failure
Column Exists: replies.html Failure
2.5.0
Column Exists: tickets.user_agent Failure
Column Exists: tickets.screen_resolution_width Failure
Column Exists: tickets.screen_resolution_height Failure
Column Exists: stage_tickets.user_agent Failure
Column Exists: stage_tickets.screen_resolution_width Failure
Column Exists: stage_tickets.screen_resolution_height Failure
2.6.0
Table Exists: logging Failure
Column Exists: logging.id Failure
Column Exists: logging.username Failure
Column Exists: logging.message Failure
Column Exists: logging.severity Failure
Column Exists: logging.location Failure
Column Exists: logging.timestamp Failure
Table Exists: user_api_tokens Failure
Column Exists: user_api_tokens.id Failure
Column Exists: user_api_tokens.user_id Failure
Column Exists: user_api_tokens.token Failure
Table Exists: temp_attachment Failure
Column Exists: temp_attachment.id Failure
Column Exists: temp_attachment.file_name Failure
Column Exists: temp_attachment.saved_name Failure
Column Exists: temp_attachment.size Failure
Column Exists: temp_attachment.type Failure
Column Exists: temp_attachment.date_uploaded Failure
Table Exists: calendar_event Failure
Column Exists: calendar_event.id Failure
Column Exists: calendar_event.start Failure
Column Exists: calendar_event.end Failure
Column Exists: calendar_event.all_day Failure
Column Exists: calendar_event.name Failure
Column Exists: calendar_event.location Failure
Column Exists: calendar_event.comments Failure
Column Exists: calendar_event.category Failure
Table Exists: calendar_event_reminder Failure
Column Exists: calendar_event_reminder.id Failure
Column Exists: calendar_event_reminder.user_id Failure
Column Exists: calendar_event_reminder.event_id Failure
Column Exists: calendar_event_reminder.amount Failure
Column Exists: calendar_event_reminder.unit Failure
Column Exists: calendar_event_reminder.email_sent Failure
Column Exists: tickets.due_date Failure
Column Exists: tickets.overdue_email_sent Failure
Column Exists: categories.usage Failure
Column Exists: users.notify_overdue_unassigned Failure
Column Exists: users.default_calendar_view Failure
2.6.2
Column Exists: stage_tickets.due_date Failure
Column Exists: stage_tickets.overdue_email_sent Failure
3.1.0
Column Exists: categories.background_color Failure
Column Exists: categories.foreground_color Failure
Column Exists: categories.display_border_outline Failure
Column Exists: logging.stack_trace Failure
Table Exists: custom_nav_element Failure
Column Exists: custom_nav_element.id Failure
Column Exists: custom_nav_element.image_url Failure
Column Exists: custom_nav_element.font_icon Failure
Column Exists: custom_nav_element.place Failure
Column Exists: custom_nav_element.url Failure
Column Exists: custom_nav_element.sort Failure
Table Exists: custom_nav_element_to_text Failure
Column Exists: custom_nav_element_to_text.id Failure
Column Exists: custom_nav_element_to_text.nav_element_id Failure
Column Exists: custom_nav_element_to_text.language Failure
Column Exists: custom_nav_element_to_text.text Failure
Column Exists: custom_nav_element_to_text.subtext Failure
Setting Exists: admin_navbar_background Failure
Setting Exists: admin_navbar_background_hover Failure
Setting Exists: admin_navbar_text Failure
Setting Exists: admin_navbar_text_hover Failure
Setting Exists: admin_navbar_brand_background Failure
Setting Exists: admin_navbar_brand_background_hover Failure
Setting Exists: admin_navbar_brand_text Failure
Setting Exists: admin_navbar_brand_text_hover Failure
Setting Exists: admin_sidebar_background Failure
Setting Exists: admin_sidebar_background_hover Failure
Setting Exists: admin_sidebar_text Failure
Setting Exists: admin_sidebar_text_hover Failure
Setting Exists: admin_sidebar_font_weight Failure
Setting Exists: admin_sidebar_header_background Failure
Setting Exists: admin_sidebar_header_text Failure
3.2.0
Table Exists: audit_trail Failure
Table Exists: audit_trail_to_replacement_values Failure
Column Exists: categories.mfh_description Failure
Column Exists: custom_fields.mfh_description Failure
Setting Exists: migrationNumber Failure

(F12) debug detail:
database-validation.php:1 This page was loaded non-securely in an incognito mode browser. A warning has been added to the URL bar. For more information, see https://goo.gl/y8SRRv.
modsForHesk-javascript.js:42 Uncaught TypeError: $(...).iconpicker is not a function
at HTMLDocument.loadJquery (modsForHesk-javascript.js:42)
at c (jquery-1.10.2.min.js:4)
at Object.fireWith [as resolveWith] (jquery-1.10.2.min.js:4)
at Function.ready (jquery-1.10.2.min.js:4)
at HTMLDocument.q (jquery-1.10.2.min.js:4)

But then continued the installation using the clean database and the installation was successful!
Not quite sure why the MODS for HESK install page offers the database validator and gives those failures on a clean database
but still it continues to install successfully?

But excellent work! VERY WELL DONE

Thank you,
TechGuy29

[mkoch227]

The database validator is there to validate your current database to check if any Mods for HESK tables and/or columns are missing from an existing installation. Since you looked at the validator before installing Mods for HESK, everything failed. This is normal. Now that since you've installed Mods for HESK, all of the validations should pass.

[TechGuy29]

Hi Mike,
Thanks for the prompt response, appreciated more than you know. Thanks for clearing matters.

What would be best practise to import my live database table data to my test system that now has MODS for HESK running?

Kind Regards
TechGuy29

[mkoch227]

I'm having issues posting my response here, so here's a link to my response: https://pastebin.com/Met5YsEX

Once I figure out why the forum doesn't like my message, I'll copy it back over here

[TechGuy29]

I'll get onto this again, and post back to you.
Thanks a mil Mike.

Regards
TechGuy29

PS - for some reason i tried pasting your response with mine and i got some "route link not found..."