We have 3 custom modules using OpenAccess that are *not* based on Content. We have fairly simple model classes, with provider classes that are based on the OpenAccessContext class. This was taken partially from Josh Morales' forum post on Intra-site modules.
Not sure if it's a factor here, but we deviated from Josh's example by placing the guts of the module code (provider, model, manager) in a separate assembly, but used Josh's method of adding admin pages and registering the module as part of the web application code.
This all works fine for each module individually. We can access the admin page(s), add/edit items, etc. However, if we try to access the administrative page of either of the other two modules, we get the following error:
Type is enhanced and registered, but not available from the database class meta data. This can be caused by a wrong connection id or configuration.
Parameter name: src
Actual value was <
module assembly name here>
Restarting the application, we are able to access the module that cause the error - only to receive the same error when we try to access one of the other modules.
Some investigation turned up references to this in the OpenAccess forums from several months ago indicating that database connection sharing may be the problem. All of our modules are using the connection string found in the DataConfig.config file for their connections.
Is this an issue with OpenAccess? Could it be that we are not releasing some of our resources properly - maybe missing some important "Dispose" in our provider or manager? Obviously, the in-built Sitefinity modules all operate together without issue, so it seems to be an implementation issue on our end, but we have no idea where to start trouble-shooting.
We are at a critical moment in a project (of course! ;)), so any help would be greatly appreciated. I don't recall having this issue in 3.x, but understand things are vastly different now.