Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
8 years ago

Power BI Report Server Issues with HA and NLB

Hello everyone,   I’ve installed Power BI Reporting Services as a scaled out deployment on two servers with the SSRS DB on a HA Always On Cluster. I’ve used a SSL Certificate for a virtual host nam...
ha
Need Help
pbx's avatar
pbx
Icon for Helper V rankHelper V
8 years ago

You can manage URL reservations using netsh http commands, for example: netsh http show urlacl shows you all reservations. See the following;

 

https://msdn.microsoft.com/en-us/library/windows/desktop/cc307236(v=vs.85).aspx

https://docs.microsoft.com/en-us/sql/reporting-services/install-windows/about-url-reservations-and-registration-ssrs-configuration-manager

 

For the second error, check to make sure both nodes have access to the SQL server on ther aforementioned port, and also check service account permissions, and local firewall logs (if you are using Windows firewall). I have to admit the error is a bit weird. What log file this error shows up in?

 

 

 

Anonymous's avatar
Anonymous
Not applicable
8 years ago

Thanks for your reply.

I’ve checked via urlacl the registrations. I’ve found 3 registrations which pointed on a wrong url. The other one seems to be correct. I deleted the three wrong registrations. But must be the registrations for the ssrs services pointed to the service account? Currently the registrations are made for a local service account …

    Reserved URL            : https://powerbi.<domain>.org:443/ReportServer/

        User: NT SERVICE\PowerBIReportServer

            Listen: Yes

            Delegate: No

            SDDL: D:(A;;GX;;;S-1-5-80-1730998386-2757299892-37364343-1607169425-3512908663)

 

Second Error:

Both Server runs under the same service account. If I stop one of the server, I can use the Portal. So I don’t think that the firewall or something else blocks the request.

The Logfile stored under:

"<DRIVE>:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles\RSPowerBI_<DATETIME>.log"

  • pbx's avatar
    pbx
    Icon for Helper V rankHelper V
    8 years ago

    NT SERVICE\PowerBIReportServer is an internal group that should contain your domain service account, so you should be good there. I think the idea is that if you switch the service account, the URL reservations do not need to change.

     

    Let's put the database error aside for now. Based on what you are saying that stopping one server works, there must be some misconfiguration. Let's see if we can find that.

     

    First thing would be to provide your URL reservations in the rsreportserver.config file. You don't need to provide the actual urls, but mask them in a way that are consistent.

    Second, when you restart the PBIRS service, a few log files are generated. Could you look into those and provide the following info?

     

    1. In the RSPowerBI_YYYY_MM_DD_HH_MI_SS.log, there is one or more lines like this: “|INFO|1|CFG : Hosting-url-ReportServerWebApp = [a url here] (env)”. Can you provide the url?
    2. In the RSPortal_YYYY_MM_DD_HH_MI_SS.log, the is one or more lines like this: “INFO: Web app url: some url binding here”.  What does that look like?
    3. In the ReportingServicesService_YYYY_MM_DD_HH_MI_SS.log, there are three lines like below:
      • INFO: Using report server internal url  <a url here>.
      • INFO: Using report server external url <a url here>.
      • INFO: Using url root <a url here>.

    By the way, how confident are you in performance of the Windows NLB? How do you know if that is not acting up?

     

     

  • pbx's avatar
    pbx
    Icon for Helper V rankHelper V
    8 years ago

    Since my response yesterday disappeared in the thin air, I am posting again.

     

    As for NT SERVICE\PowerBIReportServer, this is an internal group that should contain your service account, I beleive the setup process adds that account to this group. The idea might be that you don't need to change URL reservation if you change the service account. You can check memebership of this group on your Windows server to be sure.

     

    For the second error, let's put the database issue aside for now. Given that it works if you stop one server, I suspect it is an issue with your configuration or your Windows NLB. How confident are you in the performance of the Windows NLB? That service is not that smart and some people experience weird issues with it. Have you checked the NLB logs?

     

    As for the configuration, few things would help troubleshooting the issue. Could you please provide the following (you dont need to provide actual values for URLs, consistently masked ones should be fine)?

     

    1. URL reservations ins rsrepotserver.config file
    2. SecureConnectionLevel setting in the above file.
    3. Value of the following after you restart the PBIRS service:
      1. In the RSPowerBI_YYYY_MM_DD_HH_MI_SS.log, there is one or more lines like this: “|INFO|1|CFG : Hosting-url-ReportServerWebApp = [a url here] (env)”.
      2. In the RSPortal_YYYY_MM_DD_HH_MI_SS.log, there is one or more lines like this: “INFO: Web app url: url binding”.
      3. In the ReportingServicesService_YYYY_MM_DD_HH_MI_SS.log, there are three lines like this:
        1. INFO: Using report server internal url <a url here>.
        2. INFO: Using report server external url <a url here>.
        3. INFO: Using url root <a url here>.
    • Anonymous's avatar
      Anonymous
      Not applicable
      8 years ago

      Yes, there was a night with many alcohol 😊

      After the removal of the three url registrations, I haven’t found the first error.

      I already contact the NLB admin (external)  to check the logs, but I haven’t now a response.   

      Do you have any best practices for the BLB or necessary configurations/settings?

       

      1. URL reservations ins rsrepotserver.config file
        1. <UrlString>https://powerbi.<domain>.org:443</UrlString>
      2. SecureConnectionLevel setting in the above file.
        1. <Add Key="SecureConnectionLevel" Value="0"/>
      3. Value of the following after you restart the PBIRS service:
        1. In the RSPowerBI_YYYY_MM_DD_HH_MI_SS.log, there is one or more lines like this: “|INFO|1|CFG : Hosting-url-ReportServerWebApp = [a url here] (env)”.
          1. I’ve got 3 files after restarting the service,
            2018-01-02 23:14:51.9064|INFO|1|CFG : Hosting-url-ReportServerWebApp = [https://powerbi.<domain>.org/Reports] (env)
            2018-01-02 23:14:51.9689|INFO|1|CFG : Hosting-url-ReportServerWebApp = [https://powerbi.<domain>.org/Reports] (env)

      The values in the three files are the same. There are no errors.

        1. In the RSPortal_YYYY_MM_DD_HH_MI_SS.log, there is one or more lines like this: “INFO: Web app url: url binding”.

      Here I got 4 files after the restart
      RSPortal!reportserverwebapp!RSPortal.exe!1!01/02/2018-23:14:53:: i INFO: Web app url: https://powerbi.<domain>.org:443/Reports/

      The values in the four files are the same. There are no errors.

       

        1. In the ReportingServicesService_YYYY_MM_DD_HH_MI_SS.log, there are three lines like this:

          Here I got 3 files with after the restart.
          1. INFO: Using report server internal url <a url here>.
          2. INFO: Using report server external url <a url here>.
          3. INFO: Using url root <a url here>.

      configmanager!DefaultDomain!b6c!01/02/2018-23:14:52:: i INFO: Using report server internal url https://powerbi.<domain>.org:443/ReportServer.

      configmanager!DefaultDomain!b6c!01/02/2018-23:14:52:: i INFO: Using report server external url https://powerbi.<domain>.org:443/ReportServer.

      configmanager!DefaultDomain!b6c!01/02/2018-23:14:52:: i INFO: Using url root https://powerbi.<domain>.org/ReportServer.

       

       

      The URL’s seems to be correct. But I’m confused about the count of the logfles. The two errors from the second posting doesn’t appear anymore. But the issue to deploy a report on the server already exists.

       

      I checked again the Windows Event Log – Application Section. There I got everytime after a restart following error – 3 Events, corresponding with the amount of logfiles:

      The description for Event ID 25 from source MSOLAP$PBIRS cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

       

      If the event originated on another computer, the display information had to be saved with the event.

       

      The following information was included with the event:

       

      msmdsrvi.rll

      1031

       

      Source: MSOLAP$PBIRS

      Event Id: 25

      Level: Error

       

      I don’t think that a reinstall fixe this error. The report server was already reinstalled after a Kerberos issue and this error was at this time in the log too. I’ve not noticed that the error is logged since the reinstall (4 weeks) every time by a restart or start from the servers (the error is logged on both server.

       

       

      I clicked a little bit in the portal on some reports ad folders. I want open the context menu of a report, I’ve got following error (RsPortal…log) . next try it works (the user reported this issue 4 or 5 times …) – the error seems to be a connection problem with the sqlserver:

      RSPortal!reportserverwebapp!RSPortal.exe!3!01/02/2018-23:41:51:: e ERROR: OData exception occurred: Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException: Fehler in der Berichtsserver-Datenbank. Dies kann auf einen Verbindungsfehler, ein Timeout oder wenig Speicherplatz innerhalb der Datenbank zurückzuführen sein. ---> System.Data.SqlClient.SqlException: Invalid object name 'ExtendedCatalog'.

         at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)

         at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)

         at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)

         at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()

         at System.Data.SqlClient.SqlDataReader.get_MetaData()

         at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption)

         at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, Boolean inRetry, SqlDataReader ds, Boolean describeParameterEncryptionRequest)

         at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)

         at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)

         at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)

         at System.Data.SqlClient.SqlCommand.ExecuteReader()

         at Microsoft.ReportingServices.Library.InstrumentedSqlCommand.ExecuteReader()

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

         at Microsoft.ReportingServices.Library.Storage.WrapAndThrowKnownExceptionTypes(Exception e)

         at Microsoft.ReportingServices.Library.InstrumentedSqlCommand.ExecuteReader()

         at Microsoft.ReportingServices.Library.DBInterface.CatalogObjectExists(CatalogItemPath objectName, ItemType& type, Guid& id, Int32& snapshotLimit, Byte[]& secDesc, Int32& execOptions, Guid& snapshotId, Guid& linkID)

         at Microsoft.ReportingServices.Library.DBInterface.ObjectExists(ExternalItemPath objectName, ItemType& type, Guid& id, Int32& snapshotLimit, Byte[]& secDesc, Int32& execOptions, Guid& snapshotId, Guid& linkID)

         at Microsoft.ReportingServices.Library.DBInterface.ObjectExists(ExternalItemPath objectName, ItemType& type)

         at Microsoft.ReportingServices.Portal.Repositories.CatalogItemRepository.ThrowIfRestrictedItemType(RSService rsService, String path)

         at Microsoft.ReportingServices.Portal.Rep. | RequestID = s_f3559e81-6afe-4ea4-ae88-18e096d83eb2

      • jtarquino's avatar
        jtarquino
        Icon for Microsoft Employee rankMicrosoft Employee
        8 years ago

        From your latest logs you are still having issues connecting to the database

        System.Data.SqlClient.SqlException: Invalid object name 'ExtendedCatalog'.

         

        Please double check that you are using network service account or a domain account  (can you share this line from your logs)

        RSPortal!crypto!1!04/27/2017-11:27:31:: i INFO: Initializing crypto as user: NT AUTHORITY\NETWORK SERVICE

         

         

        Also go to your SQL Server and ensure both of the machine accounts  (for network service will look like yourdomain\YourMachine$) are in the logins and that both have enough permission 

         

  • jtarquino's avatar
    jtarquino
    Icon for Microsoft Employee rankMicrosoft Employee
    8 years ago

    Seems to be you are running the service under your virtual service account (NT SERVICE\PowerBIReportServer), double check you use Network service account (it will show up in the logs as NT AUTHORITY\NETWORK SERVICE) or a service account and check that one have permissions in your SQL database, to be sure you can share the logs of the portal.

     

    For example a Virtual Service account will look like

    RSPortal!crypto!RSPortal.exe!1!01/02/2018-14:27:01:: i INFO: Initializing crypto as user: NT SERVICE\PowerBIReportServer

     

    A network service will look like

    RSPortal!crypto!1!04/27/2017-11:27:31:: i INFO: Initializing crypto as user: NT AUTHORITY\NETWORK SERVICE