BTW, by default HTTP binding is removed, only HTTPS is allowed. So I thought, lets try to do it over HTTP (port 80) instead of HTTPS (port 443). at .SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at .SoapHttpClientProtocol.Invoke(String methodName, Object parameters) at 2010.CreateCacheRefreshPlan(String ItemPath, String Description, String EventType, String MatchData, ParameterValue Parameters) at 2010.c_Displa圜lass136_0.b_0() at (Boolean setConnectionProtocol) at 2010.CreateCacheRefreshPlan(String itemPath, String description, String eventType, String matchData, ParameterValue parameters) at ._Displa圜lass19_0.b_0() at .(SoapHttpClientProtocol soapClient, IPrincipal userPrincipal, Func1 func) at .SubscriptionService.CreateCacheRefreshPlan(IPrincipal userPrincipal, CacheRefreshPlan cacherefreshPlan) at .V2.(CacheRefreshPlan entity) at .(ODataPath oDataPath, T value) at lambda_method(Closure, Object, Object ) at ._Displa圜lass6_2.b_2(Object instance, Object methodParameters) at .ReflectedHttpActionDescriptor.ExecuteAsync(HttpControllerContext controllerContext, IDictionary2 arguments, CancellationToken cancellationToken) - End of stack trace from previous location where exception was thrown - at .Throw() at .HandleNonSuccessAndDebuggerNotification(Task task) at .ApiControllerActionInvoker.d_1.MoveNext() - End of stack trace from previous location where exception was thrown - at .Throw() at .HandleNonSuccessAndDebuggerNotification(Task task) at .ActionFilterResult.d_5.MoveNext() - End of stack trace from previous location where exception was thrown - at .Throw() at .HandleNonSuccessAndDebuggerNotification(Task task) at .ExceptionFilterResult.d_6.MoveNext().| RequestID = s_9b953a1c-bc48-41f3-ad5b-12e903990663īy now I may have read 95% of the forums/blogs/solutions/documentations without luck. 00:47:55.7026|ERROR|63|OData exception occurred: : The request failed with HTTP status 401: Unauthorized. Data source have basic credentials and on the data source page test connection is successful with the basic SQL login credentials.But whenever I try to add a refresh schedule i get the same error. And I tried to add refresh schedule on another Import mode PBIX report. Upon checking I saw the schedule refresh failed. This morning one of the colleagues reported that the data wasnt refreshed. All the data source connection remain the same (non SSL remote SQL Server). I have upgraded the SSL to a SAN SSL the other day on the report server. I have reports that runs on Imported mode from a remote SQL Server which doesnt accept encrypted connection. My PowerBI report server (on prem) was previously on a self cert SSL before. I have just experienced a bizarre problem today.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |