Difference between revisions of "Huge size of logs.txt microsoft teams"

From Ilianko
m
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
Huge log is generated by MS Teams in the folder
 
Huge log is generated by MS Teams in the folder
  
−
*C:\Users\ilianko\AppData\Roaming\Microsoft\Teams
+
*C:\Users\user\AppData\Roaming\Microsoft\Teams
  
 
The log name:
 
The log name:
Line 9: Line 9:
 
The Log is full with this entries:
 
The Log is full with this entries:
 
<code><pre>
 
<code><pre>
−
Wed Aug 02 2023 12:22:30 GMT+0300 <11284> -- info -- Sending Teams call status to SfB:TeamsNoCall  
+
Wed Aug 02 2023 12:22:30 <11284> -- info -- Sending Teams call status to SfB:TeamsNoCall  
−
Wed Aug 02 2023 12:22:30 GMT+0300 <11284> -- info -- Sending data for IPC to Sfb: TeamsNoCall  
+
Wed Aug 02 2023 12:22:30  <11284> -- info -- Sending data for IPC to Sfb: TeamsNoCall  
−
Wed Aug 02 2023 12:22:30 GMT+0300 <11284> -- info -- Sending data for IPC to Sfb: TeamsStatusQuery  
+
Wed Aug 02 2023 12:22:30  <11284> -- info -- Sending data for IPC to Sfb: TeamsStatusQuery  
−
Wed Aug 02 2023 12:22:30 GMT+0300 <11284> -- info -- Received: SfBNoCall#  
+
Wed Aug 02 2023 12:22:30  <11284> -- info -- Received: SfBNoCall#  
−
Wed Aug 02 2023 12:22:30 GMT+0300 <11284> -- info -- processing command: sfbnocall  
+
Wed Aug 02 2023 12:22:30  <11284> -- info -- processing command: sfbnocall  
−
Wed Aug 02 2023 12:22:30 GMT+0300 <11284> -- info -- processing command:   
+
Wed Aug 02 2023 12:22:30  <11284> -- info -- processing command:   
−
Wed Aug 02 2023 12:22:30 GMT+0300 <11284> -- info -- Sending Teams call status to SfB:TeamsNoCall  
+
Wed Aug 02 2023 12:22:30  <11284> -- info -- Sending Teams call status to SfB:TeamsNoCall  
−
Wed Aug 02 2023 12:22:30 GMT+0300 <11284> -- info -- Sending data for IPC to Sfb: TeamsNoCall  
+
Wed Aug 02 2023 12:22:30  <11284> -- info -- Sending data for IPC to Sfb: TeamsNoCall  
−
Wed Aug 02 2023 12:22:30 GMT+0300 <11284> -- info -- Sending data for IPC to Sfb: TeamsStatusQuery  
+
Wed Aug 02 2023 12:22:30  <11284> -- info -- Sending data for IPC to Sfb: TeamsStatusQuery  
−
Wed Aug 02 2023 12:22:30 GMT+0300 <11284> -- info -- Received: SfBNoCall#  
+
Wed Aug 02 2023 12:22:30  <11284> -- info -- Received: SfBNoCall#  
−
Wed Aug 02 2023 12:22:30 GMT+0300 <11284> -- info -- processing command: sfbnocall  
+
Wed Aug 02 2023 12:22:30  <11284> -- info -- processing command: sfbnocall  
−
Wed Aug 02 2023 12:22:30 GMT+0300 <11284> -- info -- processing command:  
+
Wed Aug 02 2023 12:22:30  <11284> -- info -- processing command:  
 
</pre></code>
 
</pre></code>
  
−
In the current environment we have both skype for business on-premise and teams working.
+
In AD environment skype for business on-premise and teams are existing together on windows workstation.
−
If there is unanswered call to local Teams member, during idle screen the log generation explodes. If the Skype for business is stopped no more logs are generated.
+
If there is unanswered call to Teams when workstation is in idle state, the log generation explodes. If Skype for business stops, no more logs are generated.
 +
 
 +
==Workaround==:
 +
*Create Reg entry
 +
[HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Office\16.0\Lync]
 +
"EnableTeamsHIDInterop"=dword:00000000
 +
 
 +
Or
 +
*delete logs.txt file and create folder with the same name logs.txt

Latest revision as of 06:26, 7 August 2023

Huge log is generated by MS Teams in the folder

  • C:\Users\user\AppData\Roaming\Microsoft\Teams

The log name:

  • file name: logs.txt / old_logs_[date].txt


The Log is full with this entries: 

Wed Aug 02 2023 12:22:30  <11284> -- info -- Sending Teams call status to SfB:TeamsNoCall 
Wed Aug 02 2023 12:22:30  <11284> -- info -- Sending data for IPC to Sfb: TeamsNoCall 
Wed Aug 02 2023 12:22:30  <11284> -- info -- Sending data for IPC to Sfb: TeamsStatusQuery 
Wed Aug 02 2023 12:22:30  <11284> -- info -- Received: SfBNoCall# 
Wed Aug 02 2023 12:22:30  <11284> -- info -- processing command: sfbnocall 
Wed Aug 02 2023 12:22:30  <11284> -- info -- processing command:  
Wed Aug 02 2023 12:22:30  <11284> -- info -- Sending Teams call status to SfB:TeamsNoCall 
Wed Aug 02 2023 12:22:30  <11284> -- info -- Sending data for IPC to Sfb: TeamsNoCall 
Wed Aug 02 2023 12:22:30  <11284> -- info -- Sending data for IPC to Sfb: TeamsStatusQuery 
Wed Aug 02 2023 12:22:30  <11284> -- info -- Received: SfBNoCall# 
Wed Aug 02 2023 12:22:30  <11284> -- info -- processing command: sfbnocall 
Wed Aug 02 2023 12:22:30  <11284> -- info -- processing command:

In AD environment skype for business on-premise and teams are existing together on windows workstation. If there is unanswered call to Teams when workstation is in idle state, the log generation explodes. If Skype for business stops, no more logs are generated.

==Workaround==:

  • Create Reg entry

[HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Office\16.0\Lync] "EnableTeamsHIDInterop"=dword:00000000

Or

  • delete logs.txt file and create folder with the same name logs.txt
Retrieved from "https://ilianko.com/index.php?title=Huge_size_of_logs.txt_microsoft_teams&oldid=6084"