Home

How to fix SCCM error 0x1 1?

Alton Alexander
By Alton AlexanderUpdated on June 4th, 2022

The SCCM 0x1 1 error code indicates that there is a problem with the way that the System Center Configuration Manager (SCCM) is configured. This can be caused by a number of factors, including incorrect settings in the SCCM console or a corrupt SCCM database. In either case, the result is that SCCM is unable to communicate with the site server or clients, which can prevent it from managing devices and deploying software updates.

One potential way to fix the SCCM 0x1 1 error is to reset the SCCM site server. This can be done by running the "Reset Site Server" task in the SCCM console. This will delete all data on the site server, so it should only be used as a last resort. If the reset is successful, the SCCM 0x1 1 error should be resolved.

Users typically search for a solution by asking about:

  • the software change returned error code 0x1 1
  • sccm 0x1 1

1. Restart the SMS_EXECUTIVE service

To restart the SMS_EXECUTIVE service in order to fix SCCM 0x1:

  1. Log on to the server where the SMS_EXECUTIVE service is installed.
  2. In the Server Manager console, open the Services console.
  3. In the Services console, double-click the SMS_EXECUTIVE service.
  4. In the Startup/Shutdown section, click Restart.
  5. In the dialog box that appears, click OK.

2. Stop and start the SMS_SITE_COMPONENT_MANAGER service

To Stop the SMS_SITE_COMPONENT_MANAGER service, use the following command: sc stop SMS_SITE_COMPONENT_MANAGER To start the SMS_SITE_COMPONENT_MANAGER service, use the following command: sc start SMS_SITE_COMPONENT_MANAGER

3. Delete the site control file and recreate it

  1. Navigate to the <sysvol>\Microsoft\Windows\SiteControl folder.
  2. Locate the sitecontrol.mdb file.
  3. Right-click on the file and select Delete.
  4. Click Yes when prompted to confirm the deletion.
  5. Follow the instructions in the confirmation message to create a new site control file.

Still not working? maybe try one of these options:

  1. Recreate the site system relationship
  2. Delete the site and recreate it
  3. Reinstall the Configuration Manager site