Forum Discussion

ruimonteiro's avatar
ruimonteiro
Regular Visitor
10 years ago

Error publishing PBIX file

Hi,

 

I have succesfully migrated a on premise data warehouse to a SQL Azure Data Warehouse, with a fact table containing about 10 millions records. Then I have created a new report with Power BI Desktop in order to fix some relationships and successfully created a few charts.

The problem is in the publish process, I'm getting this error:

 

The underlying connection was closed: An unexpected error occurred on a send.

Stack Trace:

BackendUrl: https://wabi-north-europe-redirect.analysis.windows.net/
ActivityId: c1eb36ab-3c93-45fa-af2a-d0c41de03df7
RequestId: 8321b4d6-dde7-47c1-b6af-fd8276a85ee0
X-PowerBI-Error-Info:
ErrorDetailsCode:
System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host

 

Can anybody help with this issue please? I've read that the upload max size is 250MB. My pbix file has about 1.3GB. If it is the case, is it possible to reduce the size by clearing the imported data rows to desktop and then connect to the SQL Azure Data Warehouse when the report is online?

 

Thanks in advance!

 

Regards,

 

Rui Monteiro.

 

Need Help

1 Reply

  • srookey's avatar
    srookey
    New Member
    10 years ago

    We're experiencing the exact same issue.  I had to delete some tables from our dataset to make the .pbix file small enough to publish.  (Deleting one table with about 50,000 rows reduced our .pbix file from 264 MB to 57 MB.)  We need the ability to include the deleted tables in future reports.  There must be a solution for this.  When the reports publish, they should only be transferring schema information about the dataset - there's no reason the file should be so large.