Reply
Highlighted
Regular Visitor
Posts: 25
Registered: ‎07-28-2015

Another fun new error! FailedToRefreshPackageAfterImportError

[ Edited ]

Anyone received this error below?  This is a new error I'm seeing in PBI desktop when attempting to publish to PBI online.

 

Error Message:

Publishing failed for an unknown reason. (FailedToRefreshPackageAfterImportError)

Stack Trace:

BackendUrl: https://wabi-us-east2-redirect.analysis.windows.net/
ActivityId: 3d1cdff4-29c2-413d-9c04-16305b356cea
RequestId: 3143abf3-2965-4680-bfcc-4de5d5f2c071
ErrorCode: FailedToRefreshPackageAfterImportError
System.InvalidOperationException: Publishing failed for an unknown reason. (FailedToRefreshPackageAfterImportError)

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.PowerBI.Client.Windows.IExceptionHandlerExtensions.<HandleAsyncExceptions>d__0.MoveNext()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.MoveNextRunner.Run()
at System.Threading.Tasks.AwaitTaskContinuation.RunCallback(ContextCallback callback, Object state, Task& currentTask)
at System.Threading.Tasks.Task.FinishContinuations()
at System.Threading.Tasks.Task.Finish(Boolean bUserDelegateExecuted)
at System.Threading.Tasks.Task`1.TrySetException(Object exceptionObject)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1.SetException(Exception exception)
at Microsoft.PowerBI.Client.Windows.FloatingDialog.KoPublishDialog.<<OnLoad>b__4>d__5.MoveNext()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.MoveNextRunner.Run()
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Delegate.DynamicInvokeImpl(Object[] args)
at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)
at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
at System.Windows.Forms.Control.InvokeMarshaledCallbacks()
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
at Microsoft.Mashup.Client.ClientShared.WindowManager.ShowDialog[T](T form, IWin32Window owner)
at Microsoft.Mashup.Client.ClientShared.Ux.FloatingDialog.FloatingDialog.ShowDialog(IWin32Window owner, Nullable`1 showTimeout)
at Microsoft.PowerBI.Client.Windows.FloatingDialog.KoPublishDialog.ShowDialogAndPublish()
at Microsoft.PowerBI.Client.Windows.FloatingDialog.KoPublishDialog.TryShowDialogAndPublish(Report report, IWin32Window ownerWindow, WindowsHost windowsHost, IWindowService shellService, BIPackageManager biPackageManager, IPowerBIService powerBIService, Boolean configureGateway, TelemetryUserActionId entryPoint, LocalizedString title)
at Microsoft.PowerBI.Client.Windows.MainWindow.PublishReport(TelemetryUserActionId entryPoint)
at Microsoft.Mashup.Client.Windows.Ribbon.RibbonCommandHandler.Execute(UInt32 commandId, CommandExecutionVerb verb, PropertyKeyRef keyRef, PropVariantRef currentValue, IUISimplePropertySet commandExecutionProperties)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
at Microsoft.Mashup.Client.ClientShared.WindowManager.ShowDialog[T](T form, IWin32Window owner)
at Microsoft.PowerBI.Client.Program.<>c__DisplayClassb.<Main>b__0()
at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)
at Microsoft.PowerBI.Client.Program.Main(String[] args)

 

Super User
Posts: 3,461
Registered: ‎06-25-2015

Re: Another fun new error! FailedToRefreshPackageAfterImportError

@jseek You'll get better assistance submitting a frown. That is a lot of error result for anyone to actually match up to something. The only other checks you could do are validate that the size of the file is smaller than 250mb, or other known "breakers".

Near SE WI? Join our PUG MSBIWI
Regular Visitor
Posts: 39
Registered: ‎11-13-2015

Re: Another fun new error! FailedToRefreshPackageAfterImportError

I have exactly the same error message when publishing. It could have something to do with the restore I had to do after a windows update ruining my nvidia driver setup. This looks like it messed up the gateway because so it failed to connect. I reinstalled it and now it works again. But there is something wrong with the certificate. Renewal in the app leads to a message below :

 

PersonalGateway_DataSourceKindLabel: 
Verwerkingsfout:Cannot decrypt the credential for data source NewPbiDataSource_3e3ca337-9163-4f75-9d6b-2e57a8ebadfa. The credential is missing or the certificate is changed. Please make sure the certificate has not been changed since it is configured in gateway management console.
Cluster-URI:WABI-NORTH-EUROPE-redirect.analysis.windows.net
Activiteits-id:a8c4f986-0d09-46c9-a081-82512b7fc5f4
Aanvraag-id:be5a3e7e-afbf-47f0-88da-41c854fe2aac
Tijd:2016-01-27 09:39:36Z

 

Regular Visitor
Posts: 25
Registered: ‎07-28-2015

Re: Another fun new error! FailedToRefreshPackageAfterImportError

Sent already.  But still find it helpful to post in the community, to know if others are receiving the same issues.

 

Thanks for the info.  The file is below 55mb.  So far everything has worked fine, and there wasn't any changes I made other than refreshing data, so seems odd.

 

Regular Visitor
Posts: 39
Registered: ‎11-13-2015

Re: Another fun new error! FailedToRefreshPackageAfterImportError

One of the files simply got through without any explanation. The second still stubling...

JP1 Frequent Visitor
Frequent Visitor
Posts: 3
Registered: ‎02-03-2016

Re: Another fun new error! FailedToRefreshPackageAfterImportError

I had the same error today. I renamed the .pbix and it was solved.

Regular Visitor
Posts: 26
Registered: ‎08-22-2015

Re: Another fun new error! FailedToRefreshPackageAfterImportError

Big Big issue with this error. Send a frown to Microsoft. They do not have any fix. My trust is going down severely with Power BI due to such critical errors which makes us helpless.

 

a. I also renamed the file, published it but after few days.. same error again.

 

b. Secondly, renaming the file creates a new dataset in service, thus my dashboard linked to original dataset is gone. (And I had many dashboard linked). How many times I have to recreate the dashboard. This is completely frustating.

 

Microsoft - Pls do something about it OR allow to change connection of existing dashboard to new dataset.

 

Arup

 

PS: My file size is 60 MB. 

Member
Posts: 67
Registered: ‎11-09-2015

Re: Another fun new error! FailedToRefreshPackageAfterImportError

INCIDENTDATE AND TIMESTATUSDETAILS
PB42278Feb 3, 2016 9:16 PMService degradationCurrent Status: Engineers continue to investigate potential mitigation options. In parallel, engineers are investigating a potential caching issue that may be contributing to the problem.

User Impact: The affected users are unable to upload new workbooks.

Customer Impact: Analysis of incident scope indicates that many customers appear to be impacted by this event. For those customers affected, this issue potentially affects any user attempting to access or use the affected feature. Some customers have reported that their organization is affected by this issue.

Incident Start Time: Friday, January 22, 2016, at 10:05 PM UTC

Preliminary Root Cause: As part of our ongoing work to improve the service an update was deployed to a portion of infrastructure that caused impact to the Power BI service.

Next Update by: Thursday, February 4, 2016, at 8:00 PM UTC
 Feb 3, 2016 7:49 PMService degradationCurrent Status: Engineers have identified that a recent update to the service has caused impact to workbook functionality. Engineers are in the process of developing a solution to mitigate impact.

User Impact: The affected users are unable to upload new workbooks.

Customer Impact: Analysis of incident scope indicates that many customers appear to be impacted by this event. For those customers affected, this issue potentially affects any user attempting to access or use the affected feature. Some customers have reported that their organization is affected by this issue.

Incident Start Time: Friday, January 22, 2016, at 10:05 PM UTC

Preliminary Root Cause: As part of our ongoing work to improve the service an update was deployed to a portion of infrastructure that caused impact to the Power BI service.

Next Update by: Wednesday, February 3, 2016, at 10:00 PM UTC
 Feb 3, 2016 7:36 PMInvestigatingCurrent Status: Engineers are investigating an issue in which some users are experiencing problems accessing or using Power BI services or features. This event is actively being investigated. More information will be provided shortly.

User Impact: The affected users are unable to upload new workbooks.

Customer Impact: Analysis of incident scope indicates that many customers appear to be impacted by this event. For those customers affected, this issue potentially affects any user attempting to access or use the affected feature. Some customers have reported that their organization is affected by this issue.

 

Occasional Visitor
Posts: 1
Registered: ‎02-15-2016

Re: Another fun new error! FailedToRefreshPackageAfterImportError

Any update on this error?  We're hitting same issue.

 

Thanks,

Frequent Visitor
Posts: 3
Registered: ‎08-07-2015

Re: Another fun new error! FailedToRefreshPackageAfterImportError

This becoming a big issue in my company as well. Any fixes/ideas would be appreciated. Currently the only thing that works for us is to delete the dataset and reupload. This however kills all dashboards as well which have taken hours to produce so it's not a workable solution.

 

Cheers