Today I tried to upgrade a production site, but it did not work out too well.

First, the upgrade itself was fine, but accessing the host instance was a no go.  The page would time out or I would get 503 service unavailable.

I did however notice that other portals on that install would run without a problem.  That lead me to believe that there was an issue with this particular portal.

After failing at that for a few hours, I decided to run a clean install and not an upgrade.  The install went well and I was able to add the skin from the other installs host site so I knew at least that it was not a skin issue.

The problem with the new install came when I tried to add an icon to that page so that it shows up in the menu.  This is how the pages are on the host portal on the site I was attempting to upgrade.

After selecting the image and hitting the button to update the page, it fails.  I then get the same errors as on the upgrade portal and I can no longer access the fresh install.

Has anyone experienced this?  The only non core module that I am using is the Snapsys nav menu.  Everything else is from a clean install.

I will try removing the snapsys menu from the skin to see if it at least loads the page.

UPDATE: Removing the Snapsys menu did not fix the issue.

Thanks,

Vince

it's a known bug (http://support.dotnetnuke.com/issue/ViewIssue.aspx?id=17475&PROJID=2) that has been fixed for 6.0.1

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US

It's going though final changes and testing, I'd estimate 7-10 days until release.

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US