Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Unable to open June 2020 edition of Power BI Desktop. We weren't able to connect to the model.

Before reviewing my error message and details, please note that I have tried everything suggested in the community blog, Power BI blog, and Microsoft Documentation for this error - including but not limited to: reinstalling the gateway, removing the gateway, removing all traces of SSAS tools, removing SSMS, uninstalling 64 bit edition and trying 32 bit edition.  I have never encountered a problem upgrading to a new edition of Power BI.  This is the first time that I have encountered this problem.  I know that this has been posted in the past, but there does not seem to be a clear line of resolution.  At least that I have found.

 

Thanks.

 

Unable to open June 2020 edition of Power BI desktop.

Error: Something went wrong. We weren't able to connect to the model.

Environment: Windows 7 Enterprise SP1

Processor: Intel Core i5-3320M COU @ 2.60GHz

Memory: 8.00 GB (7.87 GB usable)

System Type: 64-bit Operating System

 

Feedback Type: Frown (Error)

Error Message: We weren't able to connect to the model.

Stack Trace:
at Microsoft.PowerBI.Client.Windows.Storage.FileOpenError.HandleError(IWindowService windowService, LocalizedString title)
at Microsoft.PowerBI.Client.Program.TryOpenOrCreateReport(IUIHost uiHost, ISplashScreen splashScreen, IFileManager fileManager, IFileHistoryManager fileHistoryManager, String filePath, FileType fileType)
at Microsoft.PowerBI.Client.Program.<>c__DisplayClass1_0.<Main>b__1()
at Microsoft.PowerBI.Client.Windows.IExceptionHandlerExtensions.<>c__DisplayClass3_0.<HandleExceptionsWithNestedTasks>b__0()
at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)

 

Stack Trace Message:
We weren't able to connect to the model.

 

Invocation Stack Trace:
at Microsoft.Mashup.Host.Document.ExceptionExtensions.GetCurrentInvocationStackTrace()
at Microsoft.Mashup.Client.UI.Shared.StackTraceInfo..ctor(String exceptionStackTrace, String invocationStackTrace, String exceptionMessage)
at Microsoft.PowerBI.Client.Windows.Telemetry.PowerBIUserFeedbackServices.GetStackTraceInfo(Exception e)
at Microsoft.PowerBI.Client.Windows.Telemetry.PowerBIUserFeedbackServices.ReportException(IWindowHandle activeWindow, IUIHost uiHost, FeedbackPackageInfo feedbackPackageInfo, Exception e, Boolean useGDICapture)
at Microsoft.Mashup.Client.UI.Shared.UnexpectedExceptionHandler.<>c__DisplayClass14_0.<HandleException>b__0()
at Microsoft.Mashup.Client.UI.Shared.UnexpectedExceptionHandler.HandleException(Exception e)
at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)
at Microsoft.PowerBI.Client.Program.Main(String[] args)


PowerBINonFatalError:
{"AppName":"PBIDesktop","AppVersion":"2.82.5858.641","ModuleName":"Microsoft.PowerBI.Client.Windows.dll","Component":"Microsoft.PowerBI.Client.Windows.Storage.FileOpenError","Error":"Microsoft.PowerBI.Client.Windows.AnalysisServices.InvalidDynamicPortException","MethodDef":"HandleError","ErrorOffset":"76"}

Status: New
Comments
v-chuncz-msft
Community Support

@dchapman-gnb 

 

Similar issue has been reported: CRI 191989260, so stay tuned.