https

19 Topics

HTTPS ERROR POWER BI REPORT SERVER
Colegas alquien que me pueda ayudar, Recientemente reinstale un servidor PBIRS por que la base de datos se contraba corrupta, segui los pasos en el foro para dicha reinstalacion, ahora veo que el sitio con el puerto 80 funciona, puedo organizar mis carpeta, asignar usuarios, ver informes BI, etc. Sin embargo al usar el puerto 443, puedo realizar todo ello excepto visualizar informes BI. Antes no me pasaba eso, sin embargo el servidor anterior yo no lo configure. Revise mi configuracion en report server configuration manager y al parecer todo esta bien. ¿es necesario realizar mas configuraciones en los archivos .config? esta parte aun lo lo revise. Mi version de septiembre 2025
Solved
vladimir74
7 months ago Place Report Server
Views
0likes
Comments
DNS name result: 404 - File or directory not found.
Hello everyone, I am using windows server and I have report server configuration manager and I can access the power bi dashboard using https with the hostname: https://hostname/reports and it is working fine. the issue is I linked my hostname with DNS as Cname within my company network, when I try to access https://myDNSname.com/reports I got below error: 404 - File or directory not found. The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable. the DNS name is correct but I don't know what is the issue. I kindly seek your support thank you, Regards, __PRESENT __PRESENT
Solved
MohammedNasser
1 year ago Place Report Server
Views
0likes
Comments
Problem with HTTPS on Power bi Report Server
Hi. I'm facing the following problem. Can someone help me to solve this? I configured the power bi report server to work with HTTPS (443 port) keeping the HTTP working too. When I access the URL like this http://urltopowerbireportingservices (HTTP:80), automatically is redirected correctly to https://urltopowerbireportingservices/Reports (HTTPS:443). However, if a access the URL like https://urltopowerbireportingservices (without /Reports), an error 404 occurred (see image 1). URL https://urltopowerbireportingservices/Reports (with /Reports) works perfectly. Image 1 - Error 404 when I access https://urltopowerbireportingservices The problem is that the URL https://urltopowerbireportingservices is not redirecting to https://urltopowerbireportingservices/Reports. How can I configure to make this work? Web Service URL configuration Web Portal URL configuration. The rsreportserver.config file is configured like this: IIS on server is disabled. Thanks.
jpgandrade90
2 years ago Place Report Server
Views
0likes
Comment
Unable to save report to PowerBI Report Server after enabling HTTPS / TLS
Hi All, After configuring my PowerBI Report Server to use a TLS Certificate I am unable to save save reports from PowerBI Desktop to the PowerBI Server. I have tried nemerous fixes from threads on this forum, but the error persists. Please see ItemNotFoundException towards the end of the "PowerBI Report Server Error" section below. PowerBI Desktop Error: Saving to PowerBI Report Server An error occured while attempting to save the report to PowerBI Report Server. PowerBI Report Server Error: 2023-08-11 07:37:37.7626|INFO|1|File Logger created: D:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles\RSPortal_2023_08_11_07_37_37.log - level Info, will roll at 32 Mb, process id 6376 2023-08-11 07:37:37.7776|INFO|1|Provider name 2023-08-11 07:37:37.7776|INFO|1|Container name Microsoft SQL Server Reporting Services Key Container 2010 2023-08-11 07:37:37.7776|INFO|1|Setting Symmetric Key 2023-08-11 07:37:37.7938|INFO|1|Setting up Hosted Process State 2023-08-11 07:37:38.0123|INFO|1|library|SQLDump flags: ReferencedMemory, AllThreads, SendToWatson 2023-08-11 07:37:38.0123|INFO|1|library|MiniDump flags: DataSegs, UnloadedModules, ProcessThreadData 2023-08-11 07:37:38.0123|INFO|1|library|Dump on: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogExceptionMicrosoft.ReportingServices.Modeling.InternalModelingExceptionMicrosoft.ReportingServices.ReportProcessing.UnhandledReportRenderingException 2023-08-11 07:37:38.0123|INFO|1|library|Do not dump on: Microsoft.PowerBI.ReportServer.WebApi.Catalog.CatalogAccessExceptionSystem.Threading.ThreadAbortExceptionSystem.Web.UI.ViewStateExceptionSystem.OutOfMemoryExceptionSystem.Web.HttpExceptionSystem.IO.IOExceptionSystem.IO.FileLoadExceptionMicrosoft.SharePoint.SPExceptionMicrosoft.ReportingServices.WmiProvider.WMIProviderExceptionSystem.AppDomainUnloadedException 2023-08-11 07:37:38.0123|INFO|1|library|Minidump location: C:\Users\PBIRS_SVC\AppData\Local\Temp\ 2023-08-11 07:37:38.0123|INFO|1|Starting ReportServerWebApp 2023-08-11 07:37:38.0279|INFO|1|library|Catalog max connection pool size: 768 2023-08-11 07:37:38.0592|INFO|1|Working directory : D:\Program Files\Microsoft Power BI Report Server\PBIRS\Portal 2023-08-11 07:37:38.0592|INFO|1|Report Server url: https://powerbirs.domain.com/ReportServer 2023-08-11 07:37:38.0592|INFO|1|Report Server Web App virtual root: /Reports 2023-08-11 07:37:38.0592|INFO|1|Web app url: https://powerbirs.domain.com:443/Reports/ 2023-08-11 07:37:38.0592|INFO|1|Authentication scheme(s): IntegratedWindowsAuthentication 2023-08-11 07:37:38.1061|INFO|1|Catalog max connection pool size: 100 2023-08-11 07:37:39.1530|INFO|1|SecureConnectionLevel: 3. Redirecting HTTP connections to HTTPS. 2023-08-11 07:37:39.1842|INFO|1|crypto|Initializing crypto as user: DOMAIN\PBIRS_SVC 2023-08-11 07:37:39.1842|INFO|1|crypto|Exporting public key 2023-08-11 07:37:39.1998|INFO|1|crypto|Importing existing encryption key 2023-08-11 07:37:42.2780|INFO|4|<Header> <Product>Microsoft Power BI Report Server 1.17.8552.27722 (15.0.1112.48)</Product> <Locale>English (United States)</Locale> <TimeZone>UTC--7</TimeZone> <Path>D:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles\RSPortal_2023_08_11_07_37_37.log</Path> <SystemName>SERVER-NAME</SystemName> <OSName>Microsoft Windows Server 2022 Standard Evaluation</OSName> <OSVersion>10.0.20348</OSVersion> <ProcessID>6376</ProcessID> <Virtualization>True</Virtualization> </Header> <ProcessorArchitecture>AMD64</ProcessorArchitecture> <ApplicationArchitecture>AMD64</ApplicationArchitecture> 2023-08-11 07:37:54.3873|INFO|7|Received request GET /api/v2.0/ServiceState| RequestID = s_94cef32e-9202-4680-8b64-a7b83ab3dac7 2023-08-11 07:37:54.6685|INFO|7|Sending response. Response code DOMAIN\User 200, Elapsed time 0:00:00.2801696| RequestID = s_94cef32e-9202-4680-8b64-a7b83ab3dac7 2023-08-11 07:37:54.8560|INFO|7|Received request GET /api/v2.0/CatalogItems(Path='/')| RequestID = s_4fd49dd9-9f8f-4890-a924-15e2c3b2bb27 2023-08-11 07:37:54.9498|INFO|7|Sending response. Response code DOMAIN\User 200, Elapsed time 0:00:00.0996048| RequestID = s_4fd49dd9-9f8f-4890-a924-15e2c3b2bb27 2023-08-11 07:37:54.9658|INFO|7|Received request GET /api/v2.0/catalogitems(e9dc2b00-9e76-4468-ab07-f057a3c589dc)/Model.Folder/catalogitems/| RequestID = s_65b472da-ee59-4477-8fb4-de5e00f67bd4 2023-08-11 07:37:55.0436|INFO|7|Sending response. Response code DOMAIN\User 200, Elapsed time 0:00:00.0817706| RequestID = s_65b472da-ee59-4477-8fb4-de5e00f67bd4 2023-08-11 07:37:56.6373|INFO|7|Received request GET /api/v2.0/CatalogItems(Path='/EDW')| RequestID = s_80135d36-17ab-40e2-b70f-8c5e372c6537 2023-08-11 07:37:56.6529|INFO|7|Sending response. Response code DOMAIN\User 200, Elapsed time 0:00:00.0127266| RequestID = s_80135d36-17ab-40e2-b70f-8c5e372c6537 2023-08-11 07:37:56.6529|INFO|17|Received request GET /api/v2.0/catalogitems(2ba032b9-e3f4-4fe6-871d-ceff0af2b983)/Model.Folder/catalogitems/| RequestID = s_e3ec502c-526f-40e6-bab7-733843633eab 2023-08-11 07:37:56.6529|INFO|17|Sending response. Response code DOMAIN\User 200, Elapsed time 0:00:00.0070938| RequestID = s_e3ec502c-526f-40e6-bab7-733843633eab 2023-08-11 07:38:02.5123|INFO|7|Received request GET /api/v2.0/CatalogItems(Path='/EDW/New_Report')| RequestID = s_b003b38d-5607-4d84-8661-6a422ee50bad 2023-08-11 07:38:02.5280|ERROR|7|library|Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: , Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: The item '/EDW/New_Report' cannot be found.;| RequestID = s_b003b38d-5607-4d84-8661-6a422ee50bad 2023-08-11 07:38:02.5435|INFO|7|Sending response. Response code DOMAIN\User 404, Elapsed time 0:00:00.0192931| RequestID = s_b003b38d-5607-4d84-8661-6a422ee50bad 2023-08-11 07:38:03.1374|INFO|17|Received request GET /api/v2.0/System/Properties| RequestID = s_a839f6f6-68a9-4fee-ae70-903a96e6da91 2023-08-11 07:38:03.1685|INFO|17|Sending response. Response code DOMAIN\User 200, Elapsed time 0:00:00.022886| RequestID = s_a839f6f6-68a9-4fee-ae70-903a96e6da91 2023-08-11 07:38:03.2779|INFO|17|Received request GET /api/v2.0/me| RequestID = s_55924c0b-902a-4c97-a43a-9e6a3f9818ec 2023-08-11 07:38:03.2935|INFO|17|Catalog max connection pool size: 100| RequestID = s_55924c0b-902a-4c97-a43a-9e6a3f9818ec 2023-08-11 07:38:03.2935|INFO|17|Creating default Global MeterCollector| RequestID = s_55924c0b-902a-4c97-a43a-9e6a3f9818ec 2023-08-11 07:38:03.3560|INFO|17|Sending response. Response code DOMAIN\User 200, Elapsed time 0:00:00.0758321| RequestID = s_55924c0b-902a-4c97-a43a-9e6a3f9818ec 2023-08-11 07:38:03.3560|INFO|17|Received request POST /api/v2.0/powerbireports(Path='/EDW/New_Report')/Model.Upload| RequestID = s_cd1ccc82-2e3e-4ee8-bd9b-b9eb4907a6c0 2023-08-11 07:38:03.3717|ERROR|17|library|Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: , Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: The item '/EDW/New_Report' cannot be found.;| RequestID = s_cd1ccc82-2e3e-4ee8-bd9b-b9eb4907a6c0 2023-08-11 07:38:03.4810|ERROR|6|The remote server returned an error: (503) Server Unavailable.| RequestID = s_cd1ccc82-2e3e-4ee8-bd9b-b9eb4907a6c0 2023-08-11 07:38:03.4810|INFO|11|Sending response. Response code DOMAIN\User 422, Elapsed time 0:00:00.1222532| RequestID = s_cd1ccc82-2e3e-4ee8-bd9b-b9eb4907a6c0 Thank you Stephan
Stephan_Louw
3 years ago Place Report Server
Views
0likes
Comments
Unable to Login to Report Server with HTTPS & SSL
Hello everyone, I am currently running an on-premise Power BI Report Server and am trying to enable the https on the system. I'm having difficulties trying to login to the Portal. It is stuck at the login page like forever. It has no issue login into the report when it is just using http. (the login credential has no issue, I have checked it millions of time) I am currently using a wildcard public certificate from GlobalSign (which is working for all my other webservers). The cert is not expired. And I have made sure that the DNS is configured correctly to resolve the hostname of the report server, but still was unable to make it through the login page. When I log in, it keeps coming back to the login page. Does anyone face this scenario before? It would be really helpful if you can provide a step by step guide solution to this. Thanks Regards Mark Teh
markteh
3 years ago Place Report Server
Views
0likes
Comments
https configuration
hi i have Microsoft Power BI Report Server Version 15.0.1110.120 i want to config HTTPS and i set this configuration: and below configuration but ihave problem when i want to login to reportserver or server when i want to login with this below link i can not login and face agein login page: https://*********/ReportServer what should i do?
omid5ive
3 years ago Place Report Server
Views
0likes
Comment
Report server using only HTTPs
Hi, is there a way to configure report server using only https, as runing also http makes a violations for the healthcheck. Therefore it should be disabled, BUT as soon as I keep https only, neither http nor https works. Seems like it requires to have port 80 bound. I do have a bound TLS cerfiticate for HTTPs, and while http is configured both variants works fine.
Solved
JurajK
3 years ago Place Report Server
Views
0likes
Comment
Server Is Not Reachable over HTTPS
I'm currently getting a 'Server is not reachable' error when attempting to connect to Power BI Report Server via Power BI desktop over HTTPS or trying to Edit in Power BI desktop from the web portal. I'm on September 2022 right now, but I was also experiencing this issue on May 2022. I can upload via the web portal interface, but I would like to get this piece working from Power BI Desktop. What's strange to me is that I AM able to connect over HTTP with no issues. There are no blocks within the Firewall or other security programs. Anyone have any suggestions? I saw a few posts on here with similar issues but didn't seem to be much resolution.
Solved
acp206
3 years ago Place Report Server
Views
0likes
Comments
Save as via HTTPS: Server is not reachable
Hi all, in our organisation we have private cloud where we are hosting 2 Report Servers: RnD and Production. RnD is reachable via HTTP and Production is reachable via HTTPS. Each server has its own private network. For production server we have certificate installed and Kerberos is working. All users can access both server. PBIX reports work fine on the server Using "Upload" button from portal we can deploy PBIX files from our machines on both servers but only on HTTP (RnD server) we can use "Save As" option in Power BI Desktop (Version: 2.51.4885.1423 64-bit (October 2017)) to deploy reports. When we specify url for PRODUCTION server (HTTPS) we have "Server is not reachable" message. Does HTTPS Save As option works on specific PORT that we need to open in firewall on our private network? Or it is something else? Thanks in advance. Dejan
destank
4 years ago Place Report Server
Views
0likes
Comments
HTTPS PowerBI Report Server to HTTP SQL Server data source - error 401
I have just experienced a bizarre problem today. My PowerBI report server (on prem) was previously on a self cert SSL before. I have reports that runs on Imported mode from a remote SQL Server which doesnt accept encrypted connection. All within the same domain. I have upgraded the SSL to a SAN SSL the other day on the report server. All the data source connection remain the same (non SSL remote SQL Server). BTW I am running May 2021 report server. This morning one of the colleagues reported that the data wasnt refreshed. Upon checking I saw the schedule refresh failed. And I tried to add refresh schedule on another Import mode PBIX report. Got a big fat "Something went wrong". Data source have basic credentials and on the data source page test connection is successful with the basic SQL login credentials.But whenever I try to add a refresh schedule i get the same error. Went on checking log and verbose. Got "Error 401". Detail error, if anyone is interested: 2021-07-07 00:47:55.7026|ERROR|63|OData exception occurred: System.Net.WebException: The request failed with HTTP status 401: Unauthorized. at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Microsoft.SqlServer.ReportingServices2010.ReportingService2010.CreateCacheRefreshPlan(String ItemPath, String Description, String EventType, String MatchData, ParameterValue[] Parameters) at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.<>c__DisplayClass136_0.b__0() at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.SoapMethodWrapper1.ExecuteMethod(Boolean setConnectionProtocol) at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.CreateCacheRefreshPlan(String itemPath, String description, String eventType, String matchData, ParameterValue[] parameters) at Microsoft.ReportingServices.Portal.Services.SoapProxy.SoapRS2010Proxy.<>c__DisplayClass19_0.<CreateCacheRefreshPlan>b__0() at Microsoft.ReportingServices.Portal.Services.SoapProxy.SoapAuthenticationHelper.ExecuteWithWindowsAuth[TReturn](SoapHttpClientProtocol soapClient, IPrincipal userPrincipal, Func1 func) at Microsoft.ReportingServices.Portal.Repositories.SubscriptionService.CreateCacheRefreshPlan(IPrincipal userPrincipal, CacheRefreshPlan cacherefreshPlan) at Microsoft.ReportingServices.Portal.ODataWebApi.V2.Controllers.CacheRefreshPlansController.AddEntity(CacheRefreshPlan entity) at Microsoft.ReportingServices.Portal.ODataWebApi.Controllers.Reflection.EntitySetReflectionODataController1.Post(ODataPath oDataPath, T value) at lambda_method(Closure , Object , Object[] ) at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ActionExecutor.<>c__DisplayClass6_2.<GetExecutor>b__2(Object instance, Object[] methodParameters) at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ExecuteAsync(HttpControllerContext controllerContext, IDictionary2 arguments, CancellationToken cancellationToken) --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Controllers.ApiControllerActionInvoker.d__1.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Controllers.ActionFilterResult.d__5.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Controllers.ExceptionFilterResult.d__6.MoveNext().| RequestID = s_9b953a1c-bc48-41f3-ad5b-12e903990663 By now I may have read 95% of the forums/blogs/solutions/documentations without luck. So I thought, lets try to do it over HTTP (port 80) instead of HTTPS (port 443). And it worked like a charm. BTW, by default HTTP binding is removed, only HTTPS is allowed. I have checked "Encrypted connection is disabled" in the datasource settings in PowerBI desktop and refresh+redeployed. Same issue over HTTPS but works fine on HTTP. Does anyone have a permanent solution/fix to this problem? Because running report server on HTTP is not allowed. I have tried restarting both instances, changing reg values mentioned on the internet, nothing worked. Additionally we have kerberos enabled, and our windows authentication works perfeclty fine for remote SQL Server datasources. Thank you all for reading and using your brain space. Have a good night. Note: the forum removed some parts of the error message. It doesnt let me submit them.
Solved
saabbir
5 years ago Place Report Server
Views
0likes
Comments