KB: Using the System Center 2012 Configuration Manager CMTrace log viewer to review a log that contains a line exceeding 8000 characters causes the log to be truncated

KB: Using the System Center 2012 Configuration Manager CMTrace log viewer to review a log that contains a line exceeding 8000 characters causes the log to be truncated

  • Comments 2
  • Likes

imageHere’s a new Knowledge Base article we published. This one talks about an issue where using the System Center 2012 Configuration Manager CMTrace log viewer to review a log that contains a line exceeding 8000 characters causes the log to be truncated at that line.

=====

Symptoms

In System Center 2012 Configuration Manager, when you use the CMTrace log viewer to review any log that contains a line exceeding 8000 characters, the log is truncated at that line.

Resolution

There are two workarounds to this issue. First, you can simply view the log file in Notepad. Viewing the log file in Notepad will allow you to see all of the contents. Second, if you prefer to view the log in CMTrace you can edit the offending lines in Notepad (making them less than 8000 characters long) and then view the edited log in CMTrace.

=====

For the most current version of this article please see the following:

2716956 - Using the System Center 2012 Configuration Manager CMTrace log viewer to review a log that contains a line exceeding 8000 characters causes the log to be truncated

J.C. Hornbeck | System Center & Security Knowledge Engineer

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Use Notepad???!!!  Edit the Log file??!!  How about fixing the bug?

  • You can use Notepad++, too. :D There's another funny bug. F-Secure creates in a currently unknown way a line full on NULs and cmtrace cuts the log at this line.