Magento – Error “Invalid model for shipping method: flatrate2” or other Shipping Methods

Unfortunately it can happen, that there is an error, when trying to generate an invoice. Once you have then looked into the report log file, one finds a great overview of the problem. Mainly there is but the first line

Invalid model for shipping method: flatrate2

That is, that Magento has a problem with a current or former Dispatch. In our case it was an attempt to have multiple flat rates side by side. So then came the flat rates 1-6. (It's been a while, so I do not remember the exact). These were then copied into the database tables and renamed etc.

Finally, we use it yet another way (Multiple Tablerates…I reported), so that the others were redundant. Thus, they were “deleted”. But probably not all. In the database were sufficient places where it was pointed to this. Thus, after some research, helped only the following:

1. In the database, e.g.. Select a database with PHPMyAdmin and correct

2. Table “core_config_data” search

3. Backup of the table to create security (Export)

4. If no backup needed, can step 2 and 3 be skipped. Otherwise, enter the following line at “SQL”

DELETE FROM core_config_data WHERE path LIKE ‘carriers/flatrate2%’

It is important here to send quotes to respect, otherwise there is an SQL error.

5. IMPORTANT: It should ALWAYS be the cache in the backend and FTP will be deleted after the deletion took place SQL, Otherwise, the same error occurs again!

6. Re trying to create an invoice. Should there be another error, again look into the report file what was wrong this time (It was the same file / error message, step was 5 😉 ignored )

7. We were then still the flatrate3, delete flatrate4 and flatrate5.

8. Each cache is not forgotten.

9. Now it should work again.

10. This should also work with other Shipping Methods, that arise across. You may be right but then the extension to be reinstalled.

Does occur, the error usually, if you have either installed an incorrect shipping method, this is wrong or you previously experimented with other methods has.

Used in Magento versions 1.4.1.1 and 1.5.1.0 Comments? Additions? Notes? Gladly!