Forum Discussion

RMDNA's avatar
RMDNA
Solution Sage
9 years ago

"Block length does not match with its complement" error

Before we start, yes, I did find this post. However, the answer and linked explanation were of no use to me. This doesn't involve anything so complicated.

 

I was working on a PBIX, and I saved and closed the file. When I tried to open it maybe 2 minutes later, I got the post title error.

 

That's all that changed, but it refuses to open now. This file isn't something I can rebuild or recreate. Any suggestions? Thanks.

3 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi RMDNA,


    Based on my test, I’m not able to reproduce the issue. In your scenario, you can follow below steps to troubleshoot your issue:


    1. Check if the issue is related to the report itself.

    Create a new report and test.


    2. Check if the issue is related to the data source.

    Verify there is no change happens on data source side within those  “2 minutes“.


    3. Check if the issue is related to network.

    If you get data from online service or web, the issue can be caused by retrieved data are broken, you can ping the target service and keep a stable connection to test again.

     
    4. Use process monitor to monitor the detail processes which the power bi desktop operated: Process Monitor.

     

    Regards,

    Xiaoxin Sheng

     

    • david2's avatar
      david2
      Helper I

      Hi,

       

      I have the same problem, see the details copied below. My pbix file got corrupted after i renamed the file. After renaming it back, it was still corrupted. Any idea what may have caused this?

       

      Thanks!

       

      David

       

      Error Message:

       

      Block length does not match with its complement.

       

      Stack Trace:

       

      System.IO.InvalidDataException: Block length does not match with its complement.

         at System.IO.Compression.Inflater.DecodeUncompressedBlock(Boolean& end_of_block)

         at System.IO.Compression.Inflater.Decode()

         at System.IO.Compression.Inflater.Inflate(Byte[] bytes, Int32 offset, Int32 length)

         at System.IO.Compression.DeflateStream.Read(Byte[] array, Int32 offset, Int32 count)

         at MS.Internal.IO.Packaging.CompressStream.Read(Byte[] buffer, Int32 offset, Int32 count)

         at MS.Internal.IO.Zip.ProgressiveCrcCalculatingStream.Read(Byte[] buffer, Int32 offset, Int32 count)

         at MS.Internal.IO.Zip.ZipIOModeEnforcingStream.Read(Byte[] buffer, Int32 offset, Int32 count)

         at System.IO.Stream.InternalCopyTo(Stream destination, Int32 bufferSize)

         at Microsoft.PowerBI.Packaging.Extensions.StreamExtensions.ReadAllBytes(Stream stream)

         at Microsoft.PowerBI.Packaging.PowerBIPackagingUtils.GetContentAsBytes(IStreamablePowerBIPackagePartContent streamablePowerBIPackagePartContent, Boolean isOptional)

         at Microsoft.PowerBI.Client.Windows.Services.ReportFactory.CreateReportFromPowerBIPackage(IPowerBIPackage powerBIPackage, Byte[] securityBindings, Boolean requiresConversionToReportLayout, IPowerBITelemetryService powerBITelemetryService, PackageValidationResult& mashupValidationResult)

         at Microsoft.PowerBI.Client.Windows.Services.FileManager.OpenFile(String filePath, Stream fileStream, Boolean isReadOnly)

         at Microsoft.PowerBI.Client.Windows.Services.FileManager.OpenFile(String filePathToOpen, IWin32Window ownerWindow, ReportUpgradeResult& upgradeResult)

         at Microsoft.PowerBI.Client.Program.TryOpenOrCreateReport(WindowsHost windowsHost, ISplashScreen splashScreen, IFileManager fileManager, IFileHistoryManager fileHistoryManager, IPowerBIStringProvider stringProvider, String filePath, PBIWinLoadPBIAppAction loadEvent, Report& report, String& importFromExcelFilePath, String& templateFilePath, String& autoRecoveredFilePath, ReportUpgradeResult& upgradeResult)

         at Microsoft.PowerBI.Client.Program.<>c__DisplayClassb.<Main>b__0()

         at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)

       

      Invocation Stack Trace:

       

         at Microsoft.Mashup.Host.Document.ExceptionExtensions.GetCurrentInvocationStackTrace()

         at Microsoft.Mashup.Client.ClientShared.StackTraceInfo..ctor(String exceptionStackTrace, String invocationStackTrace)

         at Microsoft.Mashup.Client.ClientShared.FeedbackErrorInfo..ctor(String message, Nullable`1 errorCode, String requestId, Exception exception)

         at Microsoft.Mashup.Client.ClientShared.UnexpectedExceptionHandler.<>c__DisplayClass1.<HandleException>b__0()

         at Microsoft.Mashup.Client.ClientShared.UnexpectedExceptionHandler.HandleException(Exception e)

         at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)

         at Microsoft.PowerBI.Client.Program.Main(String[] args)