Restore Error Message after upgrade from OC 2.0 to 2.0.1.1

I've been working with OC 2.0 and recently decided to try upgrading my version to 2.0.1.1 on my local server. Prior to the upgrade, I backed up all my data and then attempted a Restore in the new version. (I'm not even sure if this is the correct process).

As part of the upgrade, I created a new database and named it differently from the original one created for OC 2.0

Following the Restore, I received an error message with the following:

Warning: fopen(/Applications/XAMPP/xamppfiles/htdocs/store/system/logs/) [function.fopen]: failed to open stream: Is a directory in /Applications/XAMPP/xamppfiles/htdocs/store/system/library/log.php on line 6

Fatal error: Call to a member function get() on a non-object in /Applications/XAMPP/xamppfiles/htdocs/store/admin/index.php on line 79

And now this message is persistent on the top of my admin screen. Before I go ahead and do any more damage, I'd like to know if anyone knows the reason for this error and how to fix?

Thanks

fullspec wrote:I've been working with OC 2.0 and recently decided to try upgrading my version to 2.0.1.1 on my local server. Prior to the upgrade, I backed up all my data and then attempted a Restore in the new version. (I'm not even sure if this is the correct process).

As part of the upgrade, I created a new database and named it differently from the original one created for OC 2.0

Following the Restore, I received an error message with the following:

Warning: fopen(/Applications/XAMPP/xamppfiles/htdocs/store/system/logs/) [function.fopen]: failed to open stream: Is a directory in /Applications/XAMPP/xamppfiles/htdocs/store/system/library/log.php on line 6

Fatal error: Call to a member function get() on a non-object in /Applications/XAMPP/xamppfiles/htdocs/store/admin/index.php on line 79

And now this message is persistent on the top of my admin screen. Before I go ahead and do any more damage, I'd like to know if anyone knows the reason for this error and how to fix?

Thanks

Your must upgrade version 2.0.0.0 database to version 2.0.1.1

Have you managed to solve this issue? How?

Did you solve this?