Difference between revisions of "Huge size of logs.txt microsoft teams"
From Ilianko
| 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\ | + | *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 GMT+0300 <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 GMT+0300 <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 GMT+0300 <11284> -- info -- Sending data for IPC to Sfb: TeamsStatusQuery | ||
| Line 24: | Line 24: | ||
In the current environment we have both skype for business on-premise and teams working together. | In the current environment we have both skype for business on-premise and teams working together. | ||
| − | If there is unanswered call to local Teams member, | + | If there is unanswered call to local Teams member when computer is in idle state, the log generation explodes. If Skype for business is stopped, no more logs are generated. |
Revision as of 09:58, 2 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 GMT+0300 <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 GMT+0300 <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 GMT+0300 <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 GMT+0300 <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 GMT+0300 <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 GMT+0300 <11284> -- info -- processing command: sfbnocall
Wed Aug 02 2023 12:22:30 GMT+0300 <11284> -- info -- processing command:
In the current environment we have both skype for business on-premise and teams working together. If there is unanswered call to local Teams member when computer is in idle state, the log generation explodes. If Skype for business is stopped, no more logs are generated.
