Good evening, I was looking for a solution for a long time and have not yet found it.

I have a finished project on Laravel 5.4, which I decided to install on Windows (OpenServer). When installing, there was first such error:

Warning: require(W:\domains\furypay\bootstrap/../vendor/autoload.php): failed to open stream: No such file or directory in W:\domains\furypay\bootstrap\autoload.php on line 17 Fatal error: require(): Failed opening required 'W:\domains\furypay\bootstrap/../vendor/autoload.php' (include_path='.;w:/modules/php/PHP-5.6-x64;w:/modules/php/PHP-5.6-x64/PEAR/pear') in W:\domains\furypay\bootstrap\autoload.php on line 17

But I decided it by writing the composer update command at the root of the project.

But when updating the composer, at the end it was written:

 In Connection.php line 647: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'furypay.tickets' doesn't exist (SQL: select * from `tickets` where (`owner` is null and `status` = 0)) In Connection.php line 319: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'furypay.tickets' doesn't exist Script php artisan optimize handling the post-update-cmd event returned with error code 1

And this text appears with php artisan migrate and similar commands.

I have already tried a lot, nothing helps, I ask for help in solving this problem for you.

    1 answer 1

    As written in a message in the furypay database, there is no table tickets. To which there is a circulation in migrations. Maybe you need this table then you will need to make it in the migration. And maybe the migration is incorrect and you just need to delete everything connected with this table. Look at the code that you have and how.

    • I write this when writing the command "php artistan migrate". Even migration does not start - Daniil Rybalchenko
    • Put Xdebug, then put the breakpoint in the file Connection.php line 647: and understand the problem very quickly. - Mykola Veriga
    • Can be more? I'm new, what is breakpoint? - Daniel Rybalchenko
    • on the left there will be debug_backtrace and by it you will see what and where is wrong - Mykola Veriga
    • one
      As I understand it, these are problems not in the files themselves, but in problems with the composer, maybe a mismatch of versions or something else. - Daniel Rybalchenko