hollisorama

I rebooted both the site server and db server multiple times while troubleshooting. This has been happening since December. The event viewer has no error messages. Site components are good except for from inventory dataloader size and delta issues that I'm trying to clean up.

My site backup task is running. The logs show both the Site components and SQL DB backups completing successfully. It seems like the notification messages never get back to the site server. Site Server smsbkup.log LogEvent(): Successfully logged Event to NT Event Log. (4 - 48 - 1,073,746,880) SMS_SITE_BACKUP 1/17/2015 7:51:46 PM 5200 (0x1450) FinalSnapshotPath = \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\INBOXES\. SMS_SITE_BACKUP 1/17/2015 7:51:46 PM 5200 (0x1450) Backup Succeeded for Component - SI4Backup\SiteServer\SMSServer\inboxes. SMS_SITE_BACKUP 1/17/2015 7:53:40 PM 5200 (0x1450) FinalSnapshotPath = \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\LOGS\. SMS_SITE_BACKUP 1/17/2015 7:53:40 PM 5200 (0x1450) Backup Succeeded for Component - SI4Backup\SiteServer\SMSServer\Logs. SMS_SITE_BACKUP 1/17/2015 7:53:48 PM 5200 (0x1450) FinalSnapshotPath = \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\DATA\. SMS_SITE_BACKUP 1/17/2015 7:53:48 PM 5200 (0x1450) Backup Succeeded for Component - SI4Backup\SiteServer\SMSServer\data. SMS_SITE_BACKUP 1/17/2015 7:53:48 PM 5200 (0x1450) FinalSnapshotPath = \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\SRVACCT\. SMS_SITE_BACKUP 1/17/2015 7:53:48 PM 5200 (0x1450) Backup Succeeded for Component - SI4Backup\SiteServer\SMSServer\srvacct. SMS_SITE_BACKUP 1/17/2015 7:53:48 PM 5200 (0x1450) FinalSnapshotPath = \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\Program Files\Microsoft Configuration Manager\install.map. SMS_SITE_BACKUP 1/17/2015 7:53:48 PM 5200 (0x1450) Backup Succeeded for Component - SI4Backup\SiteServer\SMSServer. SMS_SITE_BACKUP 1/17/2015 7:53:48 PM 5200 (0x1450) FinalSnapshotPath = \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\Program Files\Microsoft Configuration Manager\BackupTemp\SMSbkSiteRegSMS.dat. SMS_SITE_BACKUP 1/17/2015 7:53:48 PM 5200 (0x1450) Backup Succeeded for Component - SI4Backup\SiteServer\SMSbkSiteRegSMS.dat. SMS_SITE_BACKUP 1/17/2015 7:53:48 PM 5200 (0x1450) Waiting On SQL Backup for component sccmsi4 to complete... SMS_SITE_BACKUP 1/17/2015 7:53:48 PM 5200 (0x1450) Sleeping for 30 seconds... SMS_SITE_BACKUP 1/17/2015 7:53:49 PM 5200 (0x1450) Sleeping for 30 seconds... SMS_SITE_BACKUP 1/17/2015 7:54:19 PM 5200 (0x1450) Database Server smsbkup.log Updating the status to [snapshot done]. SMS_SITE_SQL_BACKUP_P-SC-SCM04.DOMAIN.NET 1/17/2015 7:50:50 PM 2420 (0x0974) Starting the backup complete phase. SMS_SITE_SQL_BACKUP_P-SC-SCM04.DOMAIN.NET 1/17/2015 7:50:50 PM 2420 (0x0974) Backup Succeeded for Component - SCCMSI4. SMS_SITE_SQL_BACKUP_P-SC-SCM04.DOMAIN.NET 1/17/2015 7:52:42 PM 2420 (0x0974) Updating the database status to [sCCMSI4:Succeeded;]. SMS_SITE_SQL_BACKUP_P-SC-SCM04.DOMAIN.NET 1/17/2015 7:52:42 PM 2420 (0x0974) Successfully created the backup metadata file - E:\Site_Backup\SI4Backup\SiteDBServer\\SQLBackupDocument.xml SMS_SITE_SQL_BACKUP_P-SC-SCM04.DOMAIN.NET 1/17/2015 7:52:42 PM 2420 (0x0974) Info: Starting asynchronous BackupComplete... SMS_SITE_SQL_BACKUP_P-SC-SCM04.DOMAIN.NET 1/17/2015 7:52:42 PM 2420 (0x0974) Info: Asynchronous BackupComplete finished. SMS_SITE_SQL_BACKUP_P-SC-SCM04.DOMAIN.NET 1/17/2015 7:52:43 PM 2420 (0x0974) After BackupComplete SQL Writer status = STABLE. SMS_SITE_SQL_BACKUP_P-SC-SCM04.DOMAIN.NET 1/17/2015 7:52:43 PM 2420 (0x0974) Updating the status to [backup completed]. SMS_SITE_SQL_BACKUP_P-SC-SCM04.SDOMAINNET 1/17/2015 7:52:43 PM 2420 (0x0974) SQL backup completed - Sat Jan 17 19:52:43 2015 SMS_SITE_SQL_BACKUP_P-SC-SCM04.DOMAIN.NET 1/17/2015 7:52:43 PM 2420 (0x0974) Waiting for the Event Notification... SMS_SITE_SQL_BACKUP_P-SC-SCM04.DOMAIN.NET 1/17/2015 7:52:43 PM 2420 (0x0974) I'm not sure where to go on this. I've tried a bunch of things like permissions, local vs., remote backup target.

The root is staying the same. Thanks for you response.

Thanks Ath3na. I had seen that site too. It seemed straight forward. I just wondered if anyone had done it before and if everything went smooth or if there were any catches. I was concerned that if the certificates got messed up that my clients would not download policy anymore.

From what you describe, I'm having the same issue in my lab environment. My production environment is fine. I thought about building a fresh 2012 R2 lab environment and migrating all my systems to it. Has anyone resolved this?

I have a site with 2 management points running ConfigMgr 2012 SP1 CU3. One of the management points is also the Site Server. The certificates for both of these servers will expire in April so I have a bit of time to figure this out. What is the proper procedure for updating the certificates that are about to expire? Is the only place I need to be concerned about updating IIS? Should I reissue the cert with the same key or different key or should I issue a new certificate with the same key or different key? Your experience is appreciated.

I recently noticed a similar thing. Sometimes Microsoft re-releases an update under the same KB. You may have downloaded the original version but in order for the update to deploy, you have to download the new version.

I tried this method of install and it still fails. Anyone else have any suggestions?? Michael

My SQL server is running 2012 SP1. I just installed CU8 and now I have the same problem. I was going to start by looking here (http://blogs.technet.com/b/configurationmgr/)

The uninstall is specified. So I don't need the old version application source files to be present on the client in order for the new application to call the uninstallation routine? What if it's a script that performs the uninstall?

I'm also hiding the app so it is not displayed in Software Center so users can't accidentally install it before the deadline

I'm also using application supercedence for this deployment. The supercedence rule uninstalls the old version first. I'm my test deployment (from scratch on 3 VMs and 6 computers based on our gold image), I had deployed the old version of the app with ConfigMgr and then deployed the new app with supercedence through ConfigMgr. It all worked flawlessly. In my production deployment, the existing app is already installed on all the computers. Can I just deploy the new version of the app superceding the old or do I need to deploy both the old and the new for the supercedence to work? I wasn't going to deploy the old because the app is part of the gold image already. I hope that makes sense This new deployment will get us off from using the gold image to have the app installed and enable us to use ConfigMgr going forward.

Sweet. Thanks for the confirmation

Hi There. I have a scenario that I want to get some clarification. I think I know how it will work but wonder if I'm understanding it correctly. I have clients across a WAN that I want to deploy an application to but the bandwidth is limited and I can't put local DPs there. I want to prestage the content and then enforce its installation after the server side of the app has been upgraded on Saturday. The collection that the clients are a member has a maintenance window defined daily from 2am to 5am. I was going to deploy the app and make it available for tonight at 8pm thinking that the client would see the deployment and begin to download it. The application deadline is set for 2 days from now on Saturday at 8pm. Am I correct in thinking that the client will install the application tonight at 2am during it's first available maintenance windows?? If so, my plan is to temporarily replace the daily 2am to 5am maintenance window with a maintenance window that starts at the deployment deadline on Saturday at 8pm. It seems to me that then the client would see the application, download it and wait to install until 8pm on Saturday when it would be enforced. I also plan to hide the deployment so that it does not show up in software center. Is my thinking correct?

Could it be something in your detection settings that make it look to the client that it's not installed when it actually is?