Forum Discussion
Ongoing Publishing Issues
I only got into renaming because of this issue. I have tried to rename on the desktop and publish as a new dataset and report on the web app just to see if it is working and it failed. I have also tried to delete the report and dataset from the web now and tried to republish and still nothing. This issue has been persistent well before any name change occured.
at this point I am about to give up on Power BI, I have had to recreate the same dashboards 6 times now (will be 7 soon), potentially recreate my scheme and reports, and have pushed back projects over a month pending a fix for these issues.
I even attempted to purchase a Pro ticket for 3 days and the site kepy giving me an error. Pro is now letting me purchase but I am not confident there is a fix and can not justify spending upwards of $2000 to fix issues before even being able to test out the software.
edit: in an effort to remedy the issue, I disabled all queries and was planning on adding them back one by one and publishing after each addition. I made my first query and published under all new names. Interestingly enough I found that it did not fail and when I went to the web app found a previous attempt at this report I was originally attempting to publish appeared. I hit refresh and it went away, but I am now continuing to add back table by table (enable data load) and testing tof ind the issue.
Edit 2: So I continued doing this and ran into the same issue, what I did find however was that the aggregated and expanded columns on one of my tables was causing an issue. By replacing amy filter functions with calcualte instead and disposing of all aggregate/expand/merge queries I was finally able to get it to load back up properly while decreasing the file size significantly. Thank you for the assistance Meysun
edit 3: and its down again. Failed to refresh after publish
OK. If I understand correctly, when you are publishing a report then there is no issue.
Only when you delete just the report or rename just the dataset in the web, and then publish then it gives error. Is that correct?
Sorry let me clarify, I just had 2 scenarios.
1. I repost my original data set, it says it published but the online web app does not reflect this
2. I delete the report for my original data set and republish. The desktop app says it published successfully but the report does not show up on the web app. When I make an update it also says successful and that is overwritting a report that already exists but still no report comes up.
3. I rename my data set to something new, publishing fails with a different error every time (unexpected failure, cannot create link)
4. Tried to create a completly new dataset as suggested. No issue publishing or viewing on web app.
I removed the data set and tried to add it back as this use to fix the problem. I was acoiding this solution since it destroys all my dashboards, but I decided to do it since I need these active by EOD. But now this wont even work and I have lost my dashboards.
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.
--- End of inner exception stack trace ---
at Microsoft.PowerBI.Client.Windows.PowerBIService.PowerBIServiceClient.WaitForImportToComplete(String authorization, String activityId, String statusUrl, CancellationToken cancellationToken, String& requestId, String& datasetId, String& reportUrl)
at Microsoft.PowerBI.Client.Windows.PowerBIService.PowerBIServiceClient.<>c__DisplayClass12.<PublishReport>b__11(String& innerRequestId)
at Microsoft.PowerBI.Client.Windows.PowerBIService.PowerBIServiceClient.MakeWebRequest(WebRequestFunc webRequest, String& requestId, Int32 maxTriesAllowed)
at Microsoft.PowerBI.Client.Windows.PowerBIService.PowerBIServiceClient.PublishReport(BIPackageManager biPackageManager, String activityId, Boolean overwrite, Boolean configureGateway, PromptUserForGatewayFunc promptUserForGatewayCallback, CancellationToken cancellationToken, String& requestId, String& reportUrl, String& datasetId, Boolean& gatewayConfigured, Boolean& dataSourceNeedsCredentials)
at Microsoft.PowerBI.Client.Windows.PowerBIService.PowerBIServiceClient.<>c__DisplayClass1.<PublishReportAsync>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.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, IPowerBIServiceClient powerBIServiceClient, Boolean configureGateway, TelemetryUserActionId entryPoint, LocalizedString title)
at Microsoft.PowerBI.Client.Windows.MainWindow.<>c__DisplayClass27.<<PublishReport>b__26>d__29.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`1.TrySetResult(TResult result)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1.SetResult(TResult result)
at Microsoft.PowerBI.Client.Windows.MainWindow.<IsSaveChangesPromptNeeded>d__4c.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`1.TrySetResult(TResult result)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1.SetResult(TResult result)
at Microsoft.PowerBI.Client.Windows.CefSharpFramework.CefWebBrowser.<InvokeScriptAsync>d__1`1.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__DisplayClassb.<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-east2-redirect.analysis.windows.net/ActivityId
b81de3a1-7f68-42ad-8bf5-061605f733c9RequestId
7d2b168f-4aac-4c70-8759-1bd3df8c0bbaOnce published to the web, the report name and dataset name should be the same. I think the issue here is you are renaming just one or deleting just one and then republishing it.
If you are renaming it on the web, rename both the report and dataset.
If you are deleting it on the web, then delete both the report and dataset.
In those cases, subsequent republishing from Desktop should work.
I only got into renaming because of this issue. I have tried to rename on the desktop and publish as a new dataset and report on the web app just to see if it is working and it failed. I have also tried to delete the report and dataset from the web now and tried to republish and still nothing. This issue has been persistent well before any name change occured.
at this point I am about to give up on Power BI, I have had to recreate the same dashboards 6 times now (will be 7 soon), potentially recreate my scheme and reports, and have pushed back projects over a month pending a fix for these issues.
I even attempted to purchase a Pro ticket for 3 days and the site kepy giving me an error. Pro is now letting me purchase but I am not confident there is a fix and can not justify spending upwards of $2000 to fix issues before even being able to test out the software.
edit: in an effort to remedy the issue, I disabled all queries and was planning on adding them back one by one and publishing after each addition. I made my first query and published under all new names. Interestingly enough I found that it did not fail and when I went to the web app found a previous attempt at this report I was originally attempting to publish appeared. I hit refresh and it went away, but I am now continuing to add back table by table (enable data load) and testing tof ind the issue.
Edit 2: So I continued doing this and ran into the same issue, what I did find however was that the aggregated and expanded columns on one of my tables was causing an issue. By replacing amy filter functions with calcualte instead and disposing of all aggregate/expand/merge queries I was finally able to get it to load back up properly while decreasing the file size significantly. Thank you for the assistance Meysun
edit 3: and its down again. Failed to refresh after publish