Follow

How to parse log location for specific error syntax when redirecting all Portability (or other ProfileUnity logs) to UNC

Product: ProfileUnity

Product Version: N/A

Expires on:365 days from publish date

Updated: Feb 18, 2015

 

Problem: 

How to parse log location for specific syntax errors when redirecting all Portability (or other ProfileUnity logs) to UNC

 

Symptoms: 

Trying to determine what users might have errors in logs to determine any corrective action needed.  These errors can then be piped out to a text file for review.

 

Possible Resolution(s)

 

Create a batch file or run command at location where logs are stored.  See example:

 

find /i /c /n "syntax of string to search for" \\server\share\logs\*.log >c:\test.txt

or

find /i /c /n "error" \\server\share\logs\*.log >c:\test.txt

For additional reference see : https://liquidwarelabs.zendesk.com/entries/29568963-Where-to-find-ProfileUnity-logs-

For additional reference see : https://liquidwarelabs.zendesk.com/entries/30604046-How-to-change-Enhanced-Client-Logging-to-Debug-mode-

 

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.