Lync Snooper 2013 does not parse logs correctly unless machine region is EN-US – ERROR: Illegal character from S4 trace

Lync Snooper 2013 does not parse logs correctly unless machine region is EN-US  –

http://lyncdup.com/2013/06/lync-snooper-2013-does-not-parse-logs-correctly-unless-machine-region-is-en-us/

Snooper.exe would open the captures successfully, but you would see the following messages:

TL_ERROR(TF_COMPONENT) [0]12E0.201C::06/16/2013-08:07:35.116.00000d8a (S4,SipMessage.CheckNonAscii:1823.idx(809))Illegal character from S4 trace. Count:95

I can confirm that this has now been resolved in the latest version of the Lync Debugging Tools found here.

 

Andrew Morpeth
Andrew Morpethhttps://ucgeek.co/author/amorpeth/
Andrew is a Modern Workplace Consultant specialising in Microsoft technologies based in Auckland, New Zealand; Andrew is a Director and Professional Services Manager at Lucidity Cloud Services and a Microsoft MVP.

Related Articles

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Andrew Morpeth
Andrew Morpethhttps://ucgeek.co/author/amorpeth/
Andrew is a Modern Workplace Consultant specialising in Microsoft technologies based in Auckland, New Zealand; Andrew is a Director and Professional Services Manager at Lucidity Cloud Services and a Microsoft MVP.

Latest Articles