Thanks Alex for getting back to me.  Sorry it has been a few days, I have been pretty busy and this upgrade is a somewhat low priority for me at this moment.  To answer your questions;  I can not log in afterwards, nor does the mainpage display or render afterwards.  I do not get the "yellow screen" either.  Instead when I try to go to the base main webpage I get a white screen with the DNN logo and the following text;

DotNetNuke Error: - Version 05.00.01   An error has occurred. An error has occurred.

Return to Site

In addition to this screen the URL displays the following;

Default.aspx?tabid=36&error=The+control+collection+cannot+be+modified+during+DataBind%2c+Init%2c+Load%2c+PreRender+or+Unload+phases.&content=0

This happens right after I try to go back to the main page after the initial upgrade errors posted at the start of this thread. 

Also I am not sure why I am getting the error with "GetPackageByName" in the log file.  This Sproc exists in my DB prior to my upgrade attempt.

Please let me know if you know of any other suggestions for me or if you need any information beyond what I have provided.

Thanks,

Adam

We are currently trying to upgrade from 4.9 to 5.0.1 and we are having the same problem. The stored procedure "GetPackageByName" seems to be missing.

When we compare the packages table from a fresh install to that from the "upgraded" version, there seems to be a difference.

Upgrade:
PackageID, Name, FriendlyName, Description, PackageType, Version, License, Manifest
Fresh:
PackageID, PortalID, Name, FriendlyName, Description, PackageType, Version, License, Manifest, Owner, Organization, Url, Email, ReleaseNotes, IsSystemPackage

When we had a look at the stored procedure "GetPackageByName" in the DNN 5 version it uses PortalId wich doesnt exist.
 

As a test for when we do migrate. Check if our modules / skins / ... still work in 5 and see where we have to make changes.

Does the fact that its not recommended for production change the fact that the upgrade fails now? As it seems to me the upgrade scripts are executed in order.