SMS: SMSExec Components Report SQL Error Messages Due to a Lack of Free SQL Connections

ID: Q246785

The information in this article applies to:

Microsoft Systems Management Server versions 2.0, 2.0 SP1

SYMPTOMS

SMS Executive Service components (threads) run for a short period of time and then begin to report SQL errors if they are unable to establish an SQL connection. One of the following error messages may be logged:

General SQL Server error: Check messages from the SQL Server.

CSqlCache::InternalGetConnection() - Waiting for SQL Connection (WaitForSingleObject())

RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Systems Management Server service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp

The English-language version of this fix should have the following file attributes or later:


   Date      Time    Version          Size    File name   Platform
   ----------------------------------------------------------------
   12/15/99  6:31pm  2.00.1380.1090   169,872 Ddm.dll     i386
   12/15/99  6:31pm  2.00.1380.1090   255,248 Ddm.dll     Alpha

NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.

NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:

Q154871 Determining If You Are Eligible for No-Charge Technical Support

To work around this issue, stop and restart the SMS Executive service. This should free all SQL connections being used by the SMS Executive threads. After you restart the SMS Executive service, the threads should be able to connect to SQL.

STATUS

Microsoft has confirmed this to be a problem in Systems Management Server version 2.0.

MORE INFORMATION

To install the hotfix, use the appropriate method.

Using the Hotfix Installer

NOTE: This method only works for I386-based computers.

Copy the hotfix folder structure to a share on your network. Q246785.exe is a Microsoft Windows Installer file that updates specific files on your site server.

Log on to your site server using an account with administrative privileges.

On the site server, close the Systems Management Server Administrator console.

Run Q246785.exe and follow the directions in the wizard. You can run the file in Quiet mode by using the /s switch.

Manual Installation

Close the Systems Management Server Administrator console and stop the Systems Management Server Site Component Manager and Systems Management Server Executive services. If the SMS_SITE_BACKUP service is running, stop that as well.

Replace the Ddm.dll file in the <sms_root_directory>\bin\<platform> folder with the version obtained from the hotfix.

Restart the Systems Management Server Site Component Manager and Systems Management Server Executive services.

Additional query words: prodsms sql connection

Keywords : kbnetwork kbDatabase kbSMS200 kbSMS200bug
Version : winnt:2.0,2.0 SP1
Platform : winnt
Issue type : kbbug