#ONEDRIVE SYNC CLIENT SCRIPT ERROR INSTALL#
The only half reliable onedrive install is the one on the server used to maintain a local file history and concurrent backup that prevents agents who leave "unhappy" from destroying their local data.
#ONEDRIVE SYNC CLIENT SCRIPT ERROR DOWNLOAD#
What's worse is that the admin staff are using the online storage option which doesnt even download the damn files until the admin staff has to open/work with it, yet still onedrive is stuck constantly at syncing. Quit onedrive, reload, fixes the issue instantly. So many times i see onedrive at "syncing 9 files, 4.2gb of 4.3gb" but it never changes, it sits there for hours and hours. But no, on admin staff PCs, onedrive constantly pegging 1 cpu core, constantly syncing, like it never ever stops. Open in, click on folder, click on sync. Staff admin get the email "new user has shared their folder with you". Set sharing on the agents name for the admin staff so they can see the agents files so they can do the reports and paperwork etc.
New user comes in, create in o365 admin, sign into their laptop with those details on onedrive, all good.
No AD here, its real estate, agents come and go. Limited users for admin staff, the agents are all BYOD, so local admins. 24441, time stamp: 0x5cb93873įaulting application start time: 0x01d5c7a03754c61eįaulting application path: C:\Users\Administrator\AppData\Local\Microsoft\OneDrive\OneDrive.exeįaulting module path: C:\Windows\syswow64\KERNELBASE.dll This is an entirely difference PC, hell its a server and its also doing the same stupid error.įaulting module name: KERNELBASE.dll, version. We have checked and are way under the 300 thousand file limit. Onedrive is also constantly using a whole CPU core. Report Id: 643983b9-72e1-46ef-8bf0-31018f02a972įaulting package-relative application ID:Įxactly the same machine, 9 minutes later later.įaulting application start time: 0x01d5cc198f122178 I have been getting a LOT of these on the reception PCs.įaulting application name: OneDrive.exe, version: 19.222.1110.6, time stamp: 0x06c52c8dįaulting module name: KERNELBASE.dll, version: 2.535, time stamp: 0x5bd9df62įaulting application start time: 0x01d5cc198280c520įaulting application path: C:\Users\Reception\AppData\Local\Microsoft\OneDrive\OneDrive.exeįaulting module path: C:\Windows\System32\KERNELBASE.dll Right now they are thinking of throwing all the hard work away and just going back to file servers over VPN, at least they work every time.Įdit: i would like at least an error message that will point me in the right direction instead of "error in kernelbase"
The company im fixing this for has gone to the cloud to get with the times, but they are starting to regret it with the old file servers at each site still reliably chugging away, and onedrive having daily issues.Ĭan microsoft not at least FIX the app so its not so buggy? I mean you would think onedrive for business would be written by intelligent people, but apparrently that was a mistake on my behalf. With the old file servers and vpn, it was probably 1 hour per 6 months of work. Its getting to the point now that at least 1 hour a day is allocated to fixing onedrive issues, for a company of around 50 people. The company is way below the max amount of files and folders, but that just doesnt stop onedrive from crashing. It's constantly chewing on CPU and memory. Then even then sometimes i have to uninstall it, clear registry entries, reinstall it, resync it which can take half an hour sometimes. Half the time only a reboot fixes the issue. It keeps crashing and taking out explorer, and it doesnt even try to restart, it just shows an error message. Honestly, i am fixing onedrive sync issues every day now for only one organisation.
0 kommentar(er)
