Regarding objectQualifier: Yes, it is supported in DNN 6 (and 7).

The error you posted shows that it is occurring early in handling the request as it occurs when fetching the skin for the page but is too non-specific to give a clue to its origin. Most likely it is related to the FileManager.Instance issue. Perhaps the earlier errors logged will give a clue. Only the portion of the error from the StackTrace PropertyName node onward is important here.

---

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

I moved the site back to 5.6.8, cleared the Event Log and opened the 5.6.8 site.  Each time I stop the webserver with IIS and restart it I get the normal Application Start in the logs and I get an UpgradeNet entry.  Not sure if the UpgradeNet entry is normal.

<PropertyName>UpgradeNet</PropertyName>

<PropertyValue>Upgraded Site to .NET 4.0</PropertyValue>

 

The "Upgraded Site to .NET 4.0" being logged each time the site's application pool restarts was an issue back in the late 5.x series and would have been triggered when the application pool was switched to ASP.Net 4.0 in order to update several nodes in web.config. However, it being logged with each startup are a symptom that either the structure of web.config is such that the configuration changes cannot be properly made. This was usually due to the inclusion of a < location > element in web.config. The issue can cause the event log to become "full" with these entries, the web.config file to keep expanding in size, and a real performance hit to be placed on the site. If we can ever get the site upgraded, the issue will go away. However, if it is due to a < location > element in web.config, it is also a cause for concern since some other web.config upgrades may not have been done or will not be done during later upgrades.

Was the switch to ASP.Net 4.0 done from ASP.Net 2.0 or from 3.5?

Regarding the FileManager.Instance issue - unfortunately the last error you posted does not give any additional information.

---

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