Forum Discussion
Unable to open a .pbix file
Has anyone find a solution to this? It is the 4th month that this happens at the begining of the month. I cannot open the .pbix file and the refreshes sarted failing. Everything was fine 2 days ago and everything goes back to normal 2 days after. This is so anoying as the information at the begining of the month is so sensitive for my management team.
They are loosing trust on this tool... please help!
Here are the errors in case someone is experiencing the same...
Data refresh error:
An argument of function 'DATE' has the wrong data type or the result is too large or too small. The current operation was cancelled because another operation in the transaction failed.
.Pbix file error when trying to open the file:
Feedback Type:
Frown (Error)
Error Message:
Failed to save modifications to the server. Error returned: 'An argument of function 'DATE' has the wrong data type or the result is too large or too small.
The current operation was cancelled because another operation in the transaction failed.
'.
Stack Trace:
at Microsoft.AnalysisServices.Tabular.Model.SaveChangesImpl(SaveOptions options)
at Microsoft.PowerBI.Modeler.ModelManager.<SaveChanges>b__230_0()
at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingTelemetryService.<>c__DisplayClass6_0`1.<RunInActivity>b__0()
at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingTelemetryService.RunInActivity(ModelingActivityKind activity, Action action)
at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingTelemetryService.RunInActivity[T](ModelingActivityKind activity, Func`1 action)
at Microsoft.PowerBI.Modeler.ModelManager.SaveChanges(String description)
at Microsoft.PowerBI.Modeler.ModelManager.InternalTransaction.Commit(Boolean recalc)
at Microsoft.PowerBI.Modeling.Engine.Authoring.AsyncModelAuthoringService.ModelAuthoringTransaction.<>c__DisplayClass17_0.<Commit>b__0()
at Microsoft.PowerBI.Modeling.Engine.Authoring.ModelAuthoringExceptionHandler.AddModelChangeResultToExceptions(Action action, ModelChangeResult modelChangeResult)
at Microsoft.PowerBI.Modeling.Engine.Authoring.AsyncModelAuthoringService.ModelAuthoringTransaction.Commit(RecalcBehavior recalcBehavior)
at Microsoft.PowerBI.Client.Windows.ReportPreparer.<>c.<PerformRecalc>b__22_0(IExtendedModelChangeScope scope)
at Microsoft.PowerBI.Modeling.Engine.Authoring.AsyncModelAuthoringService.RunOutOfBandExtendedModelChange(Action`1 extendedModelChange, IDataModel dataModel, IModelManager modelManager, Boolean roleChangesImpactQueries, IRefreshPolicyUpdater refreshPolicyUpdater, Boolean skipDataModelTracing)
at Microsoft.PowerBI.Modeling.Engine.ModelingEngine.RunOutOfBandExtendedModelChange(Action`1 extendedModelChange, IDataModel dataModel, IModelManager modelManager, Boolean roleChangesImpactQueries, IRefreshPolicyUpdater refreshPolicyUpdater)
at Microsoft.PowerBI.Client.Windows.AnalysisServices.AnalysisServicesDatabaseLocal.RunOutOfBandExtendedModelChange(Action`1 extendedModelChange, IRefreshPolicyUpdater refreshPolicyUpdater, Boolean requireASDBToBeUnattached)
at Microsoft.PowerBI.Client.Windows.ReportPreparer.PerformRecalc(Report report, IPowerBIWindowService windowService)
at Microsoft.PowerBI.Client.Windows.ReportPreparer.Prepare(Report report, PackageValidationResult mashupResult, IPowerBIWindowService windowService, String fileName, ILuciaFeatureSwitchProxy luciaFeatureSwitchProxy, Nullable`1 entryPoint, Version pbixFileVersion, Boolean suppressRecalc)
at Microsoft.PowerBI.Client.Windows.Services.PowerBIPackagingService.Open(Stream stream, String streamName, IPowerBIWindowService windowService, Nullable`1 entryPoint, PowerBIPackageOpenOptions options, ReportPreparerResult& prepareResult)
at Microsoft.PowerBI.Client.Windows.Services.FileManager.<LoadFromPbix>d__24.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[T](Task`1 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.Program.TryOpenOrCreateReport(IUIHost uiHost, IPowerBIWindowService windowService, IFileManager fileManager, IFileHistoryManager fileHistoryManager, String filePath, FileType fileType)
at Microsoft.PowerBI.Client.Program.<>c__DisplayClass4_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:
Failed to save modifications to the server. Error returned: 'An argument of function 'DATE' has the wrong data type or the result is too large or too small.
The current operation was cancelled because another operation in the transaction failed.
'.
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__DisplayClass15_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.88.1385.0","ModuleName":"Microsoft.PowerBI.Tabular.dll","Component":"Microsoft.AnalysisServices.Tabular.Model","Error":"Microsoft.AnalysisServices.OperationException","MethodDef":"SaveChangesImpl - PFE_XL_EXCEL_NUM,PFE_SERVERBASE_OPERATION_CANCELLED_BECAUSE_OTHER_ONE_FAILED","ErrorOffset":"0"}
PowerBINonFatalError_MethodDefDescription:
PFE_XL_EXCEL_NUM,PFE_SERVERBASE_OPERATION_CANCELLED_BECAUSE_OTHER_ONE_FAILED
ModelChangeResult:
{"changes":[],"hasQueryImpact":false}
PowerBIUserFeedbackServices_IsReported:
True