This is perhaps due to a long period of inactivity in the web client. Nothing to worry about as long as the connection is restored once you click something in the web clint.
I also faced with above issue too.
WebClient raise error "The connection to the server was suspended" frequently (2-3 times within 1 min)
Event Viewer logged with: Long Running SQL Statement (highest metric was recorded up to 10 secs).
After 1 week tracking and tried dozen of solutions, I have idea to move to IE Browser (Because IE and NAV is developed under Microsoft - LOL ) instead of Chrome or FireFox. Thank to my Godness, everything was fine!
Same problem here (NAV 2017 build 30102). Role Centre opens fine, but trying to open any page results with connection suspended message immediately. Number of our users reporting this problem increases which may indicate it is related to some update. Luckily IE workaround works fine, but all of our users use Chrome so this is still a serious problem for us.
We discovered that using UnChrome application (https://unchrome.en.uptodown.com/windows/download) to delete unique user identifier solves the problem temporary, but when we restart Chrome connection gets suspended again.
Tried to change various site settings in Chrome but with no luck. We do have Idle Client Timeout set to 00:16:00. Don’t won’t to mess with NAV server or IIS settings for now because everything was ok for months before problem start to occur.
isabioncello, I had the same issue on the same build.
NTLM is enabled on the nav instance and NTLM is the only windows authentication provider on the subpage in IIS.
When I tried to monitor the traffic with fiddler, authentication to the web client was blocked and the browsers authentication dialog popped up. After authentication with Windows credentials I didn't get the "connection suspended" message.
This made me think I have an authentication issue.
I then enabled "Forms Authentication" on the subpage and did an iisreset. -> It seems to work now. I don't fully understand why tho. All authentications are enabled on my system.
I just applied latest CU 45 (build 30319) on stage environment and that seems to solve the problem. We will probably do the production update in couple of days...
Answers
best regards,
Thomas Barbut
Slawek
Dynamics NAV, MS SQL Server, Wherescape RED;
PRINCE2 Practitioner - License GR657010572SG
GDPR Certified Data Protection Officer - PECB License DPCDPO1025070-2018-03
Their is no error in event viewer.
Hi Slawek_Guzek ,
I receive msg while working and something just after login.
Thanks,
Evyn
WebClient raise error "The connection to the server was suspended" frequently (2-3 times within 1 min)
Event Viewer logged with: Long Running SQL Statement (highest metric was recorded up to 10 secs).
After 1 week tracking and tried dozen of solutions, I have idea to move to IE Browser (Because IE and NAV is developed under Microsoft - LOL ) instead of Chrome or FireFox. Thank to my Godness, everything was fine!
if someone has an idea please help me
thanks
We discovered that using UnChrome application (https://unchrome.en.uptodown.com/windows/download) to delete unique user identifier solves the problem temporary, but when we restart Chrome connection gets suspended again.
Tried to change various site settings in Chrome but with no luck. We do have Idle Client Timeout set to 00:16:00. Don’t won’t to mess with NAV server or IIS settings for now because everything was ok for months before problem start to occur.
NTLM is enabled on the nav instance and NTLM is the only windows authentication provider on the subpage in IIS.
When I tried to monitor the traffic with fiddler, authentication to the web client was blocked and the browsers authentication dialog popped up. After authentication with Windows credentials I didn't get the "connection suspended" message.
This made me think I have an authentication issue.
I then enabled "Forms Authentication" on the subpage and did an iisreset. -> It seems to work now. I don't fully understand why tho. All authentications are enabled on my system.
I just applied latest CU 45 (build 30319) on stage environment and that seems to solve the problem. We will probably do the production update in couple of days...