Small and medium business | Business Central, N...

Dynamics web client something went wrong

(0) Share

Report

Posted on by Dimitri Schmidt

Hi All,

We have just moved to an full web client environment of BC18 hosted in Azure.

One SQL server and an applications server.

We have no trouble logging into the webclient but when working in the client, users get the something went wrong message.

The only way to resolve this is to clear the history browser.

Any thoughts about this?

Reagrds,

Dimitri

0027.sww.jpg

I have the same question (0)

All responses (6)

Answers (0)

Sort by

Suggested answer

IB-29041624-0 1,191 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

I think i would start by checking the event log on the application server. That might give you some clue about what the root cause of this is.

Was this reply helpful? Yes No
Dimitri Schmidt 5 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi Inge,

Arround the time of the errors there are events with the:

The Saml2SecurityToken is rejected because the SAML2:Assertion's NotOnOrAfter condition is not satisfied. error.

I did allready changed the Extende Security Token Lifetime to 8

I forgot to mention we are using BC18 with Office 365 Authentification.

Gr,

Dimitri

Was this reply helpful? Yes No
Suggested answer

Marco Mels Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hello,

Please increase it to either 9 - 12 and have the users remember to logoff their sessions when they are done with their daily job.

Thanks.

Was this reply helpful? Yes No
Dimitri Schmidt 5 on at

Like
a
(0)

Report
Copy link

Link copied!

Thanks for this tip,..

I will change het life time and instruct the users to logoff.

Is this a know issue when working with Azure authentication?

Was this reply helpful? Yes No
Suggested answer

Marco Mels Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hello,

The token may expire at some point but it could also be that sessions are not automatically stopped which can be an issue. We hardly get support tickets about this topic anymore when setting it to 8 - 9. 8hrs should usually be sufficient. So a good analysis of the current behavior where users indeed logoff and logon again within that time range is the first advice. If the issue still occurs, feel free to raise is to Microsoft CSS via your partner or CSP so we can take a look together.

Thanks.

Was this reply helpful? Yes No
CU05061403-0 36 on at

Like
a
(0)

Report
Copy link

Link copied!

We are having this issue mainly when changing companies.

I created a post for it too, when we set the token to 12 hours users said the system was then really slow.

https://community.dynamics.com/forums/thread/details/?threadid=d45f5479-0518-ee11-8f6d-00224827e389

Was this reply helpful? Yes No

Join the conversation

Community site session details

Dynamics web client something went wrong

Helpful resources

News and Announcements

Quick Links

Season of Sharing Community Challenge Launch!

Women in Power Builds Momentum

Congratulations to the May Top 10 Community Leaders

Leaderboard > Small and medium business | Business Central, NAV, RMS

Featured topics

Product updates

Community site session details

Dynamics web client something went wrong

Helpful resources

News and Announcements

Quick Links

Season of Sharing Community Challenge Launch!

Women in Power Builds Momentum

Congratulations to the May Top 10 Community Leaders

Subscribe to this forum!

Select categories

Leaderboard > Small and medium business | Business Central, NAV, RMS

Featured topics

Product updates