Error with "Publish at" and Distributed calls - bad match?
We have a Umbraco website with 8 webservers, updated ny the distributed calls. We run Umbraco 4.5.2 and .Net 4.0
I works fine when I manually publish a node - but when I use the "Publish at" method - the node is only published on 1 server and the following error comes in the umbracoLog:
Error refreshing distributed list: 'System.NullReferenceException: Object reference not set to an instance of an object. at umbraco.presentation.cache.CacheRefresher..ctor() at umbraco.presentation.cache.dispatcher.InvokeDispatchMethod(DispatchType dispatchType, Guid factoryGuid, Int32 numericId, Guid guidId)'
We're also encountering this identical issue, distributed calls, manual publish fine, but Publish At results in this error message in the umbracoLog table.
System.UnauthorizedAccessException: Access to the path 'D:\<THE SITE FOLDER>\App_Data\umbraco.config' is denied.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.File.Delete(String path)
at umbraco.content.DeleteXmlCache()
at umbraco.content.PersistXmlToFile(XmlDocument xmlDoc)
at umbraco.content.PersistXmlToFile()
at umbraco.presentation.requestModule.context_PostRequestHandlerExecute(Object sender, EventArgs e)
at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Could it have something to do with the umbraco.config being in the App_Data folder now? Any special rules applied to that folder in .net that may cause this? I don't have direct access to the production servers so I can't poke around.
I'm experiencing the same error, same problem, is this going to be fixed in a future release? I imagine most large sites which may be using publishing features, will also be using distributed calls, voted for the issue on Codeplex, got 7 votes now.
Error with "Publish at" and Distributed calls - bad match?
We have a Umbraco website with 8 webservers, updated ny the distributed calls.
We run Umbraco 4.5.2 and .Net 4.0
I works fine when I manually publish a node - but when I use the "Publish at" method - the node is only published on 1 server and the following error comes in the umbracoLog:
Error refreshing distributed list: 'System.NullReferenceException:
Object reference not set to an instance of an object.
at umbraco.presentation.cache.CacheRefresher..ctor()
at umbraco.presentation.cache.dispatcher.InvokeDispatchMethod(DispatchType dispatchType, Guid factoryGuid, Int32 numericId, Guid guidId)'
Does anybody else have this error?
We're also encountering this identical issue, distributed calls, manual publish fine, but Publish At results in this error message in the umbracoLog table.
Has anyone found a resolution for this? I've posted a codeplex issue here: http://umbraco.codeplex.com/workitem/29237
Unfortunatly, we did not find a solution for this... :-(
But it's good to know we are not alone with this...
File locking in windows. Gotta love it!
I have this issue too! Elmah reports this....
System.UnauthorizedAccessException: Access to the path 'D:\<THE SITE FOLDER>\App_Data\umbraco.config' is denied.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.File.Delete(String path)
at umbraco.content.DeleteXmlCache()
at umbraco.content.PersistXmlToFile(XmlDocument xmlDoc)
at umbraco.content.PersistXmlToFile()
at umbraco.presentation.requestModule.context_PostRequestHandlerExecute(Object sender, EventArgs e)
at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Could it have something to do with the umbraco.config being in the App_Data folder now? Any special rules applied to that folder in .net that may cause this? I don't have direct access to the production servers so I can't poke around.
Hi!
You can find the solution here http://umbraco.codeplex.com/workitem/29237
I'm experiencing the same error, same problem, is this going to be fixed in a future release? I imagine most large sites which may be using publishing features, will also be using distributed calls, voted for the issue on Codeplex, got 7 votes now.
The solution is now a dead link, as they moved to github.
Can anyone here remember the solution? i have this issue and im getting a 403 whenever we hit the CacheRefresher.asmx.
I cant understand why, as the app pool user has full permissions to hit the URL, we even allow anonymous but it still gets a 403.
this leads me to believe that umbraco is serving the 403 for some other reason, and its not IIS.
Can anyone help...?
Lets see at: http://issues.umbraco.org/issue/U4-3088
I'm going to prepare a pull request.
We're getting this same issue now. Did anyone resolve it?
You can see the old 'solution' page here, but not sure how much it helps: https://web.archive.org/web/20120625044628/http://umbraco.codeplex.com/workitem/29237
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.