The error has gone when updating laravel to 4.1.30

iz5clj said:

The error has gone when updating laravel to 4.1.30 I think, it can't make error with little upgrade.

• You maybe rename migration file. (migrations table can't found renamed file)

I have the same issue here, as @erayaydin said I tink it was caused as I had renamed a migrations file.

I have since deleted that migration file and made a new one but the error persists, any idea of how to fix the error ?

.k

UPDATE:

I just fon the migration db table, detetign the entry seems to sort the problem

Delete the database and again create it.This problem comes due to foreign keys