Thanks for the info Bill.  

Any idea what would caused this or how to fix/solve the problem?  Permissions are set the same on both websites, one upgraded, one didn't.

 

The FileManager.Instance error is apparently secondary to the original duplicate key error which occurred during the upgrade through v 6.1.0. Did you receive that same error when you again tried the upgrade from 5.06.08 to 6.02.08? If so, let's try to find the duplicate key in the 5.06.08 database and correct it before proceeding with the upgrade to 6.02.08.

Restore the site files and database to 5.06.08.

Using a tool such as MS SQL Server Management Studio, run the following query (after replacing "dbo" with your installation's databaseOwner value and "DNN" with the objectQualifier value, if any):

SELECT ControlKey, ControlTitle, ControlSrc FROM dbo.DNN_ModuleControls WHERE ModuleDefID is null

Look in the result set for any module controls that have the same ControlKey (most likely a null value) and post the results here. One or more are invalid and will need to be corrected or deleted from the ModuleControls table.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner

All 4 of those are artifacts from earlier versions that did not get deleted (AdSense - no longer used) or modified (FeedExplorer - relocated to DesktopModules/Admin/FeedExplorer/ folder) during previous upgrades. You should be able to delete all 4 from the ModuleControls table and try running the upgrade to 6.2.8 again.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner