Home » discuss » Public forums » iMIS Community

Unable to load requested business object Document ERROR

Posted February 13th, 2012 by tmndi
|

I've been seeing this error alot on our WCM site. Mostly during publishing but occassionally with no reason. Recycling the application pool resolves the issue but that is not the best solution for customers who are not hosting their own WCM site. Anyone else see this or have any tips to prevent from happening?

Server Error in '/' Application.
 --------------------------------------------------------------------------------

Unable to load requested business object Document (DocumentVersionKey=d2a2810e-00ba-462e-a9a6-ee64c386bf7e, publishedOnly=True)
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: Asi.Business.BusinessItemLoadException: Unable to load requested business object Document (DocumentVersionKey=d2a2810e-00ba-462e-a9a6-ee64c386bf7e, publishedOnly=True)

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[BusinessItemLoadException: Unable to load requested business object Document (DocumentVersionKey=d2a2810e-00ba-462e-a9a6-ee64c386bf7e, publishedOnly=True)]
Asi.Business.Common.DocumentController.Document(Guid documentVersionKey, BusinessContainer container, Boolean publishedOnly, Boolean forceReloadOnInitialFailure) in c:\Builds\42\ScrumV3\15.2.0_MainFoundation_Commit\Sources\imis.net\Packages\Platform\Asi\Business\Common\DocumentController.cs:436
Asi.Business.Common.DocumentController.Document(Guid documentVersionKey, BusinessContainer container, Boolean publishedOnly) in c:\Builds\42\ScrumV3\15.2.0_MainFoundation_Commit\Sources\imis.net\Packages\Platform\Asi\Business\Common\DocumentController.cs:380
Asi.Atom.AtomBaseHierarchy.LoadFromHierarchy(Hierarchy hierarchy, AtomBaseHierarchy& item, Boolean raiseOnDeserialization, Boolean publishedOnly) in c:\Builds\42\ScrumV3\15.2.0_MainFoundation_Commit\Sources\imis.net\Packages\Platform\Asi\Atom\AtomBaseHierarchy.cs:514
Asi.Business.ContentManagement.Navigation.GetFromHierarchy(Hierarchy hierarchy, Boolean publishOnly) in c:\Builds\42\ScrumV3\15.2.0_MainFoundation_Commit\Sources\imis.net\Packages\Content Management\Asi.Business.ContentManagement\Navigation.cs:1363
Asi.Business.ContentManagement.NavigationHierarchy.get_Navigation() in c:\Builds\42\ScrumV3\15.2.0_MainFoundation_Commit\Sources\imis.net\Packages\Content Management\Asi.Business.ContentManagement\NavigationHierarchy.cs:145
Asi.Web.AsiSiteMapNode.get_Navigation() in c:\Builds\42\ScrumV3\15.2.0_MainFoundation_Commit\Sources\imis.net\Packages\Platform\Asi.Web\SiteMapProviderBase.cs:1134
Asi.Web.SwappableSiteMapProvider.IsAccessibleToUser(HttpContext context, SiteMapNode node) in c:\Builds\42\ScrumV3\15.2.0_MainFoundation_Commit\Sources\imis.net\Packages\Platform\Asi.Web\SiteMapProviderBase.cs:687
System.Web.SiteMapNode.IsAccessibleToUser(HttpContext context) +17
Asi.Web.SwappableSiteMapProvider.GetChildNodes(SiteMapNode node) in c:\Builds\42\ScrumV3\15.2.0_MainFoundation_Commit\Sources\imis.net\Packages\Platform\Asi.Web\SiteMapProviderBase.cs:454
Asi.Web.SiteMapProviderBase.GetChildNodes(SiteMapNode node) in c:\Builds\42\ScrumV3\15.2.0_MainFoundation_Commit\Sources\imis.net\Packages\Platform\Asi.Web\SiteMapProviderBase.cs:212
System.Web.SiteMapNode.get_ChildNodes() +30
System.Web.UI.WebControls.SiteMapDataSource.GetNodes(SiteMapNode node) +55
System.Web.UI.WebControls.SiteMapDataSource.GetNodes() +345
System.Web.UI.WebControls.SiteMapDataSource.GetTreeView(String viewPath) +35
System.Web.UI.WebControls.SiteMapDataSource.GetHierarchicalView(String viewPath) +32
System.Web.UI.HierarchicalDataSourceControl.System.Web.UI.IHierarchicalDataSource.GetHierarchicalView(String viewPath) +10
Telerik.Web.UI.DecoratingDataSource.System.Web.UI.IHierarchicalDataSource.GetHierarchicalView(String viewPath) +13
Telerik.Web.UI.HierarchicalControlItemContainer.GetHierarchyData(IEnumerable data) +81
Telerik.Web.UI.HierarchicalControlItemContainer.PerformDataBinding(IEnumerable data) +260
System.Web.UI.WebControls.DataBoundControl.OnDataSourceViewSelectCallback(IEnumerable data) +128
System.Web.UI.DataSourceView.Select(DataSourceSelectArguments arguments, DataSourceViewSelectCallback callback) +33
System.Web.UI.WebControls.DataBoundControl.PerformSelect() +143
System.Web.UI.WebControls.BaseDataBoundControl.DataBind() +74
System.Web.UI.WebControls.BaseDataBoundControl.EnsureDataBound() +66
Telerik.Web.UI.RadDataBoundControl.OnPreRender(EventArgs e) +22
System.Web.UI.Control.PreRenderRecursiveInternal() +103
System.Web.UI.Control.PreRenderRecursiveInternal() +175
System.Web.UI.Control.PreRenderRecursiveInternal() +175
System.Web.UI.Control.PreRenderRecursiveInternal() +175
System.Web.UI.Control.PreRenderRecursiveInternal() +175
 

‹ Access keywords for user defined fields in the web viewUnable to load requested business object Document ERROR ›
login or register to post comments | printer friendly version

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

same issue?

On February 13th, 2012 Henry Huey says:

http://www.imiscommunity.com/unable_to_load_requested_business_object_document_documentversionkey_084a6c22_04ac_4ab5_bd3f_3c00ed08da25_publishedonly_true 

The DocumentVersionKey from your stack trace doesn't point to an iMIS system document.

login or register to post comments

Looks like the same

On February 13th, 2012 tmndi says:

Looks like the same issue.

How do you identify the content that needs to be added back?

Terry Hammond enSYNC Corporation Fort Worth, TX terry@ensync-corp.com

login or register to post comments

A few things

On February 13th, 2012 Courtney Weatherton says:

1. You can run the following SQL to find out what the document is: "select [dbo].asi_PublishedDocumentPath('d2a2810e-00ba-462e-a9a6-ee64c386bf7e')". Perhaps if you can track down what document it is, you can see if there are access settings on it preventing the current user from accessing it.
2. Prior to the 15.2 release, we noticed that sometimes a document might be secured to "Authenticated users" (e.g. Logged in users) but even an authenticated user couldn't access it. We added some extra logic into the 15.2 release to make sure this never happens any more. If you're version of iMIS is pre-15.2, you may be seeing one of the symptoms we fixed.
3. The publishing service will impersonate a specified user when publishing content - this is defined in the PublishService.exe.config file. By default, it's MANAGER. But you could double check that this user is a system administrator.

Hope this helps,
Courtney

login or register to post comments

No action taken yet

On February 13th, 2012 tmndi says:

1. I did get a value returned from the query.  (My Profile)

2. The navigation item in #1 is set to be accessed by authenticated users only. This is a 15.2 implementation.

3. MANAGER is the publish user. Confirmed is a system administrator.

Terry Hammond enSYNC Corporation Fort Worth, TX terry@ensync-corp.com

login or register to post comments

Out of ideas

On February 13th, 2012 Courtney Weatherton says:

Oh, I supposed if I'd have looked closely at the stack trace, I would have known you were on 15.2 :)

What about the content "My Profile" is pointing too? Is it likewise secured to authenticated users?  And if you have a content collection organizer on the page, does each piece of content it points to use the same access setting?

Though, this stack trace does look specific to navigation - not content.  If it's not a top-level navigation, maybe walk you way up to the parent, grand-parent, etc. nodes and make sure the user has access to each of them?  I'm guessing the stack trace looks a bit different when you see the same error in publishing.

Apart from that, I'm at a loss.  The only inconsistencies I had seen with document permissions were what I mentioned being fixed in 15.2 - and I don't think navigation was one of the problem areas.  Maybe Tech Support has seen something like this before.

login or register to post comments