Forum Discussion
Power BI Report Server Issues with HA and NLB
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?
- URL reservations ins rsrepotserver.config file
- <UrlString>https://powerbi.<domain>.org:443</UrlString>
- SecureConnectionLevel setting in the above file.
- <Add Key="SecureConnectionLevel" Value="0"/>
- Value of the following after you restart the PBIRS service:
- 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)”.
- 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.
- 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.
- 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. - 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>.
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
You can ignore the "Event ID 25 from source MSOLAP$PBIRS" errors. I get them as well, has something to do with the local SSAS instance of PBIRS and I wouldn't worry about it.
At this point your issue seems to be database issue. Given you are using Always On AG, you may want to make sure your database and connectivty to that is good from both nodes. Please see the "Report Server Databases and Availability Groups" section in the following link:
Having said that, even after this you will run into issues with the current configuration. But I will save it for later, when you past this database issue :)