Hi Arjan

Simon Steed made, which I think is about the same issue - Last response from Sebastiaan from Umbraco HQ is that the issue will be fixed in Umbraco 7.1.9 - Currently there is no announcement about a fix for 6.2.x though

On page 2 Sebastiaan mentions a possible workaround - Have a look here http://our.umbraco.org/forum/core/general/56407-Worrying-errors-in-the-logs-over-last-couple-of-days-from-UmbracoWebSchedulingScheduledPublishing-?p=1

Hope this helps.

/Jan

Hi Jan, thanks for your reply. I had already noticed this workaround, but since even Umbraco HQ doesn't know which (negative) side effects this workaround might have, I'm very reluctant to use it.

Hi Arjan

Yes, it's not ideal at all and I do understand if you have concerns using it. I guess it's a matter of trying it out and see if it has any impacts (if possible of course).

Hope the guys manage to provide a fix at some point.

/Jan

I have tested the <httpRunTime fcnMode="Disabled" /> workaround on our 6.2.4 site, but that didn't work. Both errors were still being logged.

Sebastiaan added a patch (.zip) for 6.2.4 to this issue: http://issues.umbraco.org/issue/U4-5728

I've installed the patch, and the errors are gone.

After installing the patch for 6.2.4 the initial errors were gone, but this morning at around 5:10am we started seeing a different error every minute:

2014-11-25 05:10:02,678 [7] ERROR Umbraco.Web.Scheduling.ScheduledPublishing - [Thread 11] An error occurred with the scheduled publishing
System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: The handshake failed due to an unexpected packet format.
   at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
   at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.ConnectStream.WriteHeaders(Boolean async)
   --- End of inner exception stack trace ---
   at System.Net.WebClient.UploadDataInternal(Uri address, String method, Byte[] data, WebRequest& request)
   at System.Net.WebClient.UploadString(Uri address, String method, String data)
   at Umbraco.Web.Scheduling.ScheduledPublishing.Run()
2014-11-25 05:10:02,678 [7] ERROR Umbraco.Web.Scheduling.KeepAlive - [Thread 9] Error in ping
System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: The handshake failed due to an unexpected packet format.
   at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
   at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.ConnectStream.WriteHeaders(Boolean async)
   --- End of inner exception stack trace ---
   at System.Net.WebClient.DownloadDataInternal(Uri address, WebRequest& request)
   at System.Net.WebClient.DownloadString(Uri address)
   at Umbraco.Web.Scheduling.KeepAlive.Start(ApplicationContext appContext)

Just wanted to add I'm also still getting these errors after upgrading from 7.1.8 to 7.1.9. Any suggestions? Cheers.

2014-12-03 10:58:34,260 [7] ERROR Umbraco.Web.Scheduling.KeepAlive - [Thread 16] Error in ping
 System.Net.WebException: The operation has timed out
 at System.Net.WebClient.DownloadDataInternal(Uri address, WebRequest& request)
 at System.Net.WebClient.DownloadString(Uri address)
 at Umbraco.Web.Scheduling.KeepAlive.Start(ApplicationContext appContext, IUmbracoSettingsSection settings)

2014-12-03 11:01:54,299 [7] ERROR Umbraco.Web.Scheduling.ScheduledPublishing - [Thread 8] An error occurred with the scheduled             publishing
 System.Net.WebException: The operation has timed out
 at System.Net.WebClient.UploadDataInternal(Uri address, String method, Byte[] data, WebRequest& request)
 at System.Net.WebClient.UploadString(Uri address, String method, String data)
 at Umbraco.Web.Scheduling.ScheduledPublishing.Run()

Are you running the website on HTTPS? In that cause it MIGHT have something to do with this issue which will be fixed in 7.2.0:

http://issues.umbraco.org/issue/U4-5564

https://github.com/umbraco/Umbraco-CMS/pull/492

@Arjan H. - Yes, the site is running in Azure under https. I've actually had issues with the nuPickers plugin when setting that value to true. I'll try it though and see if it helps.

For reference that issue is: http://our.umbraco.org/projects/backoffice-extensions/nupickers/questionssuggestions/57988-Dependency-Handler-Error

Update: Unfortunately that does not seem to have resolved the issue in 7.1.9. I might try upgrading to the 7.2 RC assuming that the issue is resolved in that.

is working on a reply...