Quantcast
Channel: Lync Server 2013 - Management, Planning, and Deployment forum
Viewing all articles
Browse latest Browse all 5984

Event ID 33020 LS Centralized Logging Agent - Error while moving cache files to network share

$
0
0

I have the "AlwaysOn" CLS logging scenario running in my Lync 2013 Enterprise deployment.  I did not configure the CacheFileNetworkFolder option since i don't care about retaining these logs anywhere other than on the local drives of the Lync servers so i just left it blank.  Now every few hours or so I am getting Event ID 33020 in each Lync server and SCOM is firing an alert as well.

The CsClsLogging configuration is as follows:

PS C:\> Get-CsClsConfiguration


Identity                      : Global
Scenarios                     : {Name=AlwaysOn, Name=MediaConnectivity, Name=ApplicationSharing,
                                Name=AudioVideoConferencingIssue...}
SearchTerms                   : {Type=Phone;Inserts=ItemE164,ItemURI,ItemSIP,ItemPII,
                                Type=URI;Inserts=ItemURI,ItemSIP,ItemPII,
                                Type=CallId;Inserts=ItemCALLID,ItemURI,ItemSIP,ItemPII,
                                Type=ConfId;Inserts=ItemCONFID,ItemURI,ItemSIP,ItemPII...}
SecurityGroups                : {}
Regions                       : {}
EtlFileFolder                 : C:\CLSTracing
EtlFileRolloverSizeMB         : 20
EtlFileRolloverMinutes        : 60
TmfFileSearchPath             : C:\Program Files\Common Files\Microsoft Lync Server 2013\Tracing\
CacheFileLocalFolders         : C:\CLSTracing
CacheFileNetworkFolder        :
CacheFileLocalRetentionPeriod : 14
CacheFileLocalMaxDiskUsage    : 80
ComponentThrottleLimit        : 5000
ComponentThrottleSample       : 3
MinimumClsAgentServiceVersion : 6

Is there a way to stop the flow of these events without having to configure CLS to transfer the logs to a network share?



Viewing all articles
Browse latest Browse all 5984

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>