Warning event on Dynamics Nav 2017 server.

Answers

• Options

  clyde Member Posts: 2

  2017-04-05

  One of my customers was getting this. They had recently upgraded to 2017. Some clients were still connecting to a server instance that had been setup for 2013 r2. We pointed the clients to a new 2017 server instance and stopped the old one. Have not seen the error since.

  0
• Options

  Armonds Member Posts: 66

  2017-04-24

  Hello.
  
  We recently started to get the same warning + one more on NAV server:
  
  Category: Sql
  ClientSessionId: 00000000-0000-0000-0000-000000000000
  ClientActivityId: 00000000-0000-0000-0000-000000000000
  ServerSessionUniqueId: 40e209d9-dc44-428e-a2c4-16b0092a64ce
  ServerActivityId: 964d77c7-56eb-4b59-8364-4033262106e1
  EventTime: 04/24/2017 05:25:15
  Message <ii>NavSqlQueryCommand is recreated due to the changed connection.</ii>
  ProcessId: 37848
  Tag: 00000BS
  ThreadId: 38
  CounterInformation:
  
  
  Category: Runtime
  ClientSessionId: 59f01de8-e464-401e-9dd8-a524e667bf15
  ClientActivityId: f69eb374-7f92-4f10-8aa9-8af52026bbca
  ServerSessionUniqueId: 00000000-0000-0000-0000-000000000000
  ServerActivityId: 00000000-0000-0000-0000-000000000000
  EventTime: 04/24/2017 04:38:21
  Message <ii>Dispose SqlConnectionScope in a different thread, IsDisposed=False, sessionId=4724, database=XXX, threadname=, ownerThread=34, stacktrace=</ii>
  ProcessId: 37848
  Tag: 00000AD
  ThreadId: 25
  CounterInformation:
  
  On SQL server nor in SQL logs, nor Event logs I didn't noticed any suspicious entries. Maybe some one could please point out where to look to or what causes this warnings?

  0
• Options

  gmorken Member Posts: 38

  2017-09-29

  armonds, did you ever get this resolved?

  0
• Options

  Armonds Member Posts: 66

  2017-09-29

  Nop, but I have suspicion that it could be some how related with virtualization.

  0
• Options

  gmorken Member Posts: 38

  2017-10-02 edited 2017-10-02

  Are you on Windows Server 2016? Azure or on -premise? SQL-server 2016?

  0
• Options

  Armonds Member Posts: 66

  2017-10-02

  On-premise, Win 2012R2, SQL 2014

  0
• Options

  novavenda@hotmail.com Member Posts: 5

  2017-10-02

  Hi, good morning.
  
  My scenario is the next:
  
  A windows Hyper-V failover cluster with 2 nodes. Inside the cluster a virual server with windows server 2012 r2 standard to manage navision instances another server for the sql Server (sql server 2016 enterprise edition).
  
  All i installed on our Dell PowerEdge servers.
  
  I am very boring about this situation I must restart everyday this instance :-(
  
  Thank you very much for your help.

  0
• Options

  malapheev Member Posts: 1

  2017-10-02

  Hi,
  
  Which CU version are you running?
  Are you doing any OData calls to the server, the issue can be related parallel OData calls, which was fixed in out the latest updates.
  
  /Aleksandr Malafeev (MSFT)

  Aleksandr Malafeev (MSFT)

  0
• Options

  novavenda@hotmail.com Member Posts: 5

  2017-10-02

  Hi malaphevv
  
  I do not know the cumulative update we are running but the Microsoft Dynamics nav version is 10.0.13682.0 which was installed at the end of 2016.
  
  And yes, you are absolutely right, we use very intensive parallel Odata calls.
  
  I think we will wait for the 2018 version because it will be available very soon.
  
  Thank you very much for your help.

  0
• Options

  novavenda@hotmail.com Member Posts: 5

  2017-10-20

  Hello, good morning from Catalonia !!!
  
  This message is just to thank you and inform us about our evolution at Navision Nav 2017
  
  We have installed cumulative update 11 (it takes only a few minutes) and our problems on the instance are solved.
  
  We do not need to restart the instance manually at random hours every day for massive use of the CPU.
  
  In our company we are very happy for your help, both users who do not have to stop their work because the instance does not work or from the computer section.
  
  Thank you again and have a very good day.

  1
• Options

  RemkoD Member Posts: 100

  2018-03-02

  We've had a call with Microsoft regarding these warnings.
  
  The warning "Dispose SqlConnectionScope” and “NavSqlQueryCommand is recreated” often registered in the Windows Event Viewer Application logbook are removed in NAV2017 CU8 (17501)
  

  218030 Remove unnecessary trace events for disposing SqlConnectionScope from a different thread.

  0
• Options

  soetie Member Posts: 61

  2018-07-13

  Hi,
  
  is this just a bug? Or does it also causes problems?

  0
• Options

  RemkoD Member Posts: 100

  2018-07-14

  soetie wrote: »

  is this just a bug? Or does it also causes problems?

  
  I would call it a misplaced feature. It's not really a bug or causing problems besides flooding your event viewer application log. There are however quite a lot (unrelated to this) issues resolved in the NAV 2017 platform. So upgrading anyway might not be a bad idea.
  
  

  0
• Options

  MBrodie1979 Member Posts: 21

  2018-09-17

  Did anyone ever find the cause to this? Were running AUS version NAV 2017 Build 18609 and when this error floods the log the system freezes in RTC and the object designer. Sometimes a restart of services is required.

  0
• Options

  Rikt-It Member Posts: 37

  2019-03-25

  It's fixed in Nav2017-Cu24...
  
  
  https://support.microsoft.com/sv-se/help/4470114/cumulative-update-24-for-microsoft-dynamics-nav-2017-build-25480
  

  Regards
  Christer in Stockholm, Sweden

  0