Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't Obtain Account Information when saving #1317

Closed
edhans opened this issue Jun 14, 2024 · 12 comments
Closed

Can't Obtain Account Information when saving #1317

edhans opened this issue Jun 14, 2024 · 12 comments
Assignees
Labels
issue: bug Confirmed as a bug in TE3

Comments

@edhans
Copy link

edhans commented Jun 14, 2024

Description

Could be coincidence, or something new in 3.16. This started for me yesterday after upgrading. When I save a model, probably 25% of the time I get the following error when trying to save against an XMLA endpoint to a Power BI Premium Capacity.

image

Saving again so far has always fixed it, so it isn't preventing work from getting done, just annoying.

Tabular Editor 3 Version

3.16

Screenshots

No response

Steps to Reproduce

No response

Expected behavior

No response

Crash Report

No response

Windows Version

11

@edhans edhans added the template: issue Issue report created by user, needs to be triaged label Jun 14, 2024
@mlonsk mlonsk added issue: awaiting reply More information is needed and removed template: issue Issue report created by user, needs to be triaged labels Jun 17, 2024
@mlonsk mlonsk self-assigned this Jun 17, 2024
@mlonsk
Copy link
Collaborator

mlonsk commented Jun 17, 2024

Hi @edhans

That does sound annoying.
I have not been able to reproduce it by making random changes and saving it. Are you making any specific changes at that point that you are saving?

@edhans
Copy link
Author

edhans commented Jun 17, 2024

Not that I can think of. 99% of what I am doing is just adding or changing measures. The model otherwise is pretty stable.

@mlonsk
Copy link
Collaborator

mlonsk commented Jun 17, 2024

Could you share a Session ID (Help -> About Tabular Editor) with us the next time it happens, either here or at support@tabulareditor.com ? We can then try to look at the telemetry to investigate what is happening.

@edhans
Copy link
Author

edhans commented Jun 17, 2024

It just happened 30 seconds ago. Session ID d1c76377-c61c-4759-a8d3-d1d2322ca003

I had just duplicated a measure and saved the model.

@mlonsk mlonsk added issue: under review Being looked into by TE team and removed issue: awaiting reply More information is needed labels Jun 17, 2024
@edhans
Copy link
Author

edhans commented Jun 17, 2024

Just happened again. Made a very small change to a measure. Save, error shown above, click ok, then save and it works. It has never not worked on the 2nd save. Same session ID as above.

@otykier
Copy link
Collaborator

otykier commented Jun 18, 2024

Thanks Ed, we see the logs now. It seems to be a problem in AMO/TOM v. 19.80.0 which we started using in version 3.16.0 of Tabular Editor. We have reached out to Microsoft to better understand what's going on.

@edhans
Copy link
Author

edhans commented Jun 18, 2024

Thanks Daniel. I was following the thread at #1322 and wondered if it was related. 🤨

@mlonsk
Copy link
Collaborator

mlonsk commented Jun 18, 2024

It certainly seems to be; as Daniel said in #1322, we are considering our next steps.

@otykier
Copy link
Collaborator

otykier commented Jun 18, 2024

Hi @edhans
We have a new build ready where we've rolled back AMO/TOM to 19.79.1.1. This is the same version that we used in TE 3.15.0.

Could you give this new build a shot and see if this fixes the issue for you? Thanks!

Download options:

(Release notes identical to 3.16.1 with the addition that AMO/TOM has been downgraded to 19.79.1.1)

@edhans
Copy link
Author

edhans commented Jun 18, 2024

Will do. Installing now but won't be getting to work on models for a few hours this morning.

@edhans
Copy link
Author

edhans commented Jun 18, 2024

FYI @otykier - I've been working for about 3 straight hours now and rock solid stable. This issue has not come back since upgrading to 3.16.2, so yeah, that new component from MS is a mess. Thanks!

@mlonsk mlonsk added issue: bug Confirmed as a bug in TE3 and removed issue: under review Being looked into by TE team labels Jun 19, 2024
@mlonsk
Copy link
Collaborator

mlonsk commented Jun 19, 2024

Thank you for testing @edhans, much appreciated.

We have just publicly released 3.16.2 and will close this issue.

@mlonsk mlonsk closed this as completed Jun 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue: bug Confirmed as a bug in TE3
Development

No branches or pull requests

3 participants