Forum Discussion

jguerrero's avatar
jguerrero
Helper II
7 years ago

Jan 2019 Report server unreachable

I just updated the Power BI software in client & Server:

- Desktop (D) is now Version: 2.65.5313.1381 64-bit (December 2018)

- Desktop for Report Server (DRS) is now Version: 2.65.5313.1421 64-bit (January 2019)

- Power BI Report Server (PBIRS) software is also the JAN 2019

 

I am able to publish in PBIRS the newest PBIX files we have without any issues.

I open the files with (DRS) and SAVE AS - POWER BI REPORT server, select the folder, SAVE and that's it.

I am able to open & refresh the dashboard, navigate in the tabs, filtering, etc. No problem.

 

When I tried the oldest models (Desktop version was October 2018), I am not able to publish any of them.

They are over 100 MB, and even though I opened them with the new (D) version, refresh them, save them, opened with (DRS), when I tried to save them, the white screen disappear without any signal. Just ends and I am returned to (DRS).

If I tried to save it for second time, I receive errors in the credentials (Encryption that I do not use) or it says the server is unreachable. But I just saved a new PBIX in the same server minutes ago!

 

Any ideas what is happening?

Thanks in advance...

Report Server + PBI Premium
Upload

10 Replies

  • bradsy's avatar
    bradsy
    Microsoft Employee
    7 years ago

    If you have generic repro steps, we can take a look and see if we can reproduce.

    • Anonymous's avatar
      Anonymous
      Not applicable
      7 years ago

      So my PBI-SSRS Server has been wokring fine for months. There are no changes I know of in the last couple of days though in fairness our IT department could easily have screwed around with something networky or AD related and I would have no way of knowing.

       

      Now howevere I am getting the "Server is not reachable" error when saving reports from PBI Dsktop

       

      The scenario is.

      (Desktop client is 2.65.5313.1562, Server is 1.4.6969.7395 so both Jan 2019) 

      I can view reports via a web browser and they all seem to be working fine (no HTTPS configured all HTTP)

      I can access reports via the desktop tool and pull them down 

      I can upload reports to the server from my local mahcine via the web UI.

      I can access reports via the desktop locally on the server and pull them down

      I can save reports via the desktop locally on the server and this works as expected using localhost

      I can save reports via the desktop locally on the server and this works as expected using the servername

      When I try and save reports from my desktop using the servername or the IP number I get "Server is not reachable"

       

      I have scanned all the log files I can find in the PBI Server directory and come up with very little at this point. There's nothing in the SQL Server logs

       

      I am seeing the following in the RSPortal log which is telling me that the connection is being dropped but not really giving me any meaningful reasons why.

       

      What further steps can I take to figure this out?

       

      2019-05-14 10:02:56.5279|INFO|9|Received request GET /api/v2.0/ServiceState| RequestID = s_939d621b-bfd8-4d82-a338-92af7ff9a7b0 
2019-05-14 10:02:56.5279|INFO|9|Sending response. Response code MYDOMAIN\mylogin 200, Elapsed time 0:00:00.0051187| RequestID = s_939d621b-bfd8-4d82-a338-92af7ff9a7b0 
2019-05-14 10:02:57.1667|INFO|28|Received request GET /api/v2.0/CatalogItems%28Path%3D%27/%27%29| RequestID = s_f3fdfec0-9f37-4525-b30e-22edc711f8ae 
2019-05-14 10:02:57.1667|INFO|28|Sending response. Response code MYDOMAIN\mylogin 200, Elapsed time 0:00:00.0059367| RequestID = s_f3fdfec0-9f37-4525-b30e-22edc711f8ae 
2019-05-14 10:02:57.2760|INFO|28|Received request GET /api/v2.0/catalogitems%28add136b3-efae-42b9-baa7-82891eaf26ab%29/Model.Folder/catalogitems/| RequestID = s_102a0853-ce31-4d17-9aba-ded92e306dae 
2019-05-14 10:02:57.4323|INFO|36|Sending response. Response code MYDOMAIN\mylogin 200, Elapsed time 0:00:00.1449319| RequestID = s_102a0853-ce31-4d17-9aba-ded92e306dae 
2019-05-14 10:03:01.6286|INFO|28|Received request GET /api/v2.0/CatalogItems%28Path%3D%27/Training%20and%20Development%27%29| RequestID = s_fde07941-30e4-4ea5-a0f6-d749a3022770 
2019-05-14 10:03:01.6286|INFO|28|Sending response. Response code MYDOMAIN\mylogin 200, Elapsed time 0:00:00.0049712| RequestID = s_fde07941-30e4-4ea5-a0f6-d749a3022770 
2019-05-14 10:03:01.7536|INFO|28|Received request GET /api/v2.0/catalogitems%281afdaf8e-51f8-4b37-bce7-9c90c256df3d%29/Model.Folder/catalogitems/| RequestID = s_b2236363-57ca-43a4-ae3f-949894746458 
2019-05-14 10:03:01.9099|INFO|27|Sending response. Response code MYDOMAIN\mylogin 200, Elapsed time 0:00:00.1547973| RequestID = s_b2236363-57ca-43a4-ae3f-949894746458 
2019-05-14 10:03:04.1166|INFO|26|Received request GET /api/v2.0/CatalogItems%28Path%3D%27/Training%20and%20Development/Chart%20Types%20v2%27%29| RequestID = s_b3c817c7-f9a4-4fb4-8509-c59700cb85d9 
2019-05-14 10:03:04.1166|INFO|26|Sending response. Response code MYDOMAIN\mylogin 200, Elapsed time 0:00:00.005885| RequestID = s_b3c817c7-f9a4-4fb4-8509-c59700cb85d9 
2019-05-14 10:03:04.1948|INFO|28|Received request GET /api/v2.0/CatalogItems%28Path%3D%27/Training%20and%20Development/Chart%20Types%20v2%27%29/AllowedActions| RequestID = s_b40170b5-f5f0-4e17-8641-62ca6aa17fe8 
2019-05-14 10:03:04.2103|INFO|28|Sending response. Response code MYDOMAIN\mylogin 200, Elapsed time 0:00:00.007835| RequestID = s_b40170b5-f5f0-4e17-8641-62ca6aa17fe8 
2019-05-14 10:03:21.9616|INFO|37|Received request GET /api/v2.0/CatalogItems%28Path%3D%27/Training%20and%20Development/Chart%20Types%20v2%27%29| RequestID = s_fc7a92db-6918-419e-be0b-dea897116fce 
2019-05-14 10:03:21.9772|INFO|37|Sending response. Response code MYDOMAIN\mylogin 200, Elapsed time 0:00:00.0063262| RequestID = s_fc7a92db-6918-419e-be0b-dea897116fce 
2019-05-14 10:03:22.0709|INFO|38|Received request GET /api/v2.0/CatalogItems%284ba122b4-c49d-438e-af0e-971f17f5f648%29/Model.PowerBIReport/Content/%24value| RequestID = s_71e42d0f-6f51-49f7-a241-cbbda0510605 
2019-05-14 10:03:22.9143|INFO|27|Sending response. Response code MYDOMAIN\mylogin 200, Elapsed time 0:00:00.8443803| RequestID = s_71e42d0f-6f51-49f7-a241-cbbda0510605 
2019-05-14 10:03:42.5625|INFO|40|Received request GET /api/v2.0/ServiceState| RequestID = s_dbd7f110-15e2-4814-8c6b-71af6aa32a5a 
2019-05-14 10:03:42.5781|INFO|40|Sending response. Response code MYDOMAIN\mylogin 200, Elapsed time 0:00:00.0061422| RequestID = s_dbd7f110-15e2-4814-8c6b-71af6aa32a5a 
2019-05-14 10:03:43.2235|INFO|41|Received request GET /api/v2.0/CatalogItems%28Path%3D%27/%27%29| RequestID = s_a29c58a6-88c7-48cf-877e-4d8a5c0f9fff 
2019-05-14 10:03:43.2392|INFO|41|Sending response. Response code MYDOMAIN\mylogin 200, Elapsed time 0:00:00.0044065| RequestID = s_a29c58a6-88c7-48cf-877e-4d8a5c0f9fff 
2019-05-14 10:03:43.3329|INFO|41|Received request GET /api/v2.0/catalogitems%28add136b3-efae-42b9-baa7-82891eaf26ab%29/Model.Folder/catalogitems/| RequestID = s_4cfdcb20-525b-4a77-a1b0-f0a1e82cb5fb 
2019-05-14 10:03:43.4736|INFO|39|Sending response. Response code MYDOMAIN\mylogin 200, Elapsed time 0:00:00.1393143| RequestID = s_4cfdcb20-525b-4a77-a1b0-f0a1e82cb5fb 
2019-05-14 10:03:46.6469|INFO|38|Received request GET /api/v2.0/CatalogItems%28Path%3D%27/Training%20and%20Development%27%29| RequestID = s_5c8a3cd0-e97f-4340-9dd7-52e9438a60f1 
2019-05-14 10:03:46.6469|INFO|38|Sending response. Response code MYDOMAIN\mylogin 200, Elapsed time 0:00:00.0041421| RequestID = s_5c8a3cd0-e97f-4340-9dd7-52e9438a60f1 
2019-05-14 10:03:46.7251|INFO|38|Received request GET /api/v2.0/catalogitems%281afdaf8e-51f8-4b37-bce7-9c90c256df3d%29/Model.Folder/catalogitems/| RequestID = s_19cb468f-58b2-4f18-afb8-b5bcc8387b38 
2019-05-14 10:03:46.8657|INFO|17|Sending response. Response code MYDOMAIN\mylogin 200, Elapsed time 0:00:00.1459646| RequestID = s_19cb468f-58b2-4f18-afb8-b5bcc8387b38 
2019-05-14 10:03:52.6702|INFO|40|Received request GET /api/v2.0/CatalogItems%28Path%3D%27/Training%20and%20Development/Chart%20Types%20v2%20IPNO%27%29| RequestID = s_3a24f6c0-0554-4649-b780-c664edc8805c 
2019-05-14 10:03:52.6858|INFO|40|Sending response. Response code MYDOMAIN\mylogin 404, Elapsed time 0:00:00.0033024| RequestID = s_3a24f6c0-0554-4649-b780-c664edc8805c 
2019-05-14 10:03:54.1846|INFO|38|Received request GET /api/v2.0/System/Properties| RequestID = s_e5cdd5a8-4bc5-42bc-bc37-40389a4b803d 
2019-05-14 10:03:54.1846|INFO|38|Sending response. Response code MYDOMAIN\mylogin 200, Elapsed time 0:00:00.0030572| RequestID = s_e5cdd5a8-4bc5-42bc-bc37-40389a4b803d 
2019-05-14 10:03:54.6428|INFO|38|Received request GET /api/v2.0/me| RequestID = s_8594e1ef-9698-4dc5-b22a-f87e47b54441 
2019-05-14 10:03:54.6898|INFO|38|Sending response. Response code MYDOMAIN\mylogin 200, Elapsed time 0:00:00.0467899| RequestID = s_8594e1ef-9698-4dc5-b22a-f87e47b54441 
2019-05-14 10:03:54.7835|INFO|38|Received request POST /api/v2.0/powerbireports%28Path%3D%27/Training%20and%20Development/Chart%20Types%20v2%20IPNO%27%29/Model.Upload| RequestID = s_8171b33d-ca23-4848-a549-5b4143eff79f 
2019-05-14 10:04:14.2727|INFO|47|Received request GET /api/v2.0/CatalogItems%28f1754efb-6c8c-484b-8376-2ad1d717f252%29| RequestID = 041b7822-ebf5-f3e0-9644-834a086eae5f ClientSessionID = 127b1fd3-7961-433f-34cc-0d47392ec57e 
2019-05-14 10:05:54.0723|INFO|52|Connection dropped. MYDOMAIN\mylogin 10.244.35.144: POST /api/v2.0/powerbireports%28Path%3D%27/Training%20and%20Development/Chart%20Types%20v2%20IPNO%27%29/Model.Upload, Elapsed time 0:01:59.2879034| RequestID = s_8171b33d-ca23-4848-a549-5b4143eff79f

      I can see some errors in the event log (application) for MSOLAP$PBIRS (the captive SSAS instance for my PBIRS instance I assume) but these are some minutes before the issue I am experiencing so may be entirely unrleated.

       

      It looks like this

       

      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
2057
      • Anonymous's avatar
        Anonymous
        Not applicable
        7 years ago

        This gets more and more interesting. Doing some packet inspection I see the following errors on the server

         

        Packet Length =1434 HTTP/1.1 500 Internal Server Error (text/html)

         

        But I can't find anything related to these in the Windows Event Log and nothing useful in the PBI-SSRS log files