OneDrive for Business high CPU usage with Sharepoint on-premise

%3CLINGO-SUB%20id%3D%22lingo-sub-162053%22%20slang%3D%22en-US%22%3EOneDrive%20for%20Business%20high%20CPU%20usage%20with%20Sharepoint%20on-premise%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-162053%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%0A%3CP%3Ewe%20use%20OneDrive%20for%20Business%20for%20synchronization%20with%20SharePoint%202013%20on-premise.%20Since%20one%20of%20last%20Office%20updates%20the%20client%20started%20to%20consume%20CPU%20constantly.%20I%20found%20out%20that%20the%20client%20is%20still%20writing%20some%20.etl%20files%20into%20following%20directory%20that%20is%26nbsp%3Bbecoming%20realy%20huge%20because%20of%20it.%3C%2FP%3E%0A%3CP%3EC%3A%5CUsers%5Cusername%5CAppData%5CLocal%5CMicrosoft%5COffice%5CSpw%5Clogs%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EPlease%20don't%20give%20me%20recommendation%20to%20move%20to%20the%20classic%20OneDrive%20client%20since%20that%20is%20working%20only%20with%20SharePoint%20online%20product.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EDoes%20anyone%20have%20any%20idea%20how%20to%20stop%20the%20CPU%20drain%3F%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-162053%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOn-Premises%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOneDrive%20for%20Business%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-171033%22%20slang%3D%22en-US%22%3ERe%3A%20OneDrive%20for%20Business%20high%20CPU%20usage%20with%20Sharepoint%20on-premise%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-171033%22%20slang%3D%22en-US%22%3E%3CP%3EDuring%20the%20years%2C%20Microsoft%20only%20develop%20new%20feature%20for%20the%20latest%20Version%20or%20the%20new%20expected%20Version.%20(Exception%3A%20Security%20issues).%3CBR%20%2F%3E%3CBR%20%2F%3EAs%20I%20said%2C%20the%20Next%20Generation%20Sync%20Client%20will%20only%20work%20with%20SharePoint%20Server%202019.%3CBR%20%2F%3EFakt.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-171028%22%20slang%3D%22en-US%22%3ERe%3A%20OneDrive%20for%20Business%20high%20CPU%20usage%20with%20Sharepoint%20on-premise%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-171028%22%20slang%3D%22en-US%22%3E%3CP%3E1st%20-%20Yes%2C%20I%20wrote%20that%20I%20cannot%20use%20it.%3C%2FP%3E%0A%3CP%3E2nd%20-%20Sharepoint%20server%202013%20is%20still%20supported%20product%20as%20same%20as%20OneDrive%20for%20Business%20(Groove)%20so%20why%20do%20I%20need%20to%20wait%3F%20Microsoft%20should%20fix%20it's%20issue.%3C%2FP%3E%0A%3CP%3E3rd%20-%20Yes%20thats%20the%20point.%20I%20wrote%20it.%20Whole%20issue%20is%20about%20OneDrive%20for%20Business%2C%20read%20more%20carefuly%20please.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E4th%20-%20I%20cannot%20use%20new%20generation%20sync%20client%20so%20I%20don't%20care%20about%20it's%20log%20location.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-171023%22%20slang%3D%22en-US%22%3ERe%3A%20OneDrive%20for%20Business%20high%20CPU%20usage%20with%20Sharepoint%20on-premise%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-171023%22%20slang%3D%22en-US%22%3E%3CP%3E1st%3A%20You%20cannot%20use%20the%20new%20sync%20Client%20to%20sync%20data%20from%20any%20OnePremises%20Version.%20You%20must%20sync%20with%20the%20old%20OneDrive%20for%20Business%20(Groove)%20Client.%3C%2FP%3E%0A%3CP%3E2nd%3A%20The%20first%20onPremises%20SharePoint%20you%20will%20be%20able%20is%20SharePoint%20Server%202019%20!!%3CBR%20%2F%3E3rd%3A%20The%20Picture%20showd%20%22OneDrive%20for%20Business%22%20and%20Not%26nbsp%3B%20OneDrive%3CBR%20%2F%3E4th%3A%20The%20log%20Files%20from%20the%20new%20Next%20Generation%20Sync%20Client%20are%20stored%20on%20a%20diffrent%20Location%3A%3CBR%20%2F%3E%26nbsp%3BC%3A%5CUsers%5C%5BUSER%5D%5CAppData%5CLocal%5CMicrosoft%5COneDrive%5Clogs%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHans%20Brender%2C%20MVP%20Office%20Servers%20and%20Services%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Hello,

we use OneDrive for Business for synchronization with SharePoint 2013 on-premise. Since one of last Office updates the client started to consume CPU constantly. I found out that the client is still writing some .etl files into following directory that is becoming realy huge because of it.

C:\Users\username\AppData\Local\Microsoft\Office\Spw\logs

 

Please don't give me recommendation to move to the classic OneDrive client since that is working only with SharePoint online product.

 

Does anyone have any idea how to stop the CPU drain? 

Thanks

3 Replies
Highlighted

1st: You cannot use the new sync Client to sync data from any OnePremises Version. You must sync with the old OneDrive for Business (Groove) Client.

2nd: The first onPremises SharePoint you will be able is SharePoint Server 2019 !!
3rd: The Picture showd "OneDrive for Business" and Not  OneDrive
4th: The log Files from the new Next Generation Sync Client are stored on a diffrent Location:
 C:\Users\[USER]\AppData\Local\Microsoft\OneDrive\logs

 

Hans Brender, MVP Office Servers and Services

Highlighted

1st - Yes, I wrote that I cannot use it.

2nd - Sharepoint server 2013 is still supported product as same as OneDrive for Business (Groove) so why do I need to wait? Microsoft should fix it's issue.

3rd - Yes thats the point. I wrote it. Whole issue is about OneDrive for Business, read more carefuly please. 

4th - I cannot use new generation sync client so I don't care about it's log location.

Highlighted

During the years, Microsoft only develop new feature for the latest Version or the new expected Version. (Exception: Security issues).

As I said, the Next Generation Sync Client will only work with SharePoint Server 2019.
Fakt.