Every so often, we get a really odd error on random pages on our site running on azure.
The stack trace looks like this..
An unhandled exception occurred
--------------------------------------------------------------------- System.Net.WebException: The remote server returned an error: (404) Not Found.
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at ImageProcessor.Web.Helpers.RemoteFile.<GetWebResponseAsync>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at ImageProcessor.Web.Services.RemoteImageService.<GetImage>d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at ImageProcessor.Web.HttpModules.ImageProcessingModule.<ProcessImageAsync>d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.TaskAsyncHelper.EndTask(IAsyncResult ar)
at System.Web.HttpApplication.AsyncEventExecutionStep.OnAsyncEventCompletion(IAsyncResult ar)
It doesnt have any line numbers or relate to any file and it happens on seemingly unrelated things.
The error message indicates that the remote image service is throwing a 404. In older versions (pre v4.5.0) that would cause an exception to be thrown but now that will be passed on for the server to handle.
Are you using the CloudImageService to handle requests to blob storage
or is that a request to an image outwith your domain that you have no control over?
If you upgrade to the latest then you should get an indicator of which file is throwing the error.
We have 4.3.6 installed currently. We are using image processor both on local and remote images. The local images are just standard media or in a static image folder.
we use remote.axd to do the remote files.
So I'm guessing an Img Processor update is in order.
Odd error in Umbraco Logs on Azure... Image processor issue?
Every so often, we get a really odd error on random pages on our site running on azure.
The stack trace looks like this..
It doesnt have any line numbers or relate to any file and it happens on seemingly unrelated things.
Any one else seeing this?
Looks like the issue is with the storage provider. Do you use the azure cache provider too?
Nope we are not using the azure storage provider.
The error message indicates that the remote image service is throwing a 404. In older versions (pre v4.5.0) that would cause an exception to be thrown but now that will be passed on for the server to handle.
Are you using the CloudImageService to handle requests to blob storage or is that a request to an image outwith your domain that you have no control over?
If you upgrade to the latest then you should get an indicator of which file is throwing the error.
We have 4.3.6 installed currently. We are using image processor both on local and remote images. The local images are just standard media or in a static image folder.
we use remote.axd to do the remote files.
So I'm guessing an Img Processor update is in order.
The update should tell what image is being requested since the static file handler will now take over. It's definitely a remote image missing though.
is working on a reply...