SOLVED 4909 Error in SCCM 2012

[Bryan]

Hi, We are constantly receiving this error. All of the permissions are in place, and the Schema is as it should be, there is nothing missing, the System Managent folder is in place and has the proper permissions for all accounts.

The Hosting Server is good on disk space and resources.

Our primary domain account for SCCM continues to get locked out...

On 4/15/2015 1:36:57 PM, component SMS_HIERARCHY_MANAGER on computer Server.domain.local reported: Configuration Manager could not locate the "System Management" container in Active Directory (Domain.local). Nor could it create a default container. This will prevent Site Component Manager and Hierarchy Manager from updating or adding any objects to Active Directory.

Possible cause: The site server's machine account might not have the correct rights to update active directory.
Solution: Either give the Service Account rights to update the domain's System Container, or manually create the "System Management" container in this domain's Active Directory system container, and give the site server computer account full rights to that container (and all children objects.)

I tried to correct the issue using the solution in the link, still to no avail.

http://prajwaldesai.com/task-sequence-failed-error-code-0x80070002/

Any assistance is greatly appreciated.

 

[Prajwal Desai]

@Bryan - Could you check sitecomp.log and see if there are any errors ?. You can post the log file here, I will check if there are any errors. In the sccm console under Administration > Hierarchy Configuration > Active Directory Forests, do you see the correct forest ? Check the properties of that forest & check if you are publishing with a specific account or with the default machines account? If you are publishing with a specific account, you need to give that account rights to the System Management container.

 

[Bryan]

@Bryan - Could you check sitecomp.log and see if there are any errors ?. You can post the log file here, I will check if there are any errors. In the sccm console under Administration > Hierarchy Configuration > Active Directory Forests, do you see the correct forest ? Check the properties of that forest & check if you are publishing with a specific account or with the default machines account? If you are publishing with a specific account, you need to give that account rights to the System Management container.

Hi Prajwal, thank you for your prompt answer. I do see the correct forrest and "use the computer account of the site server" is what the radial button is on.

 

[Prajwal Desai]

Okay that's good. So what does sitecomp.log tell ?. Any errors in the log file ?

 

[Bryan]

@Bryan - Could you check sitecomp.log and see if there are any errors ?. You can post the log file here, I will check if there are any errors. In the sccm console under Administration > Hierarchy Configuration > Active Directory Forests, do you see the correct forest ? Check the properties of that forest & check if you are publishing with a specific account or with the default machines account? If you are publishing with a specific account, you need to give that account rights to the System Management container.

Registry keys Operations Management\SMS Server Role\SMS Fallback Status Point already exists on server SCCMSERVER.Domain.LOCAL. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:14.852+240><thread=8056 (0x1F78)>
Writing SQL Alias registry values. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:14.858+240><thread=8056 (0x1F78)>
Installed FSP Configuration for SCCMSERVER.Domain.LOCAL. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:14.885+240><thread=8056 (0x1F78)>
Component SMS_FALLBACK_STATUS_POINT is running. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:14.892+240><thread=8056 (0x1F78)>
Writing component specific registry values. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:14.898+240><thread=8056 (0x1F78)>
Component SMS_HIERARCHY_MANAGER is running. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:14.905+240><thread=8056 (0x1F78)>
Component SMS_INBOX_MANAGER is running. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:14.913+240><thread=8056 (0x1F78)>
Component SMS_INBOX_MONITOR is running. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:14.920+240><thread=8056 (0x1F78)>
Component SMS_INVENTORY_DATA_LOADER is running. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:14.928+240><thread=8056 (0x1F78)>
Component SMS_INVENTORY_PROCESSOR is running. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:14.936+240><thread=8056 (0x1F78)>
Component SMS_LAN_SENDER is running. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:14.945+240><thread=8056 (0x1F78)>
Component SMS_LICENSE_MANAGER is running. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:14.954+240><thread=8056 (0x1F78)>
Component SMS_MIGRATION_MANAGER is running. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:14.964+240><thread=8056 (0x1F78)>
Writing component specific registry values. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:14.972+240><thread=8056 (0x1F78)>
Registry keys Operations Management\SMS Server Role\SMS Management Point already exists on server SCCMSERVER.Domain.LOCAL. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:14.980+240><thread=8056 (0x1F78)>
Writing SQL Alias registry values. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:14.989+240><thread=8056 (0x1F78)>
Component SMS_MP_CONTROL_MANAGER is running. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:15.002+240><thread=8056 (0x1F78)>
Component SMS_MP_FILE_DISPATCH_MANAGER is running. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:15.012+240><thread=8056 (0x1F78)>
Component SMS_NOTIFICATION_MANAGER is running. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:15.022+240><thread=8056 (0x1F78)>
Writing component specific registry values. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:15.030+240><thread=8056 (0x1F78)>
Installed BGB Server Configuration for SCCMSERVER.Domain.LOCAL. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:15.044+240><thread=8056 (0x1F78)>
Component SMS_NOTIFICATION_SERVER is running. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:15.054+240><thread=8056 (0x1F78)>
Component SMS_OBJECT_REPLICATION_MANAGER is running. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:15.064+240><thread=8056 (0x1F78)>
Component SMS_OFFER_MANAGER is running. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:15.074+240><thread=8056 (0x1F78)>
Component SMS_OFFER_STATUS_SUMMARIZER is running. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:15.085+240><thread=8056 (0x1F78)>
Component SMS_OUTBOX_MONITOR is running. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:15.096+240><thread=8056 (0x1F78)>
Component SMS_PACKAGE_TRANSFER_MANAGER is running. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:15.106+240><thread=8056 (0x1F78)>
Component SMS_POLICY_PROVIDER is running. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:15.117+240><thread=8056 (0x1F78)>
Writing component specific registry values. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:15.127+240><thread=8056 (0x1F78)>
Registry keys Operations Management\SMS Server Role\SMS Portal Web Site already exists on server SCCMSERVER.Domain.LOCAL. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:15.138+240><thread=8056 (0x1F78)>
Writing SQL Alias registry values. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:15.148+240><thread=8056 (0x1F78)>
Updating PORTALWEB on SCCMSERVER.Domain.LOCAL $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:15.162+240><thread=8056 (0x1F78)>
Updated PORTALWEB Configuration for SCCMSERVER.Domain.LOCAL. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:15.175+240><thread=8056 (0x1F78)>
Installing Security settings on site system [SCCMSERVER.Domain.LOCAL]... $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:15.185+240><thread=8056 (0x1F78)>
Security settings are up to date for SCCMSERVER.Domain.LOCAL. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:15.197+240><thread=8056 (0x1F78)>
Component SMS_PORTALWEB_CONTROL_MANAGER is running. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:15.208+240><thread=8056 (0x1F78)>
Component SMS_REPLICATION_CONFIGURATION_MONITOR is running. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:15.220+240><thread=8056 (0x1F78)>
Component SMS_REPLICATION_MANAGER is running. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:15.232+240><thread=8056 (0x1F78)>
Component SMS_RULE_ENGINE is running. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:15.244+240><thread=8056 (0x1F78)>
Component SMS_SCHEDULER is running. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:15.256+240><thread=8056 (0x1F78)>
Component SMS_SITE_CONTROL_MANAGER is running. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:15.269+240><thread=8056 (0x1F78)>
Writing component specific registry values. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:15.280+240><thread=8056 (0x1F78)>
Reading IsClustered property from SQL server. $$<SMS_SITE_COMPONENT_MANAGER><04-13-2015 01:34:15.306+240><thread=8056 (0x1F78)>
Read IsClustered property from SQL server. $

 

[Bryan]

I got this when attempting to add a PC to SCCM

• Name: PCNAME
• MAC Address:
• SMBIOS GUID:
• Source Computer:
• Choose Target Collection: Laptop Image Build
Errors
The SMS Provider reported an error.
ConfigMgr Error Object:
instance of SMS_ExtendedStatus
{
Description = "Unable to save changes";
ErrorCode = 2152205056;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspsite.cpp";
Line = 1346;
Operation = "ExecMethod";
ParameterInfo = "SMS_Site";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
};

 

[Prajwal Desai]

ErrorCode = 2152205056 - This error is seen when you have issues with the drivers being imported to boot image. I believe you have imported more than one driver to boot image out of which one is causing the issue. On of possible solutions is to import driver one by one, and see which one is causing the problem. It is a long process but still it helps.To ensure that the driver can be properly added and injected into a WinPE Boot Image, make sure that all files and subdirectories in the same location as the INF file are copied over to the Driver Source location.

Secondly, are you trying to import a computer using MAC address, check if there is already an existing record that has that same MAC address.

This issue might have been fixed in SP1 / R2. Which version of CM are you using ?

You could also try the following steps :-

1) Make a note of all Driver Packages and Boot Images that the affected driver have been added to
2) Delete the affected driver from the Driver node in the SCCM 2012 Admin Console
3) Re-download the driver from the OEM manufacturer
4) If necessary, extract the driver from OEM manufacturer package
5) From the extracted files, locate the directory where the INF file for the driver is stored
6) Copy all of the files and sub directories in the directory where the INF file is located to the location where the customer normally stores driver sources
7) Re-import the driver from the location in Step 6
8) Add the driver back to all Boot Images and Driver Packages removed in Step 2

 

[Bryan]

ErrorCode = 2152205056 - This error is seen when you have issues with the drivers being imported to boot image. I believe you have imported more than one driver to boot image out of which one is causing the issue. On of possible solutions is to import driver one by one, and see which one is causing the problem. It is a long process but still it helps.To ensure that the driver can be properly added and injected into a WinPE Boot Image, make sure that all files and subdirectories in the same location as the INF file are copied over to the Driver Source location.

Secondly, are you trying to import a computer using MAC address, check if there is already an existing record that has that same MAC address.

This issue might have been fixed in SP1 / R2. Which version of CM are you using ?

You could also try the following steps :-

1) Make a note of all Driver Packages and Boot Images that the affected driver have been added to
2) Delete the affected driver from the Driver node in the SCCM 2012 Admin Console
3) Re-download the driver from the OEM manufacturer
4) If necessary, extract the driver from OEM manufacturer package
5) From the extracted files, locate the directory where the INF file for the driver is stored
6) Copy all of the files and sub directories in the directory where the INF file is located to the location where the customer normally stores driver sources
7) Re-import the driver from the location in Step 6
8) Add the driver back to all Boot Images and Driver Packages removed in Step 2

OK, Deleted all references and re added, this time no problems.

 

[Prajwal Desai]

So did that work ?. I think you have asked 2 issues in one thread, am i correct ?

 

[Bryan]

Yes, sorry, I thought it was related to the original issue. Fortunately it wasn't. But I do continue to have the issue with the first item.

 

[Prajwal Desai]

For the first issue, could you check if site server computer account has full rights to that container (system management).
http://prajwaldesai.com/installing-prerequisites-for-configuration-manager-2012-r2/

 

[Bryan]

For the first issue, could you check if site server computer account has full rights to that container (system management).
http://prajwaldesai.com/installing-prerequisites-for-configuration-manager-2012-r2/

We have everything in place as far as the schema is concerned, we are not sure why, but it is no longer an issue at this time. The administrative account is no longer locking out or displaying any bad password count on and of our DC's. My assumption that restarting the hosting SCCM2012 box is what did the trick.

 

[Prajwal Desai]

Great. Nice to know that your issues are fixed. I will mark this thread as solved.