cancel
Showing results for 
Search instead for 
Did you mean: 

Suddenly unable to open a .pbix file- "Connections not found".

I have no clue what is going on.  The report file was working normally yesterday, until I uploaded it to PowerBI.com.   Now I can only edit it in the online app.  I can't open it in the desktop app at all.  I keep getting the error message, "Required property 'Connections' not found in JSON. Path ", line 1, position 136. "    How am I supposed to fix this?  I don't recall doing anything with JSONs for this report.  

 

Why is the file opening online, but not on desktop? 

 

Below is the output from "Copy Details" that came with my prompt to report an issue.   I don't know what any of this means, but hopefully it helps.  Thanks in advance.  

 

Feedback Type:
Frown (Error)

Timestamp:
2020-08-13T13:47:57.4575372Z

Local Time:
2020-08-13T08:47:57.4575372-05:00

Session ID:
2d4022bd-a2ed-42f8-8725-c00bc329ea1e

Release:
June 2019

Product Version:
2.70.5494.761 (19.06) (x64)

Stack Trace:
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.EndProcessProperty(Object newObject, JsonReader reader, JsonObjectContract contract, Int32 initialDepth, JsonProperty property, PropertyPresence presence, Boolean setDefaultValue)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.PopulateObject(Object newObject, JsonReader reader, JsonObjectContract contract, JsonProperty member, String id)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateObject(JsonReader reader, Type objectType, JsonContract contract, JsonProperty member, JsonContainerContract containerContract, JsonProperty containerMember, Object existingValue)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)
at Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType)
at Newtonsoft.Json.JsonConvert.DeserializeObject(String value, Type type, JsonSerializerSettings settings)
at Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value, JsonSerializerSettings settings)
at Microsoft.PowerBI.Client.Windows.Services.ReportFactory.DeserializeJsonObject[T](String jsonContent)
at Microsoft.PowerBI.Client.Windows.Services.ReportFactory.DeserializeJson(Byte[] data)
at Microsoft.PowerBI.Client.Windows.Services.ReportFactory.CreateReportFromPowerBIPackage(IPowerBIPackage powerBIPackage, String pbixFilePath, Byte[] securityBindings, Boolean requiresConversionToReportLayout, PowerBIPackageOpenOptions options, IPowerBITelemetryService powerBITelemetryService, IAnalysisServicesService analysisServices, PackageValidationResult& mashupValidationResult)
at Microsoft.PowerBI.Client.Windows.Services.PowerBIPackagingService.Open(FileStream fileStream, IPowerBIWindowService windowService, Nullable`1 entryPoint, PowerBIPackageOpenOptions options, ReportPreparerResult& prepareResult)
at Microsoft.PowerBI.Client.Windows.Services.FileManager.<LoadFromPbix>d__20.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 Microsoft.PowerBI.Client.Windows.Services.UIBlockingService.<>c__DisplayClass15_0`1.<<BlockUIAndRun>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.PowerBI.Client.Windows.Services.UIBlockingService.WaitOnUIThreadForTaskCompletion(Task task)
at Microsoft.PowerBI.Client.Windows.Services.UIBlockingService.BlockUIAndRun[T](Func`1 asyncMethod)
at Microsoft.PowerBI.Client.Windows.Services.FileManager.OpenFile(IPowerBIWindowService windowService, IPbixFile fileToOpen, Nullable`1 entryPoint)
at Microsoft.PowerBI.Client.Windows.Services.FileOperationUIHandler.OpenFileInternal(IPowerBIWindowService windowService, IExceptionHandler exceptionHandler, IQueryServices queryServices, IOpenSaveUI openSaveUI, TelemetryUserActionId entryPoint, IPbixFile pbixFile, Boolean fromRecentFile)
at Microsoft.PowerBI.Client.Windows.Services.FileOperationUIHandler.OpenLocalFile(IPowerBIWindowService windowService, IExceptionHandler exceptionHandler, IQueryServices queryServices, TelemetryUserActionId entryPoint, String filePath, Boolean fromRecentFile)
at Microsoft.PowerBI.Client.Windows.FileCommands.OpenFileLocal(IPowerBIWindowService windowService, IExceptionHandler exceptionHandler, OpenFileCommandParameter openParameters)
at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)

OS Version:
Microsoft Windows NT 10.0.17134.0 (x64 en-US)

CLR Version:
4.7 or later [Release Number = 461808]

Peak Virtual Memory:
37.8 GB

Private Memory:
252 MB

Peak Working Set:
439 MB

IE Version:
11.590.17134.0

User ID:
03e6a4ff-e94a-4e0f-9544-01d29ab3e69d

Workbook Package Info:
1* - en-US, Query Groups: 0, fastCombine: Disabled, runBackgroundAnalysis: True.

Telemetry Enabled:
True

Model Default Mode:
Empty

Snapshot Trace Logs:
C:\Users\a1654246\AppData\Local\Microsoft\Power BI Desktop\FrownSnapShot887835851.zip

Disabled Preview Features:
PBI_shapeMapVisualEnabled
PBI_SpanishLinguisticsEnabled
PBI_NewWebTableInference
PBI_showIncrementalRefreshPolicy
PBI_showManageAggregations
PBI_improvedFilterExperience
PBI_qnaLiveConnect
PBI_keyDrivers
PBI_userFavoriteResourcePackagesEnabled

Disabled DirectQuery Options:
TreatHanaAsRelationalSource

Cloud:
GlobalCloud

DPI Scale:
100%

Supported Services:
Power BI

Status: New
Comments
Community Support

@ablanke1 ,

 

Which data source are you connecting? Make sure power bi desktop has been updated to the latest version. In addtion, if this issue persists, I would suggest you create a suppport ticket here for further analysis.

Support Ticket.gif 

Regards,

Jimmy Tao

New Member

@v-yuta-msft 

 

Thanks for the response.  I thought I already had the newest version of PowerBI installed, but I rebooted my computer and then I was able to open my report again.