Forum Discussion

All41S's avatar
All41S
Frequent Visitor
8 years ago

Error creating Report Scheduler

Hello PowerBI Community,

 

we have an issue creating a Report Scheduler for our PowerBI Reports.

We're using PowerBI Report Server on-premise October 2017.

 

Base are different PowerBI Reports with SQL and Excel Reports as source.

The accountdetails are placed behind the Report and tested successfully.

 

When we're now try creating a scheduled report and the Website - we get this error.

 

Errormessage:

There was an error

Sorry, an error has occurred. Repeat the process.

 

Any Ideas?

 

Thanks!

 

Best regards

All41S

ReportServer
Schedule Refresh

5 Replies

    • All41S's avatar
      All41S
      Frequent Visitor
      8 years ago

      Hello Qiuyun Yu,

       

      sorry for my late reply, the Excelfile is on a server share and is accessable from our internal network with no issues.

      The SQL Database is not a DirectQuery we choose "Import".

       

      So as far i understand you, it should work right?

       

      Any other ideas what could be the issue?

       

      Best regards

      All41S

      • All41S's avatar
        All41S
        Frequent Visitor
        8 years ago

        Today i updated to the newest PowerBi Report Server Version (March 2018)  but still having the same issue.

         

        Any Ideas?

  • Anonymous's avatar
    Anonymous
    Not applicable
    8 years ago

    Hi,

     

    I meet same error when scehduling a report which data source is from SQL data warehouse with import function. We just updated the latest version of Power BI reporting server. If individual scheduler does not work, I don't see much benefit to use the reporting server.

     

    This report can be successfully scheduled in Power BI service without any issue.

    • All41S's avatar
      All41S
      Frequent Visitor
      8 years ago

      I did some tracing today and found out maybe the issue behind the problem.

       

      2018-03-27 10:59:50.5654|ERROR|69|OData exception occurred: Microsoft.SqlServer.ReportingServices2010.RSConnection2010+MissingEndpointException: Fehler beim Herstellen einer Verbindung mit dem Berichtsserver. Überprüfen Sie die Verbindungsinformationen, und überprüfen Sie, ob der Berichtsserver eine kompatible Version verwendet. ---> 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__DisplayClass32.<CreateCacheRefreshPlan>b__31()
   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_31ed7071-df45-47d2-aae1-efb67643786d 
2018-03-27 10:59:50.5810|INFO|78|Sending response. Response code Domain\UserID 500, Elapsed time 0:00:00,7177759| RequestID = s_31ed7071-df45-47d2-aae1-efb67643786d

      I think there is a configuration error?