Recent releases throw an error when identity impersonate is set to "false"

[db2022]

Keep getting this server error while testing the latest PBIRS releases with Forms authentication. Narrowed it down to simply changing the web.config identity impersonate from "true" to "false" (leaving everything else to default configuration).

Change in Web.config:

    <authentication mode="Windows" />
    <identity impersonate="false" />

Report Server Error

An internal error occurred on the report server. See the error log for more details.
The type initializer for 'Microsoft.Data.SqlClient.InOutOfProcHelper' threw an exception.

• Could not load file or assembly 'System.Runtime.InteropServices.RuntimeInformation, Version=4.0.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. An API call exited abnormally. (Exception from HRESULT: 0x800300FA (STG_E_ABNORMALAPIEXIT))
• Could not load file or assembly 'System.Runtime.InteropServices.RuntimeInformation, Version=4.0.1.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. An API call exited abnormally. (Exception from HRESULT: 0x800300FA (STG_E_ABNORMALAPIEXIT))

library!ReportServer_0-1!808!03/18/2025-12:35:21:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: , Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details. ---> System.TypeInitializationException: The type initializer for 'Microsoft.Data.SqlClient.InOutOfProcHelper' threw an exception. ---> System.IO.FileLoadException: Could not load file or assembly 'System.Runtime.InteropServices.RuntimeInformation, Version=4.0.1.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. An API call exited abnormally. (Exception from HRESULT: 0x800300FA (STG_E_ABNORMALAPIEXIT)) ---> System.IO.FileLoadException: Could not load file or assembly 'System.Runtime.InteropServices.RuntimeInformation, Version=4.0.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. An API call exited abnormally. (Exception from HRESULT: 0x800300FA (STG_E_ABNORMALAPIEXIT))
   --- End of inner exception stack trace ---
   at Microsoft.Data.SqlClient.InOutOfProcHelper..ctor()
   at Microsoft.Data.SqlClient.InOutOfProcHelper..cctor()
   --- End of inner exception stack trace ---
   at Microsoft.Data.SqlClient.SqlConnectionString..ctor(String connectionString)
   at Microsoft.Data.SqlClient.SqlConnectionFactory.CreateConnectionOptions(String connectionString, DbConnectionOptions previous)
   at Microsoft.Data.ProviderBase.DbConnectionFactory.GetConnectionPoolGroup(DbConnectionPoolKey key, DbConnectionPoolGroupOptions poolOptions, DbConnectionOptions& userConnectionOptions)
   at Microsoft.Data.SqlClient.SqlConnection.ConnectionString_Set(DbConnectionPoolKey key)
   at Microsoft.Data.SqlClient.SqlConnection.set_ConnectionString(String value)
   at Microsoft.Data.SqlClient.SqlConnection..ctor(String connectionString, SqlCredential credential)
   at Microsoft.ReportingServices.Library.ConnectionManager.OpenConnection()
   at Microsoft.ReportingServices.Library.Global.get_ConfigurationFromCatalog()
   at Microsoft.ReportingServices.WebServer.Global.get_HeaderRules()
   at Microsoft.ReportingServices.WebServer.Global.SetCustomHeadersIfNeeded()
   at Microsoft.ReportingServices.WebServer.Global.DispatchRequest()
   at Microsoft.ReportingServices.WebServer.Global.Application_AuthenticateRequest(Object sender, EventArgs e)
   --- End of inner exception stack trace ---;

[v-nmadadi-msft]

Hi @db2022 

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[db2022 · Accepted solution]

The issue seems to be that if the windows account is given to the report server to connect to the report server database then that windows account needs to have admin access to the PBIRS programs folder on the report server (C:\Program Files\Microsoft Power BI Report Server\PBIRS)

Don't know why that is required in the new releases, I haven't seen any mention of it in release notes. It's not an issue if SQL account is used or if using default authentication configuration.

[v-nmadadi-msft]

Hi @db2022 ,

Could you please confirm if the issue has been resolved after raising a support case? If a solution has been found, it would be greatly appreciated if you could share your insights with the community. This would be helpful for other members who may encounter similar issues.

Thank you for your understanding and assistance.

[db2022]

Really stumped on this one hoping someone can shed some light..

I reinstalled the old version from May 2023 and verified it has no issue with changing just the web.config identity impersonate from "true" to "false".

Why do the new releases (Sept 2024, Jan 2025) throw this error? Have the requirements changed? Could it be specific to my server (Edition Windows Server 2022 Datacenter, Version 21H2, OS build 20348.3328)

Thanks

[Anonymous]

Hi,@db2022 .I am glad to help you.
Based on your error message, the problem seems to be due to a version conflict that
Make sure you have the correct version installed on your system. The versions mentioned in the error message are 4.0.1.0 and 4.0.2.0. You can try updating or reinstalling these assemblies.
Or you can try creating a support ticket for more help!
URL:

Microsoft Fabric Support and Status | Microsoft Fabric


I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.
Best Regards,
Carson Jian

[db2022]

Thanks for the tips. I'm not sure how to change the assemblies. My understanding is that the only requirement for PBIRS is the .NET 4.8. 
The VM server has .NET Framework 4.8 installed (version 4.8.04161 release 528449).
The installer for PBIRS Jan. 2025 installs the dll in C:\Program Files\Microsoft Power BI Report Server\PBIRS\ReportServer\bin.