Outlook add-in and disk activity

%3CLINGO-SUB%20id%3D%22lingo-sub-916507%22%20slang%3D%22en-US%22%3EOutlook%20add-in%20and%20disk%20activity%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-916507%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20guys%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20an%20issue%20with%20outlook%202016%20(Office%20365)%20and%20teams%20Outlook%20add-in.%20When%20Teams%20add-in%20is%20turned%20on%20in%20outlook%2C%20disk%20activity%20increase%2C%20and%20computer%20slow%20down%20dramatically.%20We%20have%20noticed%20that%20the%20disk%20activity%20is%20in%20%25localappdata%25%5Ctemp%20on%20oulook%20logging%20folder%20and%20oulook%26nbsp%3B%20related%20logfiles%2C%20but%20we%20%3CU%3Edon't%20have%20turn%20on%3C%2FU%3E%20outlook%20logging.%3C%2FP%3E%3CP%3EIf%20we%20disable%20the%20teams%20add-in%2C%20outlook%20logs%20files%20are%20still%20created%2C%20but%20with%20no%20activity.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20ideas%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-916507%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-934782%22%20slang%3D%22en-US%22%3ERe%3A%20Outlook%20add-in%20and%20disk%20activity%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-934782%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20seeing%20exactly%20the%20same%20behaviour.%26nbsp%3B%20With%20Perfmon%20running%20outlook.exe%20is%20writing%20to%20a%20db%20file%20in%20%25temp%25%20continuously%20causing%20disk%20utilisation%20by%20Outlook%20to%20be%20around%2075%25%20-%20100%25.%26nbsp%3B%20If%20I%20turn%20off%20the%20Teams%20add-in%20in%20Outlook%20then%20disk%20utilisation%20drops%20to%20around%200.1%25.%26nbsp%3B%20This%20is%20causing%20major%20impact%20to%20users.%26nbsp%3B%20We%20have%20the%20latest%20Office%20365%20and%20Teams%20versions%20installed.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-934859%22%20slang%3D%22en-US%22%3ERe%3A%20Outlook%20add-in%20and%20disk%20activity%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-934859%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F317390%22%20target%3D%22_blank%22%3E%40Bob_Manning%3C%2FA%3E%26nbsp%3BCan%20you%20post%20the%20exact%20version%20of%20Office%20and%20Teams%20client.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOnly%20because%20I%20read%20this%20and%20was%20alarmed.%20But%2C%20is%20this%20monthly%20channel%2C%20semi-annual%2C%20etc.%20Thanks%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMark%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-952538%22%20slang%3D%22en-US%22%3ERe%3A%20Outlook%20add-in%20and%20disk%20activity%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-952538%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F427130%22%20target%3D%22_blank%22%3E%40Christophe_DHUYGELAERE%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGetting%20the%20same%20issue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHave%20managed%20to%20mitigate%20by%20setting%20the%20two%20files%20as%20read%20only%20for%20now.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eattrib%20%2Br%20%25appdata%25%5C..%5CLocal%5CTemp%5C*.db*%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-962454%22%20slang%3D%22en-US%22%3ERe%3A%20Outlook%20add-in%20and%20disk%20activity%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-962454%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F54198%22%20target%3D%22_blank%22%3E%40Mark%20Garza%3C%2FA%3EWe%20are%20using%20the%20monthly%20channel%20for%20Office%20and%20Teams%20is%20latest%20version.%26nbsp%3B%20Had%20session%20with%20Microsoft%20support%20today%20that%20installed%20Team%201.2.00.26774%20(64%20bit)%2C%20I%20was%20using%20the%2032bit%20Teams%20Client%20but%20this%20has%20made%20no%20difference.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-966608%22%20slang%3D%22en-US%22%3ERe%3A%20Outlook%20add-in%20and%20disk%20activity%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-966608%22%20slang%3D%22en-US%22%3E%3CP%3E%26gt%3B%20Have%20managed%20to%20mitigate%20by%20setting%20the%20two%20files%20as%20read%20only%20for%20now.%3C%2FP%3E%3CP%3E%26gt%3B%20attrib%20%2Br%20%25appdata%25%5C..%5CLocal%5CTemp%5C*.db*%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20this%20solved%20it%20for%20me!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20others%2C%20step-by-step%20instructions%20that%20worked%20for%20me%20are%20below.%3C%2FP%3E%3CUL%3E%3CLI%3ELaunch%20an%20Administrator%2FElevated%20Command%20Prompt%20(%3CA%20href%3D%22https%3A%2F%2Fappuals.com%2Fhow-to-open-an-elevated-command-prompt-on-windows-10%2F%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EInstructions%20on%20how%20to%20do%20this%3C%2FA%3E)%3C%2FLI%3E%3CLI%3ENavigate%20to%20your%20working%20temp%20directory%20by%20entering%20the%20following%20into%20your%20elevated%20command%20prompt%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-java%22%3E%3CCODE%3Ecd%20C%3A%5CUsers%5Cuser.name%5CAppData%5CLocal%5CTemp%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%222%22%3E%3CEM%3EIn%20example%20directory%20above%20replace%20%60user.name%60%20with%20your%20windows%20login%20name%3C%2FEM%3E%3C%2FFONT%3E%3C%2FP%3E%3CUL%3E%3CLI%3ENow%20paste%20the%20following%20and%20hit%20Enter%20key%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-markup%22%3E%3CCODE%3Eattrib%20%2Br%20%25appdata%25%5C..%5CLocal%5CTemp%5C*.db*%E2%80%8B%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-968462%22%20slang%3D%22en-US%22%3ERe%3A%20Outlook%20add-in%20and%20disk%20activity%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-968462%22%20slang%3D%22en-US%22%3E%3CP%3ERecommendation%20from%20Microsoft%20Support%20yesterday%20was%20to%20revert%20to%20the%20semi-annual%20channel%20which%20is%20not%20showing%20this%20same%20issue.%26nbsp%3B%20I'm%20reluctant%20to%20do%20this%20across%20all%20my%20users%20as%20there%20have%20been%20several%20new%20features%20introduced%20in%20the%20monthly%20channel%20since%20the%20last%20semi-annual%20channel%20release%20so%20they%20would%20lose%20functionality.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1070108%22%20slang%3D%22fr-FR%22%3ERe%3A%20Outlook%20add-in%20and%20disk%20activity%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1070108%22%20slang%3D%22fr-FR%22%3E%3CP%3EThis%20workaroud%20is%20working.%20But%20what%20about%20removing%20rights%20on%20the%20db%20files%3F%20Will%20it%20be%20an%20issue%20later%20with%20updates%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1123346%22%20slang%3D%22en-US%22%3ERe%3A%20Outlook%20add-in%20and%20disk%20activity%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1123346%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F433506%22%20target%3D%22_blank%22%3E%40RyanMNM%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUsed%20the%20Attrib%20command%20to%20stem%20the%20bleeding%2C%20but%20has%20anyone%20found%20a%20permanent%20solution%20to%20this%20issue%20%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1379199%22%20slang%3D%22fr-FR%22%3ERe%3A%20Outlook%20add-in%20and%20disk%20activity%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1379199%22%20slang%3D%22fr-FR%22%3E%3CP%3EThis%20issue%20is%20really%20annoying%20almost%20all%20our%20users.%3C%2FP%3E%3CP%3EWe%20use%20the%20workaround%20but%20it%20came%20back%20every%20week%2Fmonth%2F...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20need%20a%20patch!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1118141%22%20slang%3D%22en-US%22%3ERe%3A%20Outlook%20add-in%20and%20disk%20activity%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1118141%22%20slang%3D%22en-US%22%3E%3CP%3EAnyone%20had%20any%20further%20luck%20with%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Hi guys,

 

We have an issue with outlook 2016 (Office 365) and teams Outlook add-in. When Teams add-in is turned on in outlook, disk activity increase, and computer slow down dramatically. We have noticed that the disk activity is in %localappdata%\temp on oulook logging folder and oulook  related logfiles, but we don't have turn on outlook logging.

If we disable the teams add-in, outlook logs files are still created, but with no activity.

 

Any ideas ?

39 Replies
Highlighted

We are seeing exactly the same behaviour.  With Perfmon running outlook.exe is writing to a db file in %temp% continuously causing disk utilisation by Outlook to be around 75% - 100%.  If I turn off the Teams add-in in Outlook then disk utilisation drops to around 0.1%.  This is causing major impact to users.  We have the latest Office 365 and Teams versions installed.

Highlighted

@Bob_Manning Can you post the exact version of Office and Teams client.

 

Only because I read this and was alarmed. But, is this monthly channel, semi-annual, etc. Thanks

 

Mark

Highlighted

@Christophe_DHUYGELAERE 

 

Getting the same issue.

 

Have managed to mitigate by setting the two files as read only for now.

 

attrib +r %appdata%\..\Local\Temp\*.db*

 

Highlighted

@Mark GarzaWe are using the monthly channel for Office and Teams is latest version.  Had session with Microsoft support today that installed Team 1.2.00.26774 (64 bit), I was using the 32bit Teams Client but this has made no difference.

Highlighted

> Have managed to mitigate by setting the two files as read only for now.

> attrib +r %appdata%\..\Local\Temp\*.db*

 

Thank you this solved it for me!

 

For others, step-by-step instructions that worked for me are below.

  • Launch an Administrator/Elevated Command Prompt (Instructions on how to do this)
  • Navigate to your working temp directory by entering the following into your elevated command prompt

 

cd C:\Users\user.name\AppData\Local\Temp

 

In example directory above replace `user.name` with your windows login name

  • Now paste the following and hit Enter key

 

attrib +r %appdata%\..\Local\Temp\*.db*​

 

Highlighted

Recommendation from Microsoft Support yesterday was to revert to the semi-annual channel which is not showing this same issue.  I'm reluctant to do this across all my users as there have been several new features introduced in the monthly channel since the last semi-annual channel release so they would lose functionality.

Highlighted

This workaroud is working. But what about removing rights on the db files ? Will it be an issue later with updates ?

Highlighted

Anyone had any further luck with this?

Highlighted

@RyanMNM 

 

Used the Attrib command to stem the bleeding, but has anyone found a permanent solution to this issue ? 

Highlighted
Anyone had any further luck with finding a permanent solution to this issue ?
Highlighted

@DDJ-215 last i spoke to support when i raised a ticket they said it would be logged as a bug and would be fixed in a future update... when that will come is obviously up to Microsoft!

Highlighted

@RyanMNM ..  his past weekend, I uninstalled Office 32Bit and installed 64 bit.  I will post the group EOW on performance results.. So far today, it has been satisfactory..

Highlighted

@DDJ-215 interesting, the version of teams i have installed is 64Bit and office was 32bit.

 

Just updating Office to 64 to see if this helps.

Highlighted

we are running into the same issue.  making the .db file read-only worked

Highlighted

@RyanMNM 

Did this fix the high disk usage

Highlighted
Nope, so far the DB fix is the only one that seems to benefit / work.
Highlighted
Is there a more permanent solution for resolving Outlook/Teams link causing 80-1000% system utilization than the work around posted in link below? I ask because this has to be repeated every time Teams updates. Please advise!
 
Launch an Administrator/Elevated Command Prompt
Navigate to working temp directory by entering the following into your elevated command prompt:
     cd C:\Users\user.name\AppData\Local\Temp
 
In example directory above replace `user.name` with your windows login name
     Paste (or) Type the following and hit Enter key
      attrib +r %appdata%\..\Local\Temp\*.db*​
Highlighted

This issue is really annoying almost all our users.

We use the workaround but it cames back every week/month/...

 

We need a patch !

Highlighted

@benpat what version of Teams and Outlook are being run here in this thread. Notice monthly and latest Teams version curious. Thanks.