Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!

Reply
hfleitas
Frequent Visitor

Create scheduled refresh plan. An internal error occurred on the report server.

Running Power BI Report Server Version 1.3.6816.37243 (Build 15.0.2.557), Released: August 30, 2018

 

Cannot create scheduled refresh plans for Power BI reports.

 

An error has occurred.

An internal error occurred on the report server. See the error log for more details.

 

C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles\RSPortal_2018_09_29_00_00_06.log (see below)

 

The ReportingServicesService does not log an error for this event.

 

Is this happening for other ppl as well or could there be a fix? 

 

Thx,

Hiram

 

 

2018-09-29 00:01:01.9967|INFO|147|Received request POST /api/v2.0/CacheRefreshPlans| RequestID = s_b27ccbbb-bbe2-4ad9-a2fd-2c992ebeb78a 
2018-09-29 00:01:02.0123|ERROR|147|OData exception occurred: System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: An internal error occurred on the report server. See the error log for more details. ---> Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details.
   at Microsoft.ReportingServices.Library.ReportingService2010Impl.CreateCacheRefreshPlan(String ItemPath, String Description, String EventType, String MatchData, ParameterValue[] Parameters, String& CacheRefreshPlanID)
   at Microsoft.ReportingServices.WebServer.ReportingService2010.CreateCacheRefreshPlan(String ItemPath, String Description, String EventType, String MatchData, ParameterValue[] Parameters, String& CacheRefreshPlanID)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at Microsoft.SqlServer.ReportingServices2010.ReportingService2010.CreateCacheRefreshPlan(String ItemPath, String Description, String EventType, String MatchData, ParameterValue[] Parameters)
   at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.<>c__DisplayClass130.<CreateCacheRefreshPlan>b__12f()
   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_b27ccbbb-bbe2-4ad9-a2fd-2c992ebeb78a 
2018-09-29 00:01:02.0123|INFO|84|Sending response. Response code UPCIC\hfleitas 500, Elapsed time 0:00:00.0192955| RequestID = s_b27ccbbb-bbe2-4ad9-a2fd-2c992ebeb78a 

 

1 ACCEPTED SOLUTION
hfleitas
Frequent Visitor

I solved the issue by stopping the old SSRS svc.

The old API /ReportServer/*.asmx of SSRS2017 svc was still running so it connected to the 14.0 api not 15.0 and failed.

View solution in original post

3 REPLIES 3
hfleitas
Frequent Visitor

I solved the issue by stopping the old SSRS svc.

The old API /ReportServer/*.asmx of SSRS2017 svc was still running so it connected to the 14.0 api not 15.0 and failed.

Anonymous
Not applicable

Is it possible that you can provide me with a step to step guidance to this solution

Here you go.

1. RDP into the machine that you installed Power BI Report Server on.

2. If you dont have RDP access, open Computer Manager on your workstation, right click Computer Management (Local), select Connect to another computer...enter the machine name, click OK.

3. Expand Services and Applications, expand Services. 

4. Find SQL Server Reporting Services and double click it.

5. Set startup type: Manual.

6. Service status: Stopped. If it's not Stopped, click the Stop button to stop it. 

7. Click OK to apply the changes.

 

StopSSRS.png

 

8. Find the Power BI Report Server service. You can choose to restart it at this point to start fresh. But at this point you've officually fully cutover hosting from SQL Server Reporting Services to hosting Power BI Report Server. The Power BI Report Server service should appear like this.

 

PBIRS.png

Helpful resources

Announcements
April AMA free

Microsoft Fabric AMA Livestream

Join us Tuesday, April 09, 9:00 – 10:00 AM PST for a live, expert-led Q&A session on all things Microsoft Fabric!

March Fabric Community Update

Fabric Community Update - March 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors