Finance | Project Operations, Human Resources, ...

Has anyone solved the Forbidden error that pops up on logging in prior to workflow designer?

(0) Share

Report

Posted on by CO-22040757-0

Our production FnO instance has an issue with the workflows. After clicking the workflow type; the popup presents the login and after login an OS window states "Forbidden". What I've checked: no permission issues in SF, all DB users have appropriate memberships and permissions, the user account is the admin used to setup the entire infrastructure. I saw a suggestion to use a Microsoft account, I'm yet to try this as the owner of the account will be available next working day. I have hardly seen a reliable solution to this. Any help will be appreciated

[View:/cfs-file/__key/communityserver-discussions-components-files/765/bandicam-2023_2D00_06_2D00_02-15_2D00_37_2D00_26_2D00_663.mp4:320:240]

I have the same question (0)

All responses (8)

Answers (0)

Suggested answer

Komi Siabi 13,109 Most Valuable Professional on at

Like (0)

Report

Dear noetico360,

Have you tried used Microsoft edge browser instead?

Was this reply helpful? Yes No
GirishS 27,827 Moderator on at

Like (0)

Report

Hi,

As komi mentioned try to open it in microsoft edge. I too faced the similar issue and it got fixed when I open it via Microsoft edge.

Thanks,

Girish S.

Was this reply helpful? Yes No
Suggested answer

Mohit Rampal 12,565 Moderator on at

Like (0)

Report

Hi, In addition to above suggestions, you can check this old thread (Try Using Edge first as mentioned above)

community.dynamics.com/.../workflow-editor-can-not-open

www.gangsta.se/.../20210303-workflow-editor-not-working-in-chrome

Was this reply helpful? Yes No
CO-22040757-0 5 on at

Like (0)

Report

Thanks, yes! This is in Edge, also configured with a oneclick extension in chrome. In both cases; the login screen appears. Previously the package will just download to the file system. It’s the same on Edge. I assume the users crucial for this should be the admin account, axdbadmin and service fabric gMSA accounts. I don’t know if there are any other permissions that one may look at. I’ve also reviewed the certificates and ensures they’re in the local machine store. Where else can I look?

Was this reply helpful? Yes No
CO-22040757-0 5 on at

Like (0)

Report

You mean the “forbidden” error went away after opening on edge? Please look at the video I posted at let me know if you had this error and if opening on edge solved it. I

Was this reply helpful? Yes No
CO-22040757-0 5 on at

Like (0)

Report

Update: I have also got the personnel to use the Microsoft account used during the provisioning with Azure/LCS and that’s not a solution (someone stated on the community that this option solved the problem). Is this a bug? There are still no errors or even warning anywhere.

Was this reply helpful? Yes No
André Arnaud de Cal... 301,141 Super User 2025 Season 2 on at

Like (0)

Report

Hi noetico360,

I have no experience myself with workflow configuration on an on-premise environment. On cloud instances, I have seen this issue before when someone tried to open the workflow configuration with an account that was not part of the tenant.

Is it working in your UAT environment? If so, are you able to find some differences, like the domain/tenant?

If you keep having this issue, you can also consider creating a ticket for Microsoft Support.

Was this reply helpful? Yes No
CO-22040757-0 5 on at

Like (0)

Report

Thanks for your response. We were pressed during this deployment and went straight to production, no UAT sandbox environment although this will be done as the customization progresses. I think we'll raise a ticket finally. Thanks again.

Was this reply helpful? Yes No