Microsoft Office Cache Upload Center Error Repair
Office 2016 Upload Center app crash
How-do-you-do,
nosotros are using Office 2016 x64 on a MS RDS subcontract.
Since a few days we get this error, when the function upload center is opened:
When you klick repair, the app crashes:
The eventlog shows this:
Version=ane
EventType=APPCRASH
EventTime=132845469423146914
ReportType=2
Consent=1
UploadTime=132845469425137015
ReportIdentifier=64a169ea-6233-11ec-aadf-005056b72471
IntegratorReportIdentifier=64a169e9-6233-11ec-aadf-005056b72471
AppSessionGuid=00004378-0009-02d3-f465-fe1440f6d701
TargetAppId=West:00001d0810c4ef12850bd4374d80fa9f7d260000ffff!00004e0a549249f0c35aeaad337d9915afd81048aefb!MSOUC.EXE
TargetAppVer=2016//09//thirteen:19:06:38!ada64!MSOUC.EXE
BootId=4294967295
Response.type=4
Sig[0].Proper name=Awarding Name
Sig[0].Value=MSOUC.EXE
Sig[1].Proper name=Awarding Version
Sig[1].Value=16.0.4444.grand
Sig[ii].Name=Awarding Timestamp
Sig[ii].Value=57d84e3e
Sig[3].Proper name=Fault Module Name
Sig[3].Value=Csi.dll
Sig[4].Proper noun=Mistake Module Version
Sig[4].Value=16.0.4687.1000
Sig[5].Proper name=Mistake Module Timestamp
Sig[5].Value=5ac3c128
Sig[half dozen].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Kickoff
Sig[7].Value=00000000001c4084
DynamicSig[i].Proper name=OS Version
DynamicSig[1].Value=10.0.14393.2.0.0.144.eight
DynamicSig[ii].Proper noun=Locale ID
DynamicSig[2].Value=1031
UI[ii]=C:\Plan Files\Microsoft Role\Office16\MSOUC.EXE
UI[3]=Microsoft Office Upload Center has stopped working
UI[4]=Windows tin can cheque online for a solution to the trouble.
UI[5]=Check online for a solution and close the plan
UI[6]=Check online for a solution afterward and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Program Files\Microsoft Office\Office16\MSOUC.EXE
LoadedModule[ane]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\System32\KERNEL32.dll
LoadedModule[3]=C:\Windows\system32\hmpalert.dll
LoadedModule[4]=C:\Windows\System32\KERNELBASE.dll
LoadedModule[5]=C:\Windows\System32\ucrtbase.dll
LoadedModule[6]=C:\Windows\System32\ADVAPI32.dll
LoadedModule[7]=C:\Windows\System32\msvcrt.dll
LoadedModule[8]=C:\Windows\System32\sechost.dll
LoadedModule[ix]=C:\Windows\System32\RPCRT4.dll
LoadedModule[10]=C:\Windows\System32\ole32.dll
LoadedModule[11]=C:\Windows\System32\combase.dll
LoadedModule[12]=C:\Windows\System32\bcryptPrimitives.dll
LoadedModule[xiii]=C:\Windows\System32\GDI32.dll
LoadedModule[14]=C:\Windows\System32\gdi32full.dll
LoadedModule[15]=C:\Windows\System32\USER32.dll
LoadedModule[xvi]=C:\Windows\System32\win32u.dll
LoadedModule[17]=C:\Windows\SYSTEM32\VCRUNTIME140.dll
LoadedModule[xviii]=C:\Windows\SYSTEM32\MSIMG32.dll
LoadedModule[19]=C:\Programme Files\Microsoft Role\Office16\MSOHEV.DLL
LoadedModule[20]=C:\Windows\SYSTEM32\MSVCP140.dll
LoadedModule[21]=C:\Windows\SYSTEM32\VCRUNTIME140_1.dll
LoadedModule[22]=C:\Windows\System32\IMM32.DLL
LoadedModule[23]=C:\Plan Files\Mutual Files\Microsoft Shared\Office16\mso20win32client.dll
LoadedModule[24]=C:\Windows\System32\OLEAUT32.dll
LoadedModule[25]=C:\Windows\System32\msvcp_win.dll
LoadedModule[26]=C:\Program Files\Common Files\Microsoft Shared\Office16\mso30win32client.dll
LoadedModule[27]=C:\Programme Files\Common Files\Microsoft Shared\Office16\mso40uiwin32client.dll
LoadedModule[28]=C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.i.14393.4770_none_aecd7b51ddd26054\gdiplus.dll
LoadedModule[29]=C:\Programme Files\Common Files\Microsoft Shared\Office16\mso99Lwin32client.dll
LoadedModule[30]=C:\Windows\SYSTEM32\SLC.dll
LoadedModule[31]=C:\Windows\SYSTEM32\sppc.dll
LoadedModule[32]=C:\Plan Files\Mutual Files\Microsoft Shared\Office16\mso.dll
LoadedModule[33]=C:\Windows\SYSTEM32\msi.dll
LoadedModule[34]=C:\Windows\System32\SHELL32.dll
LoadedModule[35]=C:\Windows\System32\cfgmgr32.dll
LoadedModule[36]=C:\Windows\System32\windows.storage.dll
LoadedModule[37]=C:\Windows\System32\powrprof.dll
LoadedModule[38]=C:\Windows\System32\shlwapi.dll
LoadedModule[39]=C:\Windows\System32\kernel.appcore.dll
LoadedModule[40]=C:\Windows\System32\shcore.dll
LoadedModule[41]=C:\Windows\System32\profapi.dll
LoadedModule[42]=C:\Windows\SYSTEM32\bcrypt.dll
LoadedModule[43]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.14393.4169_none_7de0bbf28341b1f2\Comctl32.dll
LoadedModule[44]=C:\Plan Files\Microsoft Role\Office16\1033\wxpr.dll
LoadedModule[45]=C:\Windows\SYSTEM32\d2d1.dll
LoadedModule[46]=C:\Windows\System32\CRYPT32.dll
LoadedModule[47]=C:\Windows\System32\MSASN1.dll
LoadedModule[48]=C:\Windows\system32\uxtheme.dll
LoadedModule[49]=C:\Windows\System32\MSCTF.dll
LoadedModule[fifty]=C:\Windows\SYSTEM32\WTSAPI32.dll
LoadedModule[51]=C:\Windows\SYSTEM32\WINSTA.dll
LoadedModule[52]=C:\Windows\system32\dwmapi.dll
LoadedModule[53]=C:\Windows\SYSTEM32\DWrite.dll
LoadedModule[54]=C:\Windows\SYSTEM32\dxgi.dll
LoadedModule[55]=C:\Windows\SYSTEM32\d3d10_1.dll
LoadedModule[56]=C:\Windows\SYSTEM32\d3d10_1core.dll
LoadedModule[57]=C:\Windows\SYSTEM32\d3d11.dll
LoadedModule[58]=C:\Windows\SYSTEM32\D3D10Warp.dll
LoadedModule[59]=C:\Windows\system32\SFC.DLL
LoadedModule[60]=C:\Windows\SYSTEM32\sfc_os.DLL
LoadedModule[61]=C:\Program Files\Common Files\Microsoft Shared\OFFICE16\Csi.dll
LoadedModule[62]=C:\Windows\SYSTEM32\PROPSYS.dll
LoadedModule[63]=C:\Windows\System32\clbcatq.dll
LoadedModule[64]=C:\Program Files\Common Files\Microsoft Shared\OFFICE16\ACEOLEDB.DLL
LoadedModule[65]=C:\Program Files\Common Files\Arrangement\Ole DB\oledb32.dll
LoadedModule[66]=C:\Windows\SYSTEM32\MSDART.DLL
LoadedModule[67]=C:\Windows\SYSTEM32\DPAPI.dll
LoadedModule[68]=C:\Program Files\Mutual Files\Microsoft Shared\OFFICE16\ACECORE.DLL
LoadedModule[69]=C:\Plan Files\Common Files\Microsoft Shared\OFFICE16\1033\ACEWSTR.DLL
LoadedModule[70]=C:\Program Files\Common Files\Microsoft Shared\OFFICE16\ACEERR.DLL
LoadedModule[71]=C:\Program Files\Common Files\Microsoft Shared\OFFICE16\1033\ACEINTL.DLL
LoadedModule[72]=C:\Windows\SYSTEM32\XmlLite.dll
LoadedModule[73]=C:\Windows\SYSTEM32\WindowsCodecs.dll
LoadedModule[74]=C:\Windows\SYSTEM32\Secur32.dll
LoadedModule[75]=C:\Windows\SYSTEM32\SSPICLI.DLL
LoadedModule[76]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[77]=C:\Windows\System32\WS2_32.dll
LoadedModule[78]=C:\Windows\SYSTEM32\wbemcomn.dll
LoadedModule[79]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[80]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[81]=C:\Plan Files\Common Files\Microsoft Shared\OFFICE16\ACEES.DLL
LoadedModule[82]=C:\Plan Files\Mutual Files\Microsoft Shared\OFFICE16\VBAJET32.DLL
LoadedModule[83]=C:\Windows\SYSTEM32\MSVCR100.dll
LoadedModule[84]=C:\Program Files\Common Files\Microsoft Shared\OFFICE16\expsrv.dll
LoadedModule[85]=C:\Windows\system32\apphelp.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Microsoft Office Upload Center
AppPath=C:\Programme Files\Microsoft Role\Office16\MSOUC.EXE
ApplicationIdentity=00000000000000000000000000000000
MetadataHash=724759341
Role repairinstallation did not fix the problem
Onedrive is not installed, because nosotros don`t demand it.
This constelation worked for over 2 twelvemonth`s and now information technology doens`t any more...
Any hints, what could cause the problem?
We had the same Problem in December 2021 after installing KB5002099. Removing the KB5002099 solved the Problem. Information technology seems that the January Patch now accept the aforementioned issue. Our Servers installed the KB5002115 (witch replaces KB5002099) and KB5002116 yesterday. Now we take the same problems over again. Removing the KB5002115 (and to exist certain KB5002116) solved the Problem on our Servers. I'yard looking forward to the Feb patch, I'm certain we will have the aforementioned Problem once again. ;)
Hello @hanktank-3419,
Co-ordinate to your description, I would suggest you lot become to this path C:\Users\*<User Name>*\AppData\Local\Microsoft\Office\xvi.0 and delete "OfficeFileCache" folder.
Please make sure that this directory is non synchronized in a RDS farm environment.
Here is a like thread you could have a look 'The Microsoft Upload Middle found a problem while accessing the Office Document Cache".
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you take extra questions about this answer, delight click "Comment".
Notation: Please follow the steps in our documentation to enable eastward-mail notifications if yous desire to receive the related electronic mail notification for this thread.
Deleting this folder does not resolve this particular upshot - there's some specific about KB5002099 that has broken the Office Upload Middle or the Certificate Cache in a central fashion for those of us running RDS farms or similar user virtualization.
0 Votes 0 ·
Hi,
give thanks you for the reply.
The "OfficeFileCache" folders nether C:\Users*<User Proper noun>*\AppData\Local\Microsoft\Office\sixteen.0 get recreated automatically everytime, the upload center app is started.
sadly enough I don`t accept the registry central [HKEY_CURRENT_USER\Software\Microsoft\Part\16.0\Mutual\FileIO] mentioned in the other postal service.
the only registry key I could find is under [HKEY_LOCAL_MACHINE\Software\Microsoft\Office\16.0\Common\FileIO]; I deleted this key, but it does not get recreated again, when I open the upload eye once again...
Hi @hanktank-3419
Thank you for your reply.
Will this issue reproduce after you lot delete the "OfficeFileCache" binder?
This binder would exist generated back if yous apply Upload Eye.
I deleted this key, just it does not get recreated once again, when I open the upload center again...
To go the FileIO registry entry dorsum, please try to salve a file or upload a file to OneDrive or SharePoint Online.
Once I practise one action to a higher place after I delete this FileIO registry entry, it comes back like following image.
Please note, before you do whatever changes to Registry Editor, please remember to support the registry for restoration in example problems occur.
If deleting the "OfficeFileCache" folder and removing the FileIO* registry entry do not piece of work, I would suggest y'all repair Role on Control Panel to have a check.
Besides, please kindly share the Office version number to us. You lot could get to ane Office app > File > Account > Product Information to go this information.
0 Votes 0 ·
Hello,
as already written, nosotros don`t apply onedrive or sharepoint.
Because of that, onedrive isn`t installed on the servers:
I will give it a effort and install the onedrive option in the part setup.
Hopefully this will add teh neccessary function for the office upload center to work properly again.
Office repair installation did not set the problem;
0 Votes 0 ·
Nosotros see the same problem in our RDS surroundings. Problem seems to have started after installing Microsoft Updates from December 20th. Deleting the office enshroud and registry or removing the user profile disk does not solve the problem. The problem merely seems to occur when opening an office document from a UNC path.
hmm, I think we already had the problem before installing the dec patched on the RDS session hosts.
We do have some other single RDS exam server, which is not configured for the apply of "user profile disks".
On this server, with the same softwre patches installed on, nosotros don`t have the problem with the office upload eye...
I don`t know if this could be the root of the problem.
How-do-you-do,
I´1000 withal messing around with this trouble.
For testing I installed ALL the components in the Role 2016 setup, and then OneDrive for Business organisation now is likewise installed.
The origin Problem nonetheless persists.
When I try to first the OneDrive app from the startmenu the office upload center opens with the same errors...
What tf is wrong with the system suddenly? :/
Hello,
aforementioned Trouble over here. Occurred the kickoff fourth dimension afterwards the Office 2016 dec 2021 updates. Only difference: We´re not using RDS merely Windows 10 with VMware Horizon View over Nail Protocol.
Can confirm that the upshot merely appears with files opened from inside a CIFS-Network-Share mapped with a drive letter or a straight UNC-path.
If yous re-create the file to a local drive everything works as expected without any issue.
Deleting the OfficeFileCache folder as suggested in the posting higher up does definitely not help. The fault reappears immediately leaving the application error grand in the consequence log with the following faulty files:
C:\Program Files (x86)\Microsoft Function\Office16\MSOUC.EXE
C:\Plan Files (x86)\Common Files\Microsoft Shared\OFFICE16\Csi.dll
Another hint I've noticed:
If youre using MS-Access-Files theres a new bug using these files via RDS: The Lock-Files (.laccdb) aren't deletetd any more. One of my users had this trouble: He opened an Access-DB over a network path and afterward closing the DB the Lockfile wasn't deleted. He had to delete it by paw so other users could access the DB in the network drive.
Having a look into the folder C:\Users\%username%\AppData\Local\Microsoft\Office\16.0\OfficeFileCache there are also access-files and the lockfile (.laccdb) ist still there.
So i assume that the Upload Center isn't the root cause of this problem but the victim! The existent root cause is the handling of AccessDB-Files after the 2021/12 Office-Patch.
Afterwards opening and endmost an Access-DB the lockfiles aren't deleted any more than which causes the Upload Center to throw an error considering it thinks the AccessDb ist faulty.
Makes that any sense?
Hi Guys,
We are having the aforementioned issue later the updates in December 2021. I'm following and will contribute if I observe a solution. And so far I tin can say we utilize User Contour Disks and have a RDS Farm, users accessing shared documents from sharepoint it crashes the office upload center. I temporarily renamed the exe'southward for the upload center to prevent information technology from opening merely documents notwithstanding won't open from sharepoint and I see its related to "UNC" path. Notwithstanding I do accept a examination RDS farm that does not take UPD'southward and everything seems to work fine.
I have temporarily fixed the issue by removing KB5002099 Office 2016 Patch. I went to https://msrc.microsoft.com/update-guide/releaseNote/2021-Dec first patch listed for Part 2016 was KB5002099 after uninstalling the patch and renaming the exe's for upload center dorsum I'm able to open up sharepoint files and files from our mapped drives.
- Current Folio: Page 1
- Page two
- Page 3
- Side by side Page Adjacent Page
Source: https://docs.microsoft.com/answers/questions/672214/office-2016-upload-center-app-crash.html
just in addition, the KB5002140 from the 02.2022 patchday, which superseeds the KB5002116, does not cause the same problem;
at least not in our case;
0 Votes 0 ·