During a ConfigMgr client migration from SCCM 2007 to 2012 R2 we had several reports of SCNotification errors on clients workstations. The user would see the below 2 error messages at logon and also when they attempted to launch Software Center.
Note: The SCNotification process is a notification engine for the Configuration Manager client.
We verified the .NET installation state using the .NET Framework Setup Verification Tool and everything appeared to be ok. We also ran the .NET Framework Repair Tool without any success.
After digging into these machines further, we found they did have corrupt .NET previous to the client upgrade which caused the SCNotification failure. Why didn’t the .NET Verification or Repair tool find this corruption? This is because not all .NET corruption can be repaired and sometimes a full reinstall is required.
Here are steps I used to resolve.
1) Uninstall the ConfigMgr client.
a) Open a command prompt and navigate to c:\windows\ccmsetup
b) Type in ccmsetup.exe /uninstall, and press Enter
c) Verify the uninstall by monitoring the ccmsetup.exe process or wait until Configuration Manager is no longer listed in the Control Panel
2) Uninstall .NET Framework 4.5.1 from the workstation. If this version is not installed, uninstall the highest version of .NET (v3.0 or greater).
3) Reboot the workstation.
4) Manually install .NET Framework 4.5.1 from Microsoft.
Note: The ConigMgr 2012 R2 client will use highest version of .NET currently installed (.NET 3.0 or greater). If no supported versions are installed, the ConfigMgr client will install .NET 4.0.
5) Install the ConfigMgr client on the workstation. I used Client Push and monitored the ccmsetup.log and clientmsi.log files located here, c:\windows\ccmsetup\logs.
6) Test the workstation by rebooting and then launch Software Center. If this worked, you should have no more SCNotification errors.