I hope you have a backup of both the database and files from before attempting to upgrade!

If you have them I suggest you restore the files and database and make sure your blog is working properly again. Then get a brand new copy of the package zip and try anew with completely new files.

Oh and I would also delete all the hits from your hit log by using the stats tab and deleting one day at a time. BTW I do not think that having a big hitlog table is part of the problem. Shrinking it before upgrading just seems like a nice idea is why. Smaller backups, less for the upgrader to maybe have to think about.

Yes I did.
so far I just copied the files again as you said, but it gives me the same problem again:

Upgrading data in existing b2evolution database...

Loading: _core/model/__core.install.php
Loading: sessions/model/_sessions.install.php
Checking DB schema version... 9950 : OK.
Renaming tables...OK.
Making sure all tables use desired storage ENGINE...T_groups:innodb
T_settings:innodb
T_global__cache:innodb
T_users:innodb
T_users__fielddefs:innodb
T_users__fields:innodb
T_skins__skin:innodb
T_skins__container:innodb
T_blogs:innodb
T_coll_settings:innodb
T_widget:innodb
T_categories:innodb

An unexpected error has occurred!

If this error persists, please report it to the administrator.

Go back to home page

Additional information about this error:

MySQL error!

The used table type doesn't support FULLTEXT indexes(Errno=1214)

Your query:

ALTER TABLE evode1_categories ENGINE = innodb

I tried this posts: http://forums.b2evolution.net/viewtopic.php?t=19389&highlight=update and http://forums.b2evolution.net/viewtopic.php?t=19210 but I am afraid I do not realy get what and where to change.

aprox wrote:

Yes I did.
so far I just copied the files again as you said, but it gives me the same problem again:

The files and the database go hand in hand. Meaning the files say to the database "are you the version I expect to see" and if not you get a message saying 'wrong version'.

Restore the files and the database, see that it works properly, THEN see about upgrading.

Actually before you try upgrading again talk to your host about innodb support, and maybe search these forums for innodb to see if anyone else has had a trouble upgrading that is related to innodb. That is only a guess by the way - about it being related to innodb. But for sure restore the files and database to see a working blog again.

is it possible to upgrade the database manually, it seems that the provider is not allowing certain things to work.

I am hosting with strato.de and they write in the FAQ

important information

* multilevel quries like "SELECT * FROM table1 WHERE id IN (SELECT id FROM table2);" are not allowed
* SELECT... INTO TABLE is not allowed

To access the database you can use Telnet access (avalable with premium packets) and use the interface "mysql monitor" In oder to create a connection from the webpages to the database you must wirte a CGI-script. We have installed the database interface (dbi) as well as MySQL-module for perl, so that you can easily work with perl programming language.

(translated form German)

at a later stage it states

further changes with Version 4:

* Query Cache
(http://www.mysql.com/doc/en/Query_Cache.html)
* UNION statement, a long-awaited standard SQL feature
* new character set, latin1_de
* Multi-table DELETE and UPDATE statements
* full text index (for searching in large texts)
* InnoDB/ InnoDB Transaction Model (seit 3.23.x)
(http://www.mysql.com/doc/en/InnoDB_overview.html)
* u.v.m.

I therefore wonder wether there is an alternative installation solution besides the automatic one?

Thanks so much for your advice.