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 :)
- Anonymous8 years agoNot applicable
Thanks for reply.
This is from the log:
RSPortal!crypto!RSPortal.exe!1!01/03/2018-16:25:34:: i INFO: Initializing crypto as user: <domain>\<domainuser>
From the rsreportserver.config:
<AccountName>NT SERVICE\PowerBIReportServer</AccountName>The user above is on both server member of the local administrators group. The user have also on the Report Server database the permissions which granted via the “RsExecRole” role.
Thanks again!! Do you know why the error in the event log shows up three times and why I got more than one logfile after a restart? I don’t get the error on the event log at standalone installations. I got only the error on the installation with horizontal scaling. On which installation kind do you get these error?
From the web link:
“Manual actions or custom automation scripts need to be used to complete the failover and recovery.”
Does it mean that the report server instances should be restarted? So should I better remove the databases from the HA group?
- pbx8 years ago
Helper V
I get the Event ID 25 error at least on scale-out, will check standalone. The cause of the error is locale resources. For your case is looking for German (1031) language resources. Is it possible that you have installed a German version of PBI, but no German language on the Windows? - jtarquino8 years ago
Microsoft Employee
You might have to start to investigate why the PBIRS Server isn't able to connect consistently with the database useing the <domain>\<domainuser> user, you can use a combination of the following
SQL Profiler in the database server to ensure is connecting with the right user and the connection is coming from both of your scale out servers.
Also the SQL login failed traces to see if is failing in the security handshake.
If nothing is showing up in the SQL logs you might have to investigate the connectivity fromo the PBIRS server to the database.
Regards
-Jaime
- Anonymous8 years agoNot applicable
It is possible that the initial setup was the German. But after the reinstall I absolutely sure that I used the English setup binary. But I can imagine that the uninstall does not remove all resources, Do you have some recommendations in the case of the HA group? Should I remove the database from the group or should I implement into the run book in case of a move of the database that the report server instances restarted?
Do you really think there is a problem with the user? The most time the server works correctly and everything works fine. Sometimes I can’t deploy a report on the server via Power BI Desktop and sometimes I get curios errors (can’t connect to the database …)
So, I can’t imagine that the report server will hae problems with the user account. It is also very difficult to use the profiler because the database server hosting several production databases and the error is not always reproducible. At least the profiler cost to much performance for the other databases.
But I tell the database team to check the ErrorLog and to monitor the firewall and the connectivity.
- pbx8 years ago
Helper V
Anonymous
So I checked. I only get error on scale-out. It's weird, becuase it's looking for particular locale (which is not a suprising locale, it's actually where we are located physically), but both Windows region and PBIRS are US-EN, so I have no idea where it's getting the idea about the locale.
Regarding database: I recommend you remove the RS databases from the AG and give it a try, at least you have removed one possible point of failure.
Regarding the log files:
The following are expected:
- ReportingServicesService_YYYY...
- RSPortal_YYYY...
- RSHostingServiceYYYY
- RSOffice_YYYY or RSOfficeYYYY
- ReportingServicesWMI_YYYY
- RSPowerBI_YYYY
- and finally RSPowerBIYYYY_
The RSPowerBIYYYY is generated every hour, and the #6 is generated when service starts and once in a while. I think there is a bug somewhere in configuration and two different file name convention is used for logging PowerBI events, one has _ before YYYY, one doesn't. I'm sure if we look at configuration files, we can spot that.
- Anonymous8 years agoNot applicable
I will try it to remove the database from the HA Goup. Did you also get 3 Errors in the EventLog or only one? Hopefully see this error a guy from Microsoft and fixed it in the next release 😉
- Anonymous8 years agoNot applicable
One question more to the HA Group scenario.
On this website (https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/reporting-services-with-always-on-availability-groups-sql-server#bkmk_reportserverdatabases) I read this:
Update the database connection to use the Lister DNS Name. for native mode report servers, change the Report Server Database Name in Reporting Services configuration manager.
Why should I change the database name? The name on each node is the same?!
- pbx8 years ago
Helper V
I guess that means if you want to change it, change it there.
- pbx8 years ago
Helper V
I only get to Event ID 25 errors in the event log. I have two servers in the scale-out, maybe that's why.
- Anonymous8 years agoNot applicable
Î have two server, too. But three errors ...
- Anonymous8 years agoNot applicable
Now I removed the reoport server database from the ha group. The server runs stable and the logs are fine.
But if I pubish a report via the dektop, it gaves me 4 of 5 times a a error with no description. The Error is only on client side.
If I shutdown one report server, everything seems to be working. So I think there is a error or misconfiguration with the NLB.
The publishing via the upload feature from the webinterface works everytime.
Does anyone give me some hints what the IT can check? Or are there any best practice?
- pbx8 years ago
Helper V
You may want to add an entry in the host file of each server that points the virual host name to the IP of that server.
- Anonymous8 years agoNot applicable
I've tried it, but this have no impact.
- pbx8 years ago
Helper V
Would it be possible to turn on diagnositc logging on the client to see if you get any indication of the possible error there? Are you sure there's aboslutly no clue in the server logs about the error? Can you check if your upload sessiosn jumps across servers?
- Anonymous8 years agoNot applicable
Hm.. today i found following error in the logs:
ReportingServicesService.log
library!DefaultDomain!1040!01/12/2018-12:55:42:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: Invalid PBI Configuration, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. ;
- jtarquino8 years ago
Microsoft Employee
That error is unrelated to the PowerBI Reports feature, the configuration mentioned there is for sending a paginated report visual to the PowerBI.com , more details here https://docs.microsoft.com/en-us/sql/reporting-services/install-windows/power-bi-report-server-integration-configuration-manager.
For your problem publishing from the desktop I would recommend to use a network trace fromo the client to validate the errors you are getting from the server when the NLB is enabled
- Anonymous8 years agoNot applicable
This is planned for Monday.
Gut the powerbi Feature for paginated Feature isnt configured.