This error here is quite tricky to solve, but I finally succeded with help from MicroSoft.
The error occur when you e.g. try to access the sender in the SCCM console from Central site at a primary child site.
The SmsAdminUI.log reports following error:
Description = “Unable to load site control file. “;
ErrorCode = 2160198400;
File = “c:\\qfe\\nts_sms_fre\\sms\\siteserver\\sdk_provider\\smsprov\\sspsitecontrolextractor.cpp”;
Line = 109;
ObjectInfo = “xxx”;
Operation = “ExecQuery”;
ParameterInfo = “SELECT * FROM SMS_SCI_Component WHERE SiteCode=’xxx’ AND FileType=2 AND ComponentName=’SMS_X25_RAS_SENDER'”;
ProviderName = “WinMgmt”;
StatusCode = 2147749889;
What to do, to solve this.
When I first discovered the error and began troubleshooting. I startet with a preinst.exe /synchchild from Central site and a preinst.exe /synchparrent from the primary child site to update the site control file – this did not help.
Next was to resinstall the sms provider – no luck still the same error.
Then I did a site reset after advise from Microsoft, still the same error.
The solution was to detach the Primary site from the hierarchy.
1. Delete the primary child site address from the central site
2. Delete the Central site address from the primary child site
3. Change the configuration at primary child to be “Central site” so it no longer report to the original central site.
4. WAIT till the “locks” are gone from the primary child site
5. Normally this will give the result that the primary child site is removed from the site hierarchy. BUT this was not the case for me.
6. So Next step was to dive into the database and run the “Delete FROM …” you see below (replace nnn with you sitecode og the primary child site)
This made the trouble site to dissapear from the Console..
Time to attach the sites again.
7. Recreate the addresses at both central and primary child site
8. Change primary child site to report to central site again
9. Make a new secure key exchange between the 2 sites. (preinst.exe /keyforchild and /keyforparent)
10. The primary child site turns up again at the console at central site and the problem with “”Unable to load site control file” is gone.
11. After a short while the objects at the primary child site are getting “locked” again.
12. Monitor Replmgr.log, Sender.log and despooler.log to see how central site are busy getting things back in order a
The DELETE FROM statements below is delivered by MS as a part of the trobleshooting, uses it at you own risk!
My advise is to open a support case at MS before you decide to alter the database!
DELETE FROM SysResList WHERE SiteCode=‘nnn’
DELETE FROM SiteBoundaryADSite WHERE SiteCode=‘nnn’
DELETE FROM SiteBoundaryIPSubnet WHERE SiteCode=‘nnn’
DELETE FROM SiteControl WHERE SiteCode=‘nnn’
DELETE FROM SiteControlNotification WHERE SiteCode=‘nnn’
DELETE FROM Sites WHERE SiteCode=‘nnn’
DELETE FROM Sites_DATA WHERESiteCode=‘nnn’
DELETE FROM SiteWork WHERE SiteCode=‘nnn’
DELETE FROM PkgServers WHERE sitecode=‘nnn’
DELETE FROM PkgStatus WHERE sitecode=‘nnn’