This is coming up fairly often in the forum. I don’t have a solid answer but on thing that has come up is the use of caching plugins.

Guys I choose to come back I tell you what I found: I went thru the following linkhttp://raphaellove.com/wordpress-upgrade-admin-lockout-fix-3-4-1/
My conclusion from what I found is that the problem was caused by
W3TotalCache plugin. The plugin has some files that are not located inside Wp-Content/plugins. You will still have the problem even if you delete the plugin. You have to manually delete all associated files that are installed in the blog root folder such as “dbcache”, advancecache” etc. Once you do that, you will be able to get back to admin section – after you clean up those cache file. I hope I have helped someone in the process. Have a nice day. God bess. (www.woem.org/blog)

Unfortunately, we NEVER had the W3TotalCache installed on the site. As a matter of fact we never had any cache plugins installed and we have a real minimum (and totally unrelated to creating files/folders) of plugins installed.

I don’t think everyone on this thread has the same issue.

I have to agree with you. 🙁
So, has anyone else faced the exact same errors as we did?

Indeed this is a very sordid thread, it appears some people are having similar problems, but not exactly the same.

There definitely appears to be a problem with 3.4.1 on the ADMIN PAGE side of things. On my site, mindzoom.dk, things work fine, but if attempt to view single posts whilst LOGGED IN, the java that runs the WP BAR at the TOP and the SIDEBAR crashes. It just dies.

So in fact, many plugins work JUST FINE, it’s just when you are logged in to the admin, something goes dreadfully wrong, keeping us all up late at night.

Indeed this is a very sordid thread, it appears some people are having similar problems, but not exactly the same.

I agree. So I am trying to keep it focused on the specific errors.

I am talking about the EXACT same errors, because this was a fresh 3.4 multisite install. As I mentioned before, there were only a couple very basic plugins activated and NO cache ones.
Furthermore, if we take a closer look,the errors appeared on the basic WordPress Tables:
1. _users
2. _usermeta
3. _blogs
4. _blog_versions
5. _registration_log
6. _site
7. _sitemeta
8. _signups

That’s the reason why I ask for people to take a look at their error_log and report if they find the EXACT same errors. (I hope not but I am sure others must have experienced them.)

It would be really helpful if one of the WordPress “gurus” could have a look at this thread as well.

If you have an idea of what the errors mean (and explain), I would really appreciate it.
I would really like to start this new multisite with as few errors as I can before giving it live for customers. At this point the db is really “clean”. But it will end up having more than 40 plugins (couple dozens “heavy ones”) activated and (hopefully!!!) a few hundred sites. So, I’d hate having malfunctions further down the line.

PS: The only other plugin I had/have activated that could probably make a difference (though I don’t see how) is a domain mapping plugin.

Are those your actual table name? For example, is “47mp_users” one of the tables in your database? If that is the case the “why” is superficially pretty easy. The table already exists. You can’t create a table that already exists. The syntax should be “CREATE IF NOT EXISTS” to create only if it doesn’t exist and otherwise leave it alone or “ALTER TABLE” to update/alter the table structure.

The weird bit, the not superficial part, is that WordPress uses a function called dbDelta which should take care of create/alter problem just mentioned. That seems to be failing.

I only manually changed the name from something else to 47mp_users for security reasons before pasting the errors on pastebin. So yes. Those are the “actual” table names.

The weird bit, the not superficial part, is that WordPress uses a function called dbDelta which should take care of create/alter problem just mentioned. That seems to be failing.

That is exactly the bit I am talking about and keep wondering “Is it me?”. How come others don’t face the same issues?
As you mention, if the dbDelta function is not triggered preperly and/or on time, it could probably cause problems (resulting on double entries) with reactivating/upgrading plugins (when creating custom tables is involved), or the core itself. [worries] 🙁