adding new conn on existing report didnt work

[db042190]

hi as you can see at https://community.fabric.microsoft.com/t5/Service/2-of-3-steps-done-for-non-expiring-id-in-pbi/td-p/... we are exploring non expiring user ids in pbi.

we are lucky i suppose that i was able to change the creds on the conn of an existing/obsolete sql engine based report but before i did that i tried adding a new conn to the gateway for that report using our new non expiring id's creds .  PBI just jumped out of the panel where one does that and if i rememebr correctly left the old conn name as is.   i saw something about the refresh being disabled and the dataset must be fixed first but that seemed backward.   and i saw the same error when i successfully changed creds on the existing conn and everything worked anyway.

currently, in instance security on that user in server roles i have public and sysadmin checked.   to be honest, user mappings , securables and status dont mean anything to me in that same dropdown.   under the db, security , that user, i have db security admin checked under owned schemas, reader , writer and security admin under membership, and nothing under securables.   most of this seems irrelevant to me also if that id is alreayd sysadmin but who knows.

it seems to me we should at least understand this weird behavior because its eventually going to bite us at a more critical time.

[v-dineshya · Accepted solution]

Hi @db042190 ,

Thank you for reaching out to the Microsoft Community Forum.

Please check below things.

1. Verify the non-expiring ID is explicitly added to the SSAS cube’s viewer role, even if it has sysadmin.

2. If possible, RDP into the gateway machine and test SSAS login with the non-expiring ID via SSMS.

3. After changing credentials, confirm that the dataset is correctly mapped to the new connection. If Power BI disables refresh, it may be due to a mismatch or missing permissions.

4. Power BI sometimes retains old connection names even after credential updates. Try removing and re-adding the connection entirely if possible.

5. Please Confirm whether your organization’s non-expiring IDs are permanent or subject to hidden expiry policies.

I hope this information helps. Please do let us know if you have any further queries.

Regards,

Dinesh

[v-dineshya]

Hi @db042190 ,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. And, if you have any further query do let us know.

Regards,

Dinesh

[v-dineshya]

Hi @db042190 ,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. And, if you have any further query do let us know.

Regards,

Dinesh

[v-dineshya]

Hi @db042190 ,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. And, if you have any further query do let us know.

Regards,

Dinesh

[lbendlin]

It is not clear what you are trying to achieve or where you are stuck.  Have you tried to create a new gateway connection?