Why cmtrace.exe is not always your best friend

I once heard a very wise guy saying the notepad is all you need to read log files. I do not say I agree, as I find cmtrace a slightly better tool…. but that’s right until I ran into a ConfigMgr 2012 upgrade to ConfigMgr 1511 earlier today. My upgrade failed, during the file copy phase because it couldn’t copy a new version of cmtrace to my tools folder. Whatever you do, do not click on the View Log button in the installation dialog.

The error in configmgrsetup.log:

ERROR: Failed to copy E:\INSTALLATIONSOURCE\MS\CONFIGMGR1511\DVD\SMSSETUP\tools\CMTrace.exe to k:\program files\microsoft configuration manager\tools\cmtrace.exe, Win32 error = 5

 

image

This happened during the file copy phase, which is almost right after the upgrade database phase! I’ll leave it up to you to figure out what that means – not a big problem as we always backup the server before any upgrade!

By | 2016-01-11T10:24:47+00:00 January 11th, 2016|Configuration Manager (SCCM)|2 Comments

About the Author:

Kent Agerlund
Microsoft Regional Director, Enterprise Mobility MVP. Microsoft Certified Trainer and Principal consultant. I have been working with Enterprise client management since 1992. Co-founder of System Center User Group Denmark in 2009. Certified MCITP: Enterprise Administrator, MCSA+Messaing, and much more. Member of: Microsoft Denmark System Center Partner Expert Team The Danish Technet Influencers program System Center Influencers Program.

2 Comments

  1. Jesper Christensen January 11, 2016 at 12:41 - Reply

    That is why I always copy cmtrace to a different location. But stupid that MS did not build in a check for this

  2. Tamir Levy September 1, 2016 at 8:56 - Reply

    That is correct,
    and that is why one of the most basic things we do when we configure SCCM server is to copy the cmtrace.exe to System32 or any other path and then make it the default .log FTA program

Leave A Comment