Announcements
I have upgraded client Platform from BC14 Cu16 TO BC14 CU23. Application version is still CU11. Client is using multiple add-ons and they might have be based on different CUs. But, all add-on functions correctly.
If User session is idle for 20-30 minutes then it gets timeout. We have configured it for 8:00:00 Hours. Still it is timeout before it.
Any suggestion is appreciated.
Web Client Time out:
Business Central Administration -> Configuration
Thank you for reply.
I have added Web Client URL to Browser setting -> "Never put these sites to sleep" but it does not work.
Hello,
Several browsers have sleeping tabs. You can disable these to see if that improves the experience. They suspend the tabs and this may cause the session time out timer to start.
Thanks.
Do you have any idea how does browser cache affecting?
Below is event Log.
Error accessing Website
Type: Microsoft.Dynamics.Framework.UI.FormNotFoundException
StackTrace:
at Microsoft.Dynamics.Framework.UI.InteractionParameterHelper.GetLogicalControl(UISession uiSession, ClientLogicalControlReference clientLogicalControlReference) in s:\repo\src\platform\client\Shared\Prod.ClientFwk\Interactions\InteractionParameterHelper.cs:line 87
at Microsoft.Dynamics.Framework.UI.Client.SaveValueInteractionExecutionStrategy.Initialize(IInteractionContext context, IDictionary`2 namedParameters) in s:\repo\src\platform\client\Shared\Prod.ClientFwk\Client\Interactions\ExecutionStrategies\SaveValueInteractionExecutionStrategy.cs:line 48
at Microsoft.Dynamics.Framework.UI.InteractionManager.<InvokeInteractions>d__8.MoveNext() in s:\repo\src\platform\client\Shared\Prod.ClientFwk\Interactions\InteractionManager.cs:line 105
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Dynamics.Framework.UI.WebBase.WebBaseInteractionManager.<InvokeInteractions>d__5.MoveNext() in s:\repo\src\platform\client\web\Prod.Client.WebBase\Interactions\WebBaseInteractionManager.cs:line 56
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Dynamics.Framework.UI.CultureAwaiter`1.GetResult() in s:\repo\src\platform\client\Shared\Prod.ClientFwk\Threading\Async\CultureAwaiter.cs:line 122
at Microsoft.Dynamics.Framework.UI.Web.WebInteractionManager.<InvokeInteractions>d__2.MoveNext() in s:\repo\src\platform\client\web\Prod.Client.Web\Interactions\WebInteractionManager.cs:line 45
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Dynamics.Framework.UI.CultureAwaiter`1.GetResult() in s:\repo\src\platform\client\Shared\Prod.ClientFwk\Threading\Async\CultureAwaiter.cs:line 122
at Microsoft.Dynamics.Framework.UI.Web.CallbackHandler.<HandleRequestCore>d__4.MoveNext() in s:\repo\src\platform\client\web\Prod.Client.Web\Callbacks\CallbackHandler.cs:line 195
Source: Microsoft.Dynamics.Framework.UI
Can you share the event log ?
Thank you for response. I have already tried it but does not improve situation.
try to clear the cache and make your default browser as Microsoft Edge.
IIS have already configured both parameters for Web Client and service tire and minimum is 6 Hours. But, Session still gets expired in 20-30 minutes.
you can see it in snapshots.
Hello Dipak,
The session timeout for the Web Client is controlled by settings in the Service Tier and in the Web Client configuration.
In the service tier, check ClientServicesIdleClientTimeout parameter (MaxValue = no timeout)
In the web client, configuration (navsetings.json file) check the parameter SessionTimeout,
You can make this change manually in Json file and restart the IIS.
or you can use the the command.
for example:
Set-NAVWebServerInstanceConfiguration -WebServerInstance BC140 -KeyName SessionTimeout -KeyValue "00:20:00".
Please remember that the above settings are used in conjunction with each other. A session will be closed based on the setting that has the shortest time period.
Let me know if you have any questions.
Regards,
Saurabh
Here, it is not scenario of Browser setting as it is default 2 Hours and user's session is timeout in 20-30 minutes.
Okay, I am not sure about BC but there is timeout settings in browsers.
André Arnaud de Cal...
294,101
Super User 2025 Season 1
Martin Dráb
232,866
Most Valuable Professional
nmaenpaa
101,158
Moderator