The SCCM client logs can be found in the following directory of each client’s local hard drive c:\Windows\CCM\Logs\. There are two main logs that I use when troubleshooting application failures Execmgr.log and AppEnforce.log. In this blog post, we are troubleshooting application installation failures. SCCM has a ton of logs, sometimes I think they may have too many! Depending on what you are troubleshooting, will determine what logs you should be reviewing. However, if the package is being successfully deployed and installed on many clients but failing on others, then use the steps below to troubleshoot why SCCM is failing to install your application successfully. This may not always be true but the probability is high that it is. Chances are that if the package is failing to install on ALL your clients, then something is most likely wrong with the installation package. The first question you MUST answer is whether the software package in question is failing to install on ALL or just some clients. Of course the error code will be different depending on the issue. When you open the System Center Configuration Manager 2012 Software Center and attempt to install the application it fails with a generic error “ Unable to make changes to your software” or “ The software change returned error code 0圆43(1603)“. The first indication of a problem can be found in the Software Center of the client in question. A common error a lot of folks receive is “ The software change returned error code 1603” and also “ Process terminated with exit code 1603“. Troubleshooting application installations in SCCM 2012 R2 can seem daunting but it really isn’t.
0 kommentar(er)
