Thread

Hello all,

I’ve got EE 1.6.9 and MSM running on a Windows Server 2008 box just fine.

I downloaded the latest version of 2.1.3 and replaced all of the files as required. I also downloaded the MSM 2.0 version and uploaded those 3 files.

I edited the permissions for the /cache/ directory as well as the database.php and config.php files.

Then I went to:

http://{site_url}/system/

to update. I successfully got the prompt to upgrade.

It starts the upgrade process, and I can see it’s cycling through the queries and fixing them, according to the update tool. However, partway through, with this url:

http://{site_url}/system/index.php?C=wizard&M=do_update&agree=yes&ajax_progress=yes&language=english

I suddenly get a 500 - Internal server error. I’m not sure why in the middle of the upgrade this would happen, because the base URL was working just fine before.

Does anyone have any experience or suggestions with this? I’ve been trying, but I’m about out of ideas.

The config.php file still says version 169. Also, could it be the wrong license # that messes it up? We have multiple license #‘s as we’ve had to upgrade our MSM account a few times to accommodate more sites (we work in academia), so the question is which one do I use?

Thank you in advance for your help.

Slankman,

A 500 error is a server error. Can you double check you got correct write permissions for system/config/config.php?

Open up system/installer/config/config.php

and change

$config['uri_protocol']    = "AUTO";

to

$config['uri_protocol']    = "QUERY_STRING";

Also, could it be the wrong license # that messes it up?

Your license number would not cause an issue like this

Can you also confirm your server meets the requirements for EE2?

Hey there,

Thanks for the support. I made all of those changes, but couldn’t figure out the problem.

On the same server, I created a new install of 1.6.9, installed MSM and upgraded and it seemed to work. No 500 errors. So I’m a bit confused.

I’m working on the new install and will revisit the older install later. Thanks for your help! We can close this for now.

Closing as requested. Feel free to start a new thread if you have any more questions.