ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

MSM Adding Site results in 500 Error

January 24, 2011 3:31pm

Subscribe [3]
  • #1 / Jan 24, 2011 3:31pm

    TacomaWeekly

    17 posts

    We are trying to add an additional site to our MSM install, from four to five. Per the instructions we replaced the sites.php, sites_lang.php and Sites.php files with the new version.  After doing so we get a 500 error when attempting to create or edit sites.  The exact error in our browser is:

    HTTP Error 500 (Internal Server Error): An unexpected condition was encountered while the server was attempting to fulfill the request.

    I checked our Apache error log and no errors are reported.  I double checked the file permissions and they are correct for our install (744, owned by the apache uid/pid).  Rolling back to the previous files resolves the issue but it leaves us without the new site license.

    Without an error in the apache logs I am not sure where to start troubleshooting.  I did note that the build number for the MSM files has changed.  The current version (that 500’s for us) is 20101215, and the working version is 20101018.  I also note that the changelog does not show a 20101215 build, as seen here:

    http://ellislab.com/expressionengine/user-guide/cp/sites/msm_changelog.html

    Can you suggest a troubleshooting direction?

    *Update* - I forgot to mention we are running EE 2.1.1, see the attached image file for a screenshot of Health Check for our site.

  • #2 / Jan 25, 2011 9:37am

    Sue Crocker

    26054 posts

    Hi, TacomaWeekly.

    The MSM and EE versions need to be in sync. Please back up your database and upgrade to EE2.1.3. That should solve the issue.

    Does that help?

  • #3 / Jan 25, 2011 3:12pm

    TacomaWeekly

    17 posts

    I had been stalling on the upgrade after the 2.1.2 issues, but 2.1.3 seems to be stable according to the community.

    Long story short, upgrading to the current EE core fixed my issue.  Thanks!

  • #4 / Jan 25, 2011 3:29pm

    Ingmar

    29245 posts

    Excellent. Please don’t hesitate to post again in case there’s anything else.

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases