Bug Can not Upgrade from 1.3.8 to 2.1.0

[chatty]

Hi there,
if i try to upgrade vbDownloads from it's current version 1.3.8 to 2.1.0 i get this error message :

Invalid SQL:

                REPLACE INTO vb_dbtech_downloads_download
                SELECT * FROM vb_dbtech_downloads_filegroup;

MySQL Error   : Column count doesn't match value count at row 1
Error Number  : 1136

I try all other versions after 1.3.8 . Same errors.

I diddn't modify anything in the Database after installing vbDonwloads. same error on all versions at the same place

Here the messages before the Error :

Updating Version Number To: 1.4.0b1

• Altered Table: vb_administrator
• Altered Table: vb_user
• Altered Table: vb_usergroup
• Created Table: vb_dbtech_downloads_category
• Created Table: vb_dbtech_downloads_comment
• Created Table: vb_dbtech_downloads_delay
• Created Table: vb_dbtech_downloads_download
• Created Table: vb_dbtech_downloads_downloadlog
• Created Table: vb_dbtech_downloads_extension
• Created Table: vb_dbtech_downloads_extensiongroup
• Created Table: vb_dbtech_downloads_favourite
• Created Table: vb_dbtech_downloads_file
• Created Table: vb_dbtech_downloads_rating
• Re-created Table: vb_dbtech_downloads_report
• Populated Table: vb_dbtech_downloads_category
• Populated Table: vb_dbtech_downloads_comment
• Populated Table: vb_dbtech_downloads_extension
• Populated Table: vb_dbtech_downloads_extensiongroup

Hmm. strange...

Greetings
Oliver

 

[Fillip H.]

Can you please post a screenshot of your vb_dbtech_downloads_filegroup table and vb_dbtech_downloads_download table from phpMyAdmin? I'll need to see all the table columns.

 

[chatty]

Hi and thx. for fast responding.

Here the Pics from my database :



And BTW : I have never touch the tables here.

 

[Fillip H.]

Remove the 17th column (threadid) and then try the upgrade again

 

[chatty]

Thank you very much. That was the Problem. But the coloumn was not from me
Nobody upgrades ? hmmm.

 

[Fillip H.]

We've had dozens of upgrades already, only one other person has reported a similar issue to this