mibuso.com
Home› NAV Three Tier

Warning event on Dynamics Nav 2017 server.

novavenda@hotmail.comnovavenda@hotmail.com Member Posts: 5
in NAV Three Tier
Hi!!!

We are now working with Microsoft Dynamics nav 2017 and in one server I have a lot of warning messages in Event viewer,
and I can not find information about it, this is the message:

Server instance: XXXXX
Category: Sql
ClientSessionId: 00000000-0000-0000-0000-000000000000
ClientActivityId: 00000000-0000-0000-0000-000000000000
ServerSessionUniqueId: 825880d5-27d3-4a4f-8f71-d50349968634
ServerActivityId: 00452ebe-3b44-4270-ac68-d81026b6af4c
EventTime: 03/08/2017 08:30:30
Message <ii>NavSqlQueryCommand is recreated due to the changed connection.</ii>
ProcessId: 26008
Tag: 00000BS
ThreadId: 253
CounterInformation:

The event viewer may contain more than 200 events every second!!!
This Navision instance is used to call web services and return data asychronously, suddenly the cpu of this server shoots to the top (100% usage) and the instance needs to be restarted.


Thanks a lot for your help.

Answers

  • clydeclyde Member Posts: 2
    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.
  • ArmondsArmonds Member Posts: 66
    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?
  • gmorkengmorken Member Posts: 38
    armonds, did you ever get this resolved?
  • ArmondsArmonds Member Posts: 66
    Nop, but I have suspicion that it could be some how related with virtualization.
  • gmorkengmorken Member Posts: 38
    edited 2017-10-02
    Are you on Windows Server 2016? Azure or on -premise? SQL-server 2016?
  • ArmondsArmonds Member Posts: 66
    On-premise, Win 2012R2, SQL 2014
  • novavenda@hotmail.comnovavenda@hotmail.com Member Posts: 5
    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.
  • malapheevmalapheev Member Posts: 1
    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)
  • novavenda@hotmail.comnovavenda@hotmail.com Member Posts: 5
    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.
  • novavenda@hotmail.comnovavenda@hotmail.com Member Posts: 5
    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.
  • RemkoDRemkoD Member Posts: 100
    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.
  • soetiesoetie Member Posts: 61
    Hi,

    is this just a bug? Or does it also causes problems?
  • RemkoDRemkoD Member Posts: 100
    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.

  • MBrodie1979MBrodie1979 Member Posts: 21
    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.
  • Rikt-ItRikt-It Member Posts: 37
    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
Sign In or Register to comment.