Error: Object already exists. when displaying Power BI frame about displaymonkey HOT 34 CLOSED

from displaymonkey.

Hi
I have both management and presentation running on same machine and I have tried setup everything from scratch on a clean server 2012 and on Azure webapp, but the error still seen on both environment.

Is it something wrong with power BI embedded code? Other non-BI frames have no problem displaying.

Please let me know if you need more details.

thanks

from displaymonkey.

Are you using any other frame types which require authentication, such as SSRS report or Exchange calendar? If so, do they work without issues?

In DMM application, when you create PwrBI account, does it save without errors? If so, when you edit an existing PwrBI frame settings, does it pull dashboards/tiles/reports at all?

from displaymonkey.

from displaymonkey.

Hi, your PwrBI admin should be able to advise whether or not your organization is using tenants.

from displaymonkey.

Unfortunately the screenshots did not come attached, could you resend/repost please?

from displaymonkey.

from displaymonkey.

I have tried setting this up on 3 different systems - Win 2003, Win 2012 & Azure webapp.

Same problem still seen.

from displaymonkey.

OK, we have released update 1.3.3 this morning. Please install it and I will provide you instructions on how to trace into more details of the error.

from displaymonkey.

nice, will you be updating the binaries in here? http://www.displaymonkey.org/dm/download/

from displaymonkey.

Yes, if they are not there yet. Give me your email, I'll send you the zip archive otherwise.

from displaymonkey.

BTW, I have deployed to Azure webapp via github.

When i tried to add an Azure account, I am getting this error....no problem previously using the last version

Source
AzureAccount/Create
Message
The field IdToken must be a string or array type with a maximum length of '1000'.
Stack trace
at DisplayMonkey.Models.DisplayMonkeyEntities.SaveChanges()
at DisplayMonkey.Controllers.AzureAccountController.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 System.Web.Mvc.Async.TaskAsyncActionDescriptor.EndExecute(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass37.b__36(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResult1.CallEndDelegate(IAsyncResult asyncResult) at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResultBase1.End()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethod(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncControllerActionInvoker.AsyncInvocationWithFilters.b__3d()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.AsyncInvocationWithFilters.<>c__DisplayClass46.b__3f()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass33.b__32(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResult1.CallEndDelegate(IAsyncResult asyncResult) at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResultBase1.End()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethodWithFilters(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass21.<>c__DisplayClass2b.b__1c()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass21.b__1e(IAsyncResult asyncResult)

from displaymonkey.

any luck since my last email?

from displaymonkey.

from displaymonkey.

from displaymonkey.

REF: "The field IdToken must be a string or array type with a maximum length of '1000'"

I'm getting this when I edit or try and re-create the Azure account.

I've tried resetting the user password, issuing new azure ad app keys, blanking the DM database.

Any ideas of what else to try?

It was working fine then my colleague changed the Azure User's password, then this started :(

from displaymonkey.

Yes, we are working on the solution right now. Please stay tuned

from displaymonkey.

Hi @thadspencer, are you working together with @kamwai on the same problem by any chance?

from displaymonkey.

no, but my situation seems similar

from displaymonkey.

Please give me your email, I'm going to send you a patch to try

from displaymonkey.

thank you for the patch - working now 👍

monkey loves max columns :D

from displaymonkey.

from displaymonkey.

DM mailed me a patch including a couple of binaries and a query to run

from displaymonkey.

from displaymonkey.

My pleasure and thank you too, and congratulations on making such awesome software. The D Monkey rocks!

from displaymonkey.

awaiting @kamwai to confirm that the issue can be closed

from displaymonkey.

No luck, still the same error trace. I have deleted every thing and re-do already

{"Error":"Client ID is required.","Stack":" at DisplayMonkey.DataAccess.\u003cExecuteTransactionAsync\u003ed__1e.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at DisplayMonkey.Powerbi.\u003cGetAccessTokenAsync\u003ed__11.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at DisplayMonkey.Powerbi.\u003cGetAccessTokenAsync\u003ed__0.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()\r\n at DisplayMonkey.getAzureToken.\u003cProcessRequestAsync\u003ed__0.MoveNext()","Data":{"FrameId":1403,"PanelId":119,"DisplayId":41,"Culture":"en-us","Details":null}}

from displaymonkey.

Have not heard back from the OP for over 2 weeks now. Considering the issue closed now?

from displaymonkey.

I am having the same issue as the orginal poster kamwai.
Object already exists. Where: Powerbi::callBack::onSuccess
{Error:Object already exists.\r\n,Data:{FrameId:1440,PanelId:132,DisplayId:45,Culture:,Details:null}}

I have deleted the Azure account multiple times and successfully added it back.
I have replaced the presentation and the management code with the latest release.
I can traverse my Workspace and see Tiles and Reports to choose for Frames.
I have altered the column in SQL to extend for Azure Token.
I still have the red dialogue pop up every time a PowerBi component first renders on the screen.

Any thoughts? @DisplayMonkey @kamwai

Update: If I run the source code from my local machine it will connect to Azure Report without the error message. Please help me understand how the SQL hash for the stored passwords work.

Update 2: I can launch the project from my localhost in Visual Studio and successfully create a PowerBI connection and successfully display a Report. I cannot add the connection from the server I'm deployed to. I receive a message stating: AADSTS90014: The request body must contain the following parameter: 'password'., Trace ID: ......

from displaymonkey.

We are now getting the same error on editing or setting up any new Azure accounts:
AADSTS90014: The request body must contain the following parameter: 'password'., Trace ID: ......

Any luck getting the connection added after getting that error, @techie-pete?

EDIT: Turns out our issue was corporate firewall rules blocking some packets. When we ran the management application under my account, which is whitelisted for Azure sites, I was able to modify Azure connections fine. The server account was not whitelisted, so requests weren't getting through properly.

from displaymonkey.

Hi, we have just released an update 1.4.0. Please upgrade and see if it will take care of your issue.

Please note that in this release we have offered an alternative encryption method, to workaround RSA container manageability issues associated with Azure deployment. Please refer to Application Settings paragraph in the DM documentation for more details and examples.

from displaymonkey.

For Azure deployments please consider the new AES with stored key encryption mode DMM application setting. Once you have selected the new encryption mode, please re-enter passwords for all accounts under application settings in DMM.

from displaymonkey.

from displaymonkey.

We are going to close this particular issue for we believe it has been addressed in the latest DM release. If you still have this or similar issue. Please open another ticket. Thanks.

// DM team.

from displaymonkey.