"The query didn't return a value", Publishing content problem
Hi,
I have a problem on a production environment. When publishing the entire content tree we get a timeout error. So I tried to publish the main nodes one by one, when I try that I get the following error on some of the main nodes.
[code]
Server Error in '/' Application.
The query didn't return a value.
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: System.ArgumentException: The query didn't return a value.
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:
[ArgumentException: The query didn't return a value.]
umbraco.DataLayer.SqlHelper1.ExecuteXmlReader(String commandText, P[] parameters) +122<br />
umbraco.DataLayer.SqlHelper1.ExecuteXmlReader(String commandText, IParameter[] parameters) +53
Version Information: Microsoft .NET Framework Version:2.0.50727.1433; ASP.NET Version:2.0.50727.1433[/code]
Does anybody know how to fix this error and any suggestion about the timeout error when publishing the entire website? We already tried to set the timeout value to 5 min, but still an error.
Using Umbraco v4 final and IIS ON WINDOWS 2003 R2.
"The query didn't return a value", Publishing content problem
Hi,
I have a problem on a production environment. When publishing the entire content tree we get a timeout error. So I tried to publish the main nodes one by one, when I try that I get the following error on some of the main nodes.
[code]
Server Error in '/' Application.
The query didn't return a value.
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: System.ArgumentException: The query didn't return a value.
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:
[ArgumentException: The query didn't return a value.]
umbraco.DataLayer.SqlHelper
1.ExecuteXmlReader(String commandText, P[] parameters) +122<br /> umbraco.DataLayer.SqlHelper
1.ExecuteXmlReader(String commandText, IParameter[] parameters) +53[SqlHelperException: Umbraco Exception (DataLayer): SQL helper exception in ExecuteXmlReader]
umbraco.DataLayer.SqlHelper`1.ExecuteXmlReader(String commandText, IParameter[] parameters) +137
umbraco.cms.businesslogic.web.Document.importXml() +117
umbraco.cms.businesslogic.web.Document.ToXml(XmlDocument xd, Boolean Deep) +37
umbraco.content.PublishNodeDo(Document d, XmlDocument xmlContentCopy) +184
umbraco.content.UpdateDocumentCache(Document d) +168
umbraco.content.UpdateDocumentCache(Int32 pageId) +36
umbraco.library.UpdateDocumentCache(Int32 DocumentId) +98
umbraco.dialogs.publish.Page_Load(Object sender, EventArgs e) +1111
System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +15
System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +33
System.Web.UI.Control.OnLoad(EventArgs e) +99
umbraco.BasePages.BasePage.OnLoad(EventArgs e) +12
System.Web.UI.Control.LoadRecursive() +47
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1436
Version Information: Microsoft .NET Framework Version:2.0.50727.1433; ASP.NET Version:2.0.50727.1433[/code]
Does anybody know how to fix this error and any suggestion about the timeout error when publishing the entire website? We already tried to set the timeout value to 5 min, but still an error.
Using Umbraco v4 final and IIS ON WINDOWS 2003 R2.
Thanks
If you're using full SQL Server (not Express), try to run Profiler and catch actual sql command executing. That could point out exact problem.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.