| Message ID | Severity | Message |
|---|---|---|
|
3300 |
Error |
Site %1 (%2) is trying to report to a site that already reports to site %1. This configuration is illegal because it creates a “loop” in the site hierarchy. Solution: Configure the site hierarchy properly; it must not contain loops. See the SMS documentation for information on how to create a proper site hierarchy. |
|
3301 |
Error |
Site %1 (%2) has the same site code as another site. Possible cause: SMS Hierarchy Manager has detected that a child site has the same site code as this site or another child site. Solution: Each site must have a unique site code. Deinstall the child site and reinstall it using a unique site code. |
|
3302 |
Error |
The parent site for this site cannot be changed from site %1 (%2). Possible cause: You attempted to configure this site to report to a different parent site, but you attempted this using an SMS Administrator console that was not connected to this site’s database. Solution: To change configure this site to report to a different parent site, use an SMS Administrator console that is connected to the site’s database. If this site is a secondary site, use SMS Setup to configure this site to report to a different parent site. |
|
3303 |
Error |
SMS Hierarchy Manager cannot connect to the SMS site database. Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs. |
|
3304 |
Error |
SMS Hierarchy Manager cannot save site information to the SMS site database for site %1. Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs. |
|
3305 |
Error |
SMS Hierarchy Manager detected that site code %1 is already in use by existing site %2. Possible cause: Site %3 is using the same site code as another site. Solution: Each site must have a unique site code. Deinstall one of these sites and reinstall it using a unique site code. |
|
3306 |
Informational |
SMS Hierarchy Manager successfully processed %1, which represented serial number %4 of the site control file for site %2 (%3). If this site is a primary site, SMS Hierarchy Manager stored this site control file in the SMS site database. If this site reports to a parent site, SMS Hierarchy Manager instructed SMS Replication Manager to replicate this file to the parent site at high priority. |
|
3307 |
Informational |
SMS Hierarchy Manager detected that a change was requested by this site to the configuration of site %1. SMS Hierarchy Manager created a delta site control file for this request. If this site is site %1, SMS Hierarchy Manager submitted this file to SMS Site Control Manager at this site. If site %1 is a child site, SMS Hierarchy Manager instructed SMS Replication Manager to deliver the file to SMS Site Control Manager at site %1 at high priority. |
|
3308 |
Error |
SMS Hierarchy Manager cannot reinstall the SMS Site Component Manager under the new Service account and password. Possible cause: The Service account and password are not valid. Solution: Specify a valid Service account and password using the SMS Administrator console. Possible cause: The account does not have Administrator permissions and “Log on as a service” rights. Solution: Grant the appropriate permissions and rights using the Windows NT User Manager. |
|
3309 |
Informational |
SMS Hierarchy Manager reinstalled SMS Site Component Manager using the new Service account and password. SMS Site Component Manager will now reinstall all of the other server components at this site. |
|
3310 |
Informational |
SMS Hierarchy Manager has initiated remote installation of secondary site %1. To track the progress of this operation, you should also monitor the messages reported by the SMS Sender components. |
|
3311 |
Informational |
SMS Hierarchy Manager has initiated remote upgrade of secondary site %1. To track the progress of this operation, you should also monitor the messages reported by the SMS Sender components. |
|
3312 |
Informational |
SMS Hierarchy Manager has initiated remote deinstallation of secondary site %1. To track the progress of this operation, you should also monitor the messages reported by the SMS Sender components. |