Thread

Hey design132,

This is really strange. This should not be happening with a clean DB.

Are you disabling all of your Add-Ons? 2.1 did have some issues with caching which would produce this error, but that should be covered in the update process.

Can you try that?

Thank you,

Here’s the problem with disabling all of my addons is that I will lose whatever information I have in there.  For instance, calendar and user module from solspace if removed would eliminate all our users and calendar events.  I did clear my cache and the same issue remains.  Is there a way to perform the upgrade and eliminate this part of it?

Hey design132,

We can side track the Add-Ons. Forget that.

A Proxy and Load Balancers really confuse the updater. So please keep that in mind. If this site is still behind anything like that, this could cause issues.

I would compare the database to the updates/ud_211.php file to see if the changes already exists. Even though this is a known good DB that was backed up before any upgrade attempts, it’s acting like a DB that has been through a partial update. If you can compare your DB with the schema changes in the file that would really help.

Out of curiosity, how large is this database?

Please let me know how this goes.

Cheers,

hmm, we are on Engine Hosting servers so I couldn’t imagine that they would have anything hindering an EE install.  The DB was backed up on the 26th, the upgrade happened on the 27th… I thought?  My mind is not clear since that was a couple weeks ago.  I’m just wondering if it is a bad DB… which obviously it seems to be… how can we work around this issue— is there something I can remove before the upgrade attempt so it doesn’t throw this error?

The database itself is 3.78MB.

I opened my db and it shows the exp_comment_subscriptions table… but the file ud_211.php does not contain any such thing.  On line 101 of the updates/ud_211.php it shows this:  $this->EE->dbforge->create_table(‘comment_subscriptions’);

Is it possible to install to a fresh DB, and then overwrite with my existing DB?

Thank you guys again for all your help and support on this.

Hey design132,

That is an option. You would create a new DB and then import the data.

So this DB backup does have the table already that is being created in the update process?

So sorry for all this run around, I know it’s frustrating.

Cheers,

This is turning into a nightmare for me.  I’ve deleted my database, reuploaded all files to the server and run the installer:

All pre-installation tests have been completed successfully and no errors were detected.

If you are ready to install ExpressionEngine version 2.5.2 click the link below:

Click here to install a brand new copy of ExpressionEngine

when I click “I agree to abide by the license Terms and Conditions as stated above.” and it goes to the next page it’s just blank.  now our entire site is down.  Is there anyone whom can help us out on this.  Thanks.

Hey design132,

This is on your main server with you main site? Is there anyway to can do this on a dev server or a different directory? To get the site back up, I would roll back and then just to be safe, I would work locally until the update process worked. Is that something you can do?

The Server Wizard reported all green? Blank pages tend to be PHP errors, but not always the case.

I do not know where in the process the update is, but you can try putting $debug = 1; on your site’s main index.php file and under the Error Reporting section. That might give us a clue.

Support is off for the day, but I will keep checking here as I am able to see how things are going.

Cheers,

EE server wizard reported all greens: Congratulations! Your server is ready to use ExpressionEngine!

When i put the $debug = 1; on my index.php page under error reporting all I get when I visit the site is an error:  Your config file does not appear to be formatted correctly.

But that could just be because our site isn’t installed.

I mean I’ll do anything at this point just to get the site working after the upgrade.  I can obviously get the site back up and running and we can log in but we will never be able to update it from this point forward given this issue. 

Honestly, why am I receiving a blank page or any errors therefore when it comes to a new installation?

BTW - thank you for checking even when you’re off.  I have always appreciated support from EE when it comes to this because they often do this and trust me, we don’t take it for granted.

Hi design132,

There are many reasons why you may be getting a blank page. Some times it’s caching, sometimes it’s php errors.

Is this being treated as a new install, so new files that are all blank, or are you reusing files from before with a blank database? That could cause issues. If you are going to do a clean install, then you should do totally clean install. If you are going to upgrade, then we need a known good database backup, drop tables, then restore and then update.

Does that make sense?

I would also make sure that you are using a browser with cleared cache or maybe even a different browser.

Are you able to look at the system logs at all? Maybe Apache can tell us a bit about this?

This is difficult without seeing it, please forgive me if I am asking you stuff you already tried.

Thanks,

ah ha, ok so here’s the thing and this is my fault.  All I’m doing is overwriting the current files on my server with the files from the EE installation folder that I downloaded from your site.  then, I’m deleting my database so it’s completely blank and ready for a new install.  If I were to remove everything, I’d lose all my modules etc right?  Good call on the cache, i’ve cleared my cache but the issue remains.

lemme ask a quick question from ya… if I were to litearlly do a clean install and remove everything… then re-install all modules from their installation zip files from solspace, then after the site is up, overwrite my database with the one we have now, would that mess anything up?  Would I lose anything?

Ok this is what I did:

1) deleted the system and themes folder on my server.
2) uploaded a fresh copy of EE 2.5.2
3) deleted the old database.
4) ran the installer and loaded a new installation of EE 2.5.2
5) deleted the database and overwrote it with my copy that I had before the failed upgrade.
6) overwrote the system and themes folder with my backed up system/themes folder with all my modules in it.
7) logged back in successfully, system was upgraded and everything is working.

We’ll see what happens the next time I go to upgrade.  LOL You can close this out.  Thanks.

Hey design132,

I was just about to submit my really long answer to you, which basically detailed the steps you took.

Nice work here man, I mean it, nice work. I am really sorry this was such a headache for you, but really glad you are upgraded and working.

I will leave this open just in case something comes up. Would you mind touching base here tomorrow and letting me know things are still good?

Thanks,

Thanks!  and thank you again for all your help.  You guys rock on the support!

Hey design132,

My pleasure! Thank you for the compliment!

If you need anything else, please just let me know by opening a new thread.

Cheers,