Who Me Too'd this topic

Who Me Too'd this topic

L2 Linker

Data Retrieval Download error

So, i guess since our last Update to Version 4.2.2, we cant download any reports under the "Data Retrieval" section anymore.

It just throws the following error: Bildschirmfoto 2019-01-28 um 11.24.47.png

 

In the "Web_ESMINT.log" File i get the following two error-lines in the related time-span:

 

2019-01-28T08:01:50.2062+01:00    ERROR    w3wp    26    Cyvera.Management.Web.Controllers.AdministrationController    General    "Failed to download file from url: https://esm.intern.iwelt.de:443/BitsUploads/Logs_28_01_2019-06_57_17_000_f317aad2-22c9-11e9-a13b-acd... System.Net.WebException: The remote server returned an error: (401) Unauthorized.
   at System.Net.WebClient.OpenRead(Uri address)
   at Cyvera.Server.Facades.Download.TrapsDownloader.StreamFile(ServerConfig config, Uri sourceFileAddress)
   at Cyvera.Management.Web.Controllers.AdministrationController.FileDownload(String url)"
2019-01-28T08:01:50.2062+01:00    ERROR    w3wp    26    ApplicationLog    General    "This request has been blocked because sensitive information could be disclosed to third party web sites when this is used in a GET request. To allow GET requests, set JsonRequestBehavior to AllowGet. System.InvalidOperationException: This request has been blocked because sensitive information could be disclosed to third party web sites when this is used in a GET request. To allow GET requests, set JsonRequestBehavior to AllowGet.
   at System.Web.Mvc.JsonResult.ExecuteResult(ControllerContext context)
   at System.Web.Mvc.ControllerActionInvoker.<>c__DisplayClass1a.<InvokeActionResultWithFilters>b__17()
   at System.Web.Mvc.ControllerActionInvoker.InvokeActionResultFilter(IResultFilter filter, ResultExecutingContext preContext, Func`1 continuation)
   at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass25.<BeginInvokeAction>b__22(IAsyncResult asyncResult)"

 

I can't really say for sure what caused this error (Update or Administration-Error).

I already opened a case with Palo Alto Support, but maybe, some of you guys experienced the same behavior and have a fix for it.

 

Kind regards.

Who Me Too'd this topic