Hi all,
I just upgraded all the way from 3.2.2 to 3.7.7. then 4.8.2. I had one bump in the road that we did work around, and I thought I would share this in the form of a suggestion.
When the SQL scripts ran for the upgrade from 3.7.7. to 4.8.2, there were 3 error logs reported. The link to "click to view your portal" was overly optimistic, however. Due to a permission problem on the site, 2 of the scripts were unable to run because they could not delete DLL's apparently.
The bad part of this was, the site would NOT come up, due to old DLLs in the bin folder.
The problem was, I didn't know this until 30 minutes of searching this forum, which luckily had good suggestions that got us up. Mostly. We actually removed a file or two too many, as the scheduler is now not working and we have it disabled.
Now the suggestion: The install process has access to those errors, could it possibly write them to the portal as text or HTML files? Does it do this already, and I just couldn't find them? I know it's in the database, and to be sure we looked, but I just don't know the schema well enough to just pull it up under pressure of a production system that is not upgrading happily. If there was even a link on the screen to an upgrade report, I could open that in a new window. You can see there are errors, you even know which scripts have failed, but if those errors are bad enough to keep the site from compiling, well, you're hosed.
Good idea, bad idea, can't be done?
Thanks for your idea and time,
Roberta