topic Re: New Scheduled Refresh Plan (An error has occurred. Something went wrong. Please try again later. in Report Server

New Scheduled Refresh Plan (An error has occurred. Something went wrong. Please try again later.)

Anonymous — Tue, 29 Oct 2019 09:58:09 GMT

Hi there,

I'm trying to add new New Scheduled Refresh Plan but I got this error An error has occurred. Something went wrong. Please try again later. Even I enabled the SQL server agent please anyone can share with me a solution.

2019-10-29 12:41:50.7731|INFO|33|Received request POST /api/v2.0/CacheRefreshPlans| RequestID = s_b4857b79-3ba2-40d9-8f45-fb9723cc3a3b

2019-10-29 12:41:52.7817|ERROR|33|OData exception occurred: Microsoft.SqlServer.ReportingServices2010.RSConnection2010+MissingEndpointException: The attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version. ---> System.Net.WebException: The request failed with HTTP status 404: Not Found.

at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.SetConnectionProtocol()

at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.SoapMethodWrapper`1.ExecuteMethod(Boolean setConnectionProtocol)

--- End of inner exception stack trace ---

at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.MissingEndpointException.ThrowIfEndpointMissing(WebException e)

at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.SoapMethodWrapper`1.ExecuteMethod(Boolean setConnectionProtocol)

at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.CreateCacheRefreshPlan(String itemPath, String description, String eventType, String matchData, ParameterValue[] parameters)

at Microsoft.ReportingServices.Portal.Services.SoapProxy.SoapRS2010Proxy.<>c__DisplayClass19_0.<CreateCacheRefreshPlan>b__0()

at Microsoft.ReportingServices.Portal.Services.SoapProxy.SoapAuthenticationHelper.ExecuteWithWindowsAuth[TReturn](SoapHttpClientProtocol soapClient, IPrincipal userPrincipal, Func`1 func)

at Microsoft.ReportingServices.Portal.Repositories.SubscriptionService.CreateCacheRefreshPlan(IPrincipal userPrincipal, CacheRefreshPlan cacherefreshPlan)

at Microsoft.ReportingServices.Portal.ODataWebApi.V2.Controllers.CacheRefreshPlansController.AddEntity(CacheRefreshPlan entity)

at Microsoft.ReportingServices.Portal.ODataWebApi.Controllers.Reflection.EntitySetReflectionODataController`1.Post(ODataPath oDataPath, T value)

at lambda_method(Closure , Object , Object[] )

at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ActionExecutor.<>c__DisplayClass10.<GetExecutor>b__9(Object instance, Object[] methodParameters)

at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ExecuteAsync(HttpControllerContext controllerContext, IDictionary`2 arguments, CancellationToken cancellationToken)

--- End of stack trace from previous location where exception was thrown ---

at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

at System.Web.Http.Controllers.ApiControllerActionInvoker.<InvokeActionAsyncCore>d__0.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

at System.Web.Http.Controllers.ActionFilterResult.<ExecuteAsync>d__2.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

at System.Web.Http.Controllers.ExceptionFilterResult.<ExecuteAsync>d__0.MoveNext().| RequestID = s_b4857b79-3ba2-40d9-8f45-fb9723cc3a3b

2019-10-29 12:41:52.7817|INFO|33|Sending response. Response code ali 500, Elapsed time 0:00:02.0092546| RequestID = s_b4857b79-3ba2-40d9-8f45-fb9723cc3a3b

Re: New Scheduled Refresh Plan (An error has occurred. Something went wrong. Please try again later.

addyb77 — Wed, 30 Oct 2019 16:47:15 GMT

Hi,

I also have the same problem and came on to post the same problem. We are using Version 1.6.7206.42072 (September 2019) of PBIRS on SQL Server 2016

Re: New Scheduled Refresh Plan (An error has occurred. Something went wrong. Please try again later.

ali_a — Sun, 03 Nov 2019 15:26:09 GMT

anyone can help us
Please, the problem not solve yet

Re: New Scheduled Refresh Plan (An error has occurred. Something went wrong. Please try again later.

Anonymous — Mon, 04 Nov 2019 06:10:43 GMT

I solved the issue by reinstall report server and restart sql server 🙂

Re: New Scheduled Refresh Plan (An error has occurred. Something went wrong. Please try again later.

mgroebl — Mon, 20 Jan 2020 12:45:29 GMT

Hi, I have a similar issue (same UI message, but slightly different log message), but in my case with a custom security provider.

The problem is that the PowerBI session user doesn't get passed to the internal ReportService2010.asmx request.

See https://github.com/microsoft/Reporting-Services/issues/166 for details.

Any ideas?

Re: New Scheduled Refresh Plan (An error has occurred. Something went wrong. Please try again later.

Anonymous — Wed, 29 Jan 2020 05:40:17 GMT

@mgroebl, You have to an enable the SQL server agent and restart sql server

Good luck 🙂

Re: New Scheduled Refresh Plan (An error has occurred. Something went wrong. Please try again later.

SQLJim — Sat, 06 Aug 2022 20:43:40 GMT

We are using an even newer version 1.14.8179.3738 and have the same problem. We are attempting to use our PowerBI reports server both for PowerBI and also for SSRS reports. Since it does not seem to work, does anyone know if this is specifically prohibited? It looks so much like SSRS, we just assumed it would also allow us to upload and execute SSRS reports and datasources.

Re: New Scheduled Refresh Plan (An error has occurred. Something went wrong. Please try again later.

irshad — Wed, 14 Sep 2022 07:29:50 GMT

We also had same issue and main caused was space issue (0 KB) on E drive where we have power BI report server database. once cleared the files and obtained space, it is working fine.

Regards,

Irshad