SOLVED Secondary Site Pending Yet Installed

[Jamin]

Hi,

I have an odd issue that I've not seen before, that I'm hoping someone can help with.

Yesterday I kicked off an installation of a secondary SCCM site from our CAS. This is something I've done a bunch of times before and it has worked flawlessly. However I noticed something odd when it apparently started the installation on the secondary server without there being anything returned in the "Show Install Status" window.

I've checked today, and as far as I can tell the secondary site has installed successfully, however the CAS is still showing the state as "Pending". The primary site that the secondary was installed from though is showing the site as "Site Active".

I've checked all the replication, and site logs, everything looks fine. There are no errors I can see anywhere to indicate why the CAS is unaware that the installation has started, let alone completed.

I was hoping someone here may be able to point me in the direction of some logs I may not know about, or has maybe seen a similar issue and can suggest some resolutions?

This is a Current Branch 1806 environment.

Thanks,

Ben.

 

[Prajwal Desai]

On the server where Secondary site is being installed, can you check ConfigMgrSetup.log located on the root of C:\ and also check hman.log to see if we can get some errors that could help us for troubleshooting.

 

[Jamin]

Thanks for the reply. Things have moved on a bit since I raised the ticket.

That site never moved off of pending, however by using the RCM.box and reinitializing the site replication groups I was able to get it to a point where I had the delete option. I tried to delete the site, however that hung on pending. Looking at the hotfix release notes, it seems that was a bug in 1806, so I have now also updated to the latest 1806 hotfix. The site was still stuck at deleting.

I thought I'd try reinstalling the secondary from the Primary (rather than the CAS), that installed and both the primary and the CAS said "site active", however the "servers and site system roles" section had duplicate entries for that server, and would error when I tried to delete one or view the properties. There were also duplicate distribution points on the primary and none on the CAS. So everything was still clearly not working.

The last thing I did yesterday was uninstall the secondary from the primary. This uninstalled OK, however the CAS still showed the secondary as installed. I then did a delete without uninstall from the CAS and 24 hours later it is still stuck deleting.

I have tried removing the information from the database. It disappears briefly, but then comes back, so I'm guessing that is because WMI is also out of sync?

I've attached the hman, rcmctrl and ConfigMgrSetup logs from the CAS. Hope that helps.

Thanks,

 

[Jamin]

I had another go at deleting the site from the database today by running:

Delete from SiteControl where siteCode='<sitecode>'
Delete from SiteControlNotification where siteCode='<sitecode>'
Delete from Sites where siteCode='<sitecode>'

Again, the entries deleted until I rebooted the CAS and then they all came back.

Running: Get-wmiobject -NameSpace "ROOT\SMS\site_CAS" -Class SMS_Site -Filter "sitecode = 'sitecode'"

Returns information about the site from WMI; so as far as I can tell it is the WMI information that needs clearing up, I just don't know how. For packages you can just run Get-WmiObject and pipe it to Remove-WmiObject; however that doesn't seem to work with the site query above.

Is there a way to delete the errant site info from WMI?

Thanks,

Ben.

 

[Jamin]

Ok, well, with some desperate Googling, and the use of the SQL Server Profiler I think I tracked down the issue. I had to run:

select * from SC_SiteDefinition where siteCode='<sitecode>'

At which point I saw entries for the same site, all with different sitenumbers. I made a note of the sitenumbers and then ran:

Delete from SC_SiteDefinition_Property where sitenumber = <sitenumber>
Delete from SC_SiteDefinition_PropertyList where sitenumber = <sitenumber>

for each of the site numbers returned from the first query.

I then ran:

Delete from SC_SiteDefinition where siteCode='<sitecode>'

With all that cleared out I could then run:

delete from statusmessages where machinename='<servername>'
delete from Summarizer_Components where MachineName like '%<servername>%'
delete from summarizer_sitesystem where sitesystem like '%<servername>%'
delete from statusmessageinsstrs where insstrvalue like '%<servername>%'
delete from sysreslist where servername='<servername>'
delete from sc_sysresuse where nalpath like '%<servername>%'
Delete from Sites_Data where siteCode='<sitecode>'
Delete from SysResList where siteCode='<sitecode>'
Delete from SiteControl where siteCode='<sitecode>'
Delete from SiteControlNotification where siteCode='<sitecode>'
Delete from Sites where siteCode='<sitecode>'
Delete from Sites_Data where siteCode='<sitecode>'
Delete from pkgservers where siteCode='<sitecode>'
Delete from pkgstatus where siteCode='<sitecode>'

After doing that, and restarting the server, I waited for half an hour, and the broken secondary site did not return into the site list on the CAS, as it had done before.

I then started a fresh install of the site, and it appears to have installed successfully, with both CAS and primary in sync.

Thanks.