Snipe-it: SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name 'remember_token'

[TylerH22]

Please confirm you have done the following before posting your bug report:
•[Yes] I have enabled debug mode
•[Yes] I have read checked the Common Issues page

Provide answers to these questions:
•Is this a fresh install or an upgrade? Fresh install
•Version of Snipe-IT you're running - Not sure which version. I installed Git and ran the following command: git clone https://github.com/snipe/snipe-it
•Version of PHP you're running - 7.2
•Version of MySQL/MariaDB you're running - MySQL Server 5.7
•What OS and web server you're running Snipe-IT on - Windows Server 2008 R2 and IIS
•WITH DEBUG TURNED ON, if you're getting an error in your browser, include that error
•What specific Snipe-IT page you're on, and what specific element you're interacting with to trigger the error

We are able to get the pre-flight & setup page to load. However, when we click to go to the next page we get the "whoops, looks like something went wrong" error.

I turned on debug mode and tried again and I get the following error:

(1/3) PDOException

SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name 'remember_token'

(2/3) PDOException

SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name 'remember_token'

(3/3) QueryException

SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name 'remember_token' (SQL: alter table users add remember_token text null)
•Include what you've done so far in the installation, and if you got any error messages along the way. -

I've successfully completed all of the steps in the installation steps. Only errors I recall during the installation was when trying to generate the app key. I forget what the exact error message is now but from doing some Googling I was able to mitigate the error by disabling the below 2 lines in my php.ini file.

1. ;extension=php_pdo_oci.dll
2. ;extension=php_pdo_firebird.dll
   •Indicate whether or not you've manually edited any data directly in the database - No I have not

I have done lots of google searches and have found things that are very similar but haven't found anyone with this exact error. Any help would be greatly appreciated.
Snipe-IT_Errors.txt

[TylerH22]

Here are some additional screenshots that might be helpful:

[TylerH22]

I ran the "php artisan migrate:status" command and it appears to be failing on the following step:

2016_2_19_070119_add_remember_token_to_users_table

[TylerH22]

So I went ahead and deleted and reinstalled everything on my web server and I now get the following error: Base table or view already exists: 1050 Table 'password_resets' already exists

Everything during the install seems to go perfectly until I get to this point. It looks like I'm getting one step further than I was before as now when I run the "php artisan migrate:status" command it fails on
create_password_resets_table.

[snipe]

This doesn't really make sense though. The whole point of migrations is that they don't run twice, so you don't run into those "column/table already exists" errors.

When you deleted and reinstalled everything, did you start with a fresh database as well? Seems like some tables might not have been deleted or something?

[TylerH22]

I was able to get this fixed yesterday! I manually went in and deleted all of the tables and I was then able to migrate successfully. Apparently not everything was getting deleted, although I’m not sure how since I completely removed MySQL from my machine and made a new database.

Thanks for reaching out,
Tyler

[snipe]

Awesome! Glad to hear you're all sorted. In the future, if you've resolved your issue, please try to remember to close your ticket - it helps us out a lot. (We have to manage a lot of tickets.)

[JonathonReinhart]

FWIW I hit this just now.

• Click Next: Create Database Tables
• It took too long and I hit an NGINX 504 Gateway Timeout error
• When I went back through the setup, I got a similar error:
  SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name 'company_id' (SQL: alter tableaction_logsaddcompany_idint null)

Just trying to explain how this might happen.