6.2.0 did refactor some of the page logic (primarily around the level parameter) so perhaps this has something to do with your problem, however a quick look through gemini does not show others experiencing it which suggests it's localized to your install. Typically when that happens an upgrade fails for some reason (I helped a user debug a page related issue where it was caused by some triggers they had created on the core "tabs" table) - i'd recommend you double-check that the upgrade scripts all worked as expected - see http://www.dotnetnuke.com/Resources/W... to see where the relevant logs are and please post back any exceptions in them

I'd also recommend enabling log4net to ALL - see http://www.dotnetnuke.com/Resources/W... for details how to, in case that reveals anything (e.g. perhaps someone has deleted the page template file)

Finally, if neither of those reveal anything I would suggest running sql server profiler to see what query(s) fail - one of them is clearly expecting a single result and is getting more than 1 result (hence the exceptions) - again this type of thing happens when "foreign" data has been directly added to the system - i've seen cases where import/export tools had created invalid tabs/portals that caused this (and in a few cases core logic was broken around portal aliases which caused a similar exception - however that exception was widely seen within hours of release, hence why im suggesting its likely to be something particular to your site & extensions)

Cathal..

I am very happy to r[port that our sites are now working correctly again.

It was an issue related to Triggers and the 360 menu.

Thanks very much again!!!!!

All thanks for the info.  Got the same issue when adding pages....

Deleted the older extension version from CISS.Sidemenu and problems solved....

Don't know if a newer version from Navigation Suite works OK with 6.2