Microsoft KB Archive/886629

= A site upgrade from SMS 2.0 to SMS 2003 may not succeed if SQL replication is configured on the site database in Systems Management Server 2003 =

Article ID: 886629

Article Last Modified on 5/21/2007

-

APPLIES TO


 * Microsoft Systems Management Server 2003

-





SYMPTOMS
When you try to upgrade a site from Microsoft Systems Management Server (SMS) 2.0 to SMS 2003, you may experience the following symptoms, and the upgrade may not succeed:   Entries that are similar to the following are logged in the :\Sms\Logs\Hman.Log file on the site's parent site server: Processing site control file: Site  File  :\SMS\inboxes\hman.box\ .CT2

SMS_HIERARCHY_MANAGER  Update the Sites table: Site=  Parent=

SMS_HIERARCHY_MANAGER  *** insert SiteControl (SiteCode, TypeFlag, SerialNumber, BinaryData) values (&quot; &quot;, 1, 876, 0x0)

SMS_HIERARCHY_MANAGER  *** [42000][7139][Microsoft][ODBC SQL Server Driver][SQL Server]

Length of text, ntext, or image data to be replicated exceeds configured maximum.

SMS_HIERARCHY_MANAGER  *** insert SiteControl (SiteCode, TypeFlag, SerialNumber, BinaryData) values (&quot; &quot;, 1, 876, 0x0)

SMS_HIERARCHY_MANAGER  *** [01000][3621][Microsoft][ODBC SQL Server Driver][SQL Server]The statement has been terminated.

SMS_HIERARCHY_MANAGER  You can start the Site Component Manager service on the SMS site. However, the service stops soon after you start it, and the service does not restart. When you examine the version of SMS that is installed on the site, the version is reported as SMS 2.0. However, the version should be SMS 2003. The Publish identity data to Active Directory box is no longer selected. If you select the box again, the Set Security Mode dialog box appears and prompts you to set the security mode to Advanced.



CAUSE
This issue may occur if all the following conditions are true:
 * You have completed the SMS 2003 upgrade of a central site server.
 * Replication is enabled on the SMS 2003 central site database after you complete the upgrade of the central site server.
 * After you enable replication on the SMS 2003 central site database, you apply the SMS 2003 upgrade to an SMS 2.0 primary site or to an SMS 2.0 child site, and the site reports to the SMS 2003 central site.
 * The Microsoft SQL Server MAX TEXT REPL SIZE option of the central site database is set to a value that is too low to process the .ct2 site control file of the site where you apply the SMS 2003 upgrade.

Note The site control (.ct2) file is sent to the central site from the site where you apply the SMS 2003 upgrade.



WORKAROUND
To work around this issue, follow these steps:  Increase the value of the MAX TEXT REPL SIZE option, and remove from the site control table the records that were created by the SMS upgrade that did not succeed. To do this, follow these steps: <ol style="list-style-type: lower-alpha;"> Click Start, point to Programs, point to Microsoft SQL Server, click Query Analyzer, and then log on to the to the computer that is running Microsoft SQL Server that hosts the SMS 2.0 site database.</li> Type the following query:

sp_configure 'max text repl size' ,

GO

reconfigure with override

GO

delete from sitecontrol where typeflag = 2

GO

Note  is the MAX TEXT REPL SIZE that you want to set.</li> Click Query, and then click Execute.</li> Exit SQL Query Analyzer.</li></ol> </li> Restore the SiteCtrl.ct0 file from the most recent backup that was performed before the upgrade to SMS 2003. The SiteCtrl.ct0 file is located in the :\Sms\Inboxes\Sitectrl.box folder on the site server.</li> Apply the SMS 2003 site upgrade to the SMS 2.0 site again.</li></ol>

<div class="moreinformation_section">

MORE INFORMATION
The MAX TEXT REPL SIZE option specifies the maximum byte size of text and image data that can be added to a replicated column in a single INSERT, UPDATE, WRITETEXT, or UPDATETEXT statement. When the SMS site database has replication enabled, the upgrade may not succeed if the MAX TEXT REPL SIZE option has a value that is too low for the SMS upgrade to complete.

We strongly recommend that you test your SMS site database upgrade before you upgrade your production SMS site. If your live SMS site database upgrade is not completed, your SMS site may become inoperable.

Your database upgrade is more likely to require manual modification before a successful upgrade if one or more of the following conditions are true:
 * You have enabled replication on the site database.
 * You have modified the SMS 2.0 hardware inventory .mof file.
 * You have modified the SMS site database:
 * You have added triggers.
 * You have added columns in tables.
 * You have added stored procedures.
 * You use Management Information Format files (MIFs) that contain identification and architecture information (IDMIFS) or that do not contain identification and architecture information (NOIDMIFS) in your SMS 2.0 hierarchy.
 * You have installed third-party tools or internal tools that modify the SMS database.

Important The Setup.exe /TestDBUpgrade test is a destructive process. Do not run the Setup.exe /TestDBUpgrade test on a production SMS site database.

<div class="references_section">