Forum Discussion
Power BI Report Server Issues with HA and NLB
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
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.
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.
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 😉
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?!
I guess that means if you want to change it, change it there.
I only get to Event ID 25 errors in the event log. I have two servers in the scale-out, maybe that's why.
Î have two server, too. But three errors ...
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?
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.
I've tried it, but this have no impact.
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?
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. ;
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
This is planned for Monday.
Gut the powerbi Feature for paginated Feature isnt configured.
