Microsoft KB Archive/267237

= SMS: Upgrading SMS Service Packs Resets Provider Connections to Default =

Article ID: 267237

Article Last Modified on 10/27/2006

-

APPLIES TO


 * Microsoft Systems Management Server 2.0 Service Pack 2
 * Microsoft Systems Management Server 2.0 Service Pack 3
 * Microsoft Systems Management Server 2.0 Service Pack 4

-



This article was previously published under Q267237



SYMPTOMS
If you have increased the number of Systems Management Server (SMS) computers at your site, you may have increased the number of connection accounts that the SMS provider is using. To make the change, you would have modified the Smsprov.mof file to increase the maximum SQL connections entry (MaxSQLConnections).

If you install SMS 2.0 Service Pack 2 (SP2), Service Pack 3 (SP3), or Service Pack 4 (SP4), this resets the number of connections from your custom value back to the default value of 60.



WORKAROUND
To work around the problem, increase the connections again by using the appropriate method, which is determined by whether or not you have Microsoft Systems Management Server, and Microsoft SQL Server on the same computer.

SMS and SQL on the Same Computer
If SMS and SQL are on the same computer, the SMS provider is located in this computer. Modify the following entry

MaxSQLConnections=60

in the Smsprov.mof file, which is located on SMS site server, in the SMS\bin\i386, or SMS\bin\Alpha folder.

SMS and SQL on Different Computers
 If SMS and SQL are not on the same computer, and the SMS provider is located in the SQL computer, the Smsprov.mof file is located in the :\SMSprov\MOFs\sitecode folder. Compile this file only, and not the Smsprov.mof file that is located in the SMS\Bin\I386 or SMS\Bin\Alpha folder on the SMS site server. If you do so, you may receive the following error message when you click Remote Control in Collections:

A database could not be found with the name supplied.

 Open the Smsprov.mof file with a text editor, and then locate the following lines:

/ *************************************

// SMS_ConfigData : SMS Provider Configuration data

// *************************************

[singleton]

class SMS_ConfigData

{

// Number of instances returned as a batch to CIMOM for query results

[Description(&quot;Undocumented - do not change&quot;)]

uint32 QueryInstanceBatchCount = 0;

// Max number of SQL connections allowed at one time by the provider

[Description(&quot;Undocumented - do not change&quot;)]

uint32 MaxSQLConnections = 60;

};

By default, the MaxSQLConnections setting is equal to 60. Change this to a higher number based on the number of SMS Administrator Console users. Even if you enter a higher number (Default connection=75) during the SMS installation, it does not update the number in this file. You have to update this manually.

 After you make this change, follow these steps to compile this file:  Go to the Mofcomp.exe file, which is located in the %SystemRoot%\System32\WBEM folder. Copy the Mofcomp.exe file to the folder that contains the Smsprov.mof file. Run the following command:

mofcomp smsprov.mof

The output from the command looks like this:

Microsoft (R) 32-bit MOF Compiler Version 1.10.698.0000

Copyright (C) Microsoft Corp. 1997. All rights reserved.

Parsing MOF file: smsprov.mof

MOF file has been successfully parsed

Storing data in the repository...

Done!

</ol> </li> Update the SQL 6.5, or SQL 7.0 user connection configuration based on step 3.

In SQL 6.5: <ol style="list-style-type: lower-alpha;"> Start SQL Enterprise Manager, right-click your SQL server, and then click Configure.</li> On the Configuration tab, locate the User Connections row, and then update the Current user connections number with a higher number.</li> Click Apply Now, then click OK.</li> Right-click your SQL server, and then click Stop.</li> Right-click your SQL server, and then click Start.</li></ol>

In SQL 7.0:

<ol style="list-style-type: lower-alpha;"> Start SQL Enterprise Manager, right-click your SQL server, and then click Properties.</li> Click the Connection tab.</li> Update the Maximum concurrent user connections number to a higher number, or 0 (0 = unlimited).</li> Click Apply, and then click Yes to stop, and restart SQL 7.0.</li></ol> </li></ol>

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Additional query words: prodsms Smsprov

Keywords: kbbug kbnofix KB267237

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.