Type is enhanced and registered, but not avaiable from the database clas meta data
Sometimes when entering the ecommerce / Sitefinity orders within me generates this error. it may be happening?
Hi Omar,
Thank you for contacting us.
We have been having similar reports before, but we were not able to reproduce the problem. Can you recall when the issue started occurring? Were there any changes made to the products or the workflows? Please check Administration -> Settings -> Advanced -> Workflow -> Providers for any custom configurations.
So far we have established that this error manifests itself when you have two contexts to one database and using one and the same data object simultaneously, including cashed connection. This should be solved by disposing the managers.
var manager = AnyManager.GetManager();
//some logic with the manager here
manager.Dispose();
We are also getting the same issue in Sitefinity 7.2. The way to reproduce this is
Step 1. ) Navigate to Administration->Settings->Advanced->Data->set Enable Data Caching to false
Step 2 .) IISReset
Step 3.) Navigate to any ecommerce front end pages which will be calling any manager like var mgr = Catalogmanager.GetManager(); mgr.GetProducts().FirstOrDefault();
Step 4.) Ideally the exception can occur here. If not then repeat Step 1 and set Enable Data Caching to empty value.
Step 5.) IISReset
By now you should get the error most likely in the index page itself or the page where you are calling the instance of the CatalogManger.
Hope this helps.
Thanks
Praneeth
Hi,
Thank you for the steps provided. Indeed the bug was reopened and then fixed as you can see in our comments in the Feedback portal:
http://feedback.telerik.com/Project/153/Feedback/Details/136225-exception-on-first-load-when-using-relateddata-product-product
The fix has been included in 7.3.5614.0 internal build. You can check our release notes:
http://www.sitefinity.com/developer-network/forums/internal-builds/sitefinity-7.3-internal-builds
Excuse us for the inconvenience caused.
Regards,
Stefani Tacheva
Telerik
Thanks for the confirmation Stefani. This helps. As I am in midst of moving to production is there any quick fix for 7.2 itself?
Hello,
I am afraid that there are no workarounds available for this problem, an upgrade should be performed. More information for the upgrade procedure can be found in our Upgrade documentation article:
docs.sitefinity.com/upgrade
You need to upgrade to latest internal build of Sitefinity 7.3 version or to our latest major one Sitefinity 8.0.
Latest internal builds are available in your account in section Products & Subscriptions -> Latest Internal Builds.
Regards,
Stefani Tacheva
Telerik