web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics SL (Archived)

SL 2015 Application Server SQL Connection Leak

(0) ShareShare
ReportReport
Posted on by

I think this is probably a bug in the SL 2015 Application Server 9601000. I noticed today when investigating high SQL server utilization that Application Server seems to make connections and never close them. App Server had over 100 connections open. I closed down App Server and relaunched and every time it runs a job it creates a new SQL connection and never closes it. I am see this using Activity monitor in SSMS. While this doesn’t impact functionality I think that it would eventually impact resource utilization and possibly even performance.

*This post is locked for comments

I have the same question (0)
  • Community Member Profile Picture
    on at

    Following up after monitoring for a day. Using activity monitor in SSMS to monitor the SQL processes from my Application Server (reset 24 hours before) there are over 150 SQL processes associated with the Application Server Program. The vast majority of these SQL processes are

    select count(*) from usergrp (NOLOCK) where userid = 'UserName' AND groupid = 'ADMINISTRATORS'

    Looking a little further every SL login (MSDynamicsSL.exe) has the same process with a similar statement open.  I believe that this is actually a bug in the SL login procedure where a connection or recordset is failed to be closed. If you are trying to see this be aware MSDynamicsSL.exe doesn't set the application name so in Activity Monitor the application name is blank.  In a normal login this  an extra connection is left open until the menu is closed and has very little impact. But since Application Server logs in to impersonate the person who scheduled the job for every request this bug is amplified since the connections are not forced closed until Application Server is closed. My current solution is to reboot the Application Server twice a day to force close these connections and recover the resources.

    What is the impact is left alone? 150 connections per day @ 16KB SQL memory per connection over a week would be a 16MB memory leak on the SQL server itself.

    This article while dated suggests it might be even more than that.

    https://msdn.microsoft.com/en-us/library/aa337559(v=sql.105).aspx

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics SL (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans