Unknown Error when trying to Publish Pbix

[langer83]

I get an unknown error when trying to publish a pbix from desktop or getting the data file from online. I've published this file before but started getting an error yesterday when trying to publish/replace dataset. I deleted the reports/dashboard/dataset from online and haven't had any luck publishing it again. Also, I changed the reports and renamed the file which didn't change the erroring.

Error Message:

Publishing failed for an unknown reason.

Stack Trace:

Microsoft.PowerBI.Client.Windows.PowerBIService.PowerBIServiceException: Publishing failed for an unknown reason. ---> System.InvalidOperationException: Publishing failed for an unknown reason. ---> System.Web.HttpUnhandledException: Response Body:
{"id":"a960f7dc-33ae-4483-bed2-d84596351dd5","importState":"Failed","createdDateTime":"2016-07-08T15:03:08.57","updatedDateTime":"2016-07-08T15:03:08.57","error":{"code":""},"name":"Livstyle Reports.pbix"}
--- End of inner exception stack trace ---
--- End of inner exception stack trace ---
at Microsoft.PowerBI.Client.Windows.PowerBIService.PowerBIServiceProxy.GetUploadStatus(String statusUrl, String activityId)
at Microsoft.PowerBI.Client.Windows.PowerBIService.Flows.PublishReportFlow.<>c__DisplayClass10.<PublishReport>b__f()
at Microsoft.PowerBI.Client.Windows.PowerBIService.Flows.BaseFlow`1.MakeWebRequest(WebRequestFunc webRequest, Int32 maxTriesAllowed)
at Microsoft.PowerBI.Client.Windows.PowerBIService.Flows.PublishReportFlow.PublishReport(IFileManager fileManager, String activityId, Boolean overwrite, Boolean configureGateway, PromptUserForGatewayFunc promptUserForGatewayCallback, CancellationToken cancellationToken, String& reportUrl, String& datasetId, Boolean& gatewayConfigured, Boolean& dataSourceNeedsCredentials)
at Microsoft.PowerBI.Client.Windows.PowerBIService.Flows.PublishReportFlow.<ExecuteInternal>b__0()
at System.Threading.Tasks.Task`1.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.FloatingDialog.KoPublishDialog.<<OnLoad>b__4>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.IExceptionHandlerExtensions.<HandleAsyncExceptions>d__0.MoveNext()

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.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.ShowDialogWithTimeout(IWin32Window owner, Nullable`1 showTimeout)
at Microsoft.PowerBI.Client.Windows.FloatingDialog.KoPublishDialog.ShowDialogAndPublish()
at Microsoft.PowerBI.Client.Windows.FloatingDialog.KoPublishDialog.TryShowDialogAndPublish(String groupId, IWin32Window ownerWindow, WindowsHost windowsHost, IWindowService shellService, IReportManager reportManager, IFileManager fileManager, IPowerBIServiceClient powerBIServiceClient, IAuthenticationManager authenticationManager, IClusterManager clusterManager, Boolean configureGateway, TelemetryUserActionId entryPoint, LocalizedString title)
at Microsoft.PowerBI.Client.Windows.MainWindow.<>c__DisplayClass39.<<PublishReport>b__37>d__3c.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.PowerBI.Client.Program.<>c__DisplayClassc.<Main>b__0()
at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)
at Microsoft.PowerBI.Client.Program.Main(String[] args)

BackendUrl
https://wabi-us-north-central-redirect.analysis.windows.net/

ActivityId
e3830c9b-e51d-470b-91cd-98c91b19f2b1

RequestId
9c9639a3-e724-4bb9-bc2c-cb206ba6a055

[Sowmya_S_1997]

Hi Getting same erro we tried re-installing the app but not working kindly help

[roosterBI]

Same thing happened today trying to publish an existing .pbix.  Tried to delete it from pbi service before republishing, and also tried republishing using different name.  Still getting the same error!  I checked datasets.. everything works in pbi desktop, but can't publish

[roosterBI]

Same thing happened today trying to publish an existing .pbix.  Tried to delete it from pbi service before republishing, and also tried republishing using different name.  Still getting the same error!  I checked datasets.. everything works in pbi desktop, but can't publish

[shebr]

Just had exactly the same thing in the past half an hour...

[Seth_C_Bauer]

@langer83 Your most direct route for an answer is probably the "Send a Frown" - click the smiley face in the very top of the PBI Desktop window.

Outside that:

Is this a new file, or did you add something and try to re-publish an existing file?

Do you have any broken measures or errors in your model?

[langer83]

Not a new file but I modified it then tried to publish and replace dataset, failed. Then deleted associated reports/dataset/dashboard and tried to re-published, failed many times. I have no broken measures or errors the model either.

[v-qiuyu-msft]

Hi @langer83,

Based on my test, we can republish reports successfully now. Please try it again in your environment. If issue persists, please check if there are something doesn't meet the requirement listed in this article: Re-publish or replace a dataset published from Power BI Desktop.

If you have any question, please feel free to ask.

Best Regards,
Qiuyun Yu

[KHorseman]

I was still unable to re-publish a previously failed report this morning, but I deleted the entire dataset online and then was able to publish.

[v-qiuyu-msft]

Hi @KHorseman,

Based on my research, if the dataset published in service contain RLS settings, the error will display if we republish the report. Please check if any RLS setting in the dataset.

Best Regards,
Qiuyun Yu

[KHorseman]

@v-qiuyu-msft yeah the file I was trying to republish does have RLS. So is that still the case now? If I want to republish a .pbix with RLS, I first need to delete that dataset online? If so I guess I will just not use RLS until they fix it.

[v-qiuyu-msft]

@KHorseman @langer83 @roosterBI @shebr Currently, if the report in Power BI Service has been configured with RLS, and we have pinned the visual to a dashboard, then republish the .pbix file which contains RLS setting, the error will throw out and publish fail.

To work around the issue temporarily, we need to delete the pinned visual from the dashboard then republish the report. Or we need to delete the RLS settings in .pbix file then republish it.

For this issue, we already report it internally, your patience is greatly appreciated.

Best Regards,
Qiuyun Yu

[KHorseman]

Everybody check your Office 365 Service Health notifications. Microsoft has issued a degredation notice for this. Seems to be widespread. I have been unable to re-publish a previously published report for the last two hours, one with no changes that would otherwise explain a publishing failure. No new changes to its data content or functionality, just a couple of visual-level filter tweaks and the addition of a border to a matrix. So... sit tight and wait for them to fix it I guess.