Clearly there are/were a number of issues with v 7.00.03. Among them is the fact that if an admin or host attempts to log in and the instance is set to use the ControlBar the login will fail with an "instance of object not found" error.

With the release of 7.00.04 I was hopeful that this issue had been corrected. It has not.

For the record, we have verified that we are running .NET 4.5 and I have checked the list of .dll files that another user indicated were not upgraded for some reason. Ours were.

We have another instance of DNN with only a couple of portals that is working just fine.

Hopefully someone will figure this out.

While RibbonBar might work it’s just a temporary solution to being able to edit right away... it’s not what everyone wants to use.  We have the same issue with the Edit Page not working in the ControlBar.

What we were told is that we were supposed to upgrade from 6.2.6 to 7.0.4 but instead we went from 6.2.3 to 7.0.4

Our development install works and this is its upgrade path 6.2.3 to 7.0.2 to 7.0.4 ... NET 4.5 isn’t installed on our server but most likely would have no effect.

IT ended up being in the file system not the database.  We were able to use the upgraded DB for the site where the EDIT PAGE isn’t working against the files in the upgrade that was and it worked.

So it appears it’s a problem with the upgrade path.

Aaron

in SQL Server Management Studio, connect to the dabase server and make sure you are using the correct database.

Then

select SettingValue from HostSettings where SettingName = 'ControlPanel'

See what it says. Mine says "Admin/ControlPanel/RibbonBar.ascx"

If yours is different, you can check the location (physical file path in your DNN install) and see if the ascx file is where your database thinks it is. If not, but the RibbonBar is where it should be according to my output, then you can

Update Hostsettings
    set SettingValue = 'Admin/ControlPanel/RibbonBar.ascx' where SettingName = 'ControlPanel'

Obviously you want to proceed with caution. I often precede such updates with a "begin transaction" and execute that, and then run the update statement. You should get a message that 1 record was updated. If that isn't the case, then I'd do some selecting to find out what all happened, and be ready to do a "rollback transaction" which puts things as they were. But really, you should have no issues, and 1 record should be updated, and when you do a select, it should look fine. So then you need to close out the transaction with a "commit transaction" statement. Execute that. Then go back to your site and see if you are able to log in.