microsoft office document cache upload center error repair
Office 2022 Upload Centre app crash
Hello,
we are using Role 2022 x64 on a MS RDS farm.
Since a few days nosotros get this error, when the office upload center is opened:
When you klick repair, the app crashes:
The eventlog shows this:
Version=one
EventType=APPCRASH
EventTime=132845469423146914
ReportType=two
Consent=1
UploadTime=132845469425137015
ReportIdentifier=64a169ea-6233-11ec-aadf-005056b72471
IntegratorReportIdentifier=64a169e9-6233-11ec-aadf-005056b72471
AppSessionGuid=00004378-0009-02d3-f465-fe1440f6d701
TargetAppId=W:00001d0810c4ef12850bd4374d80fa9f7d260000ffff!00004e0a549249f0c35aeaad337d9915afd81048aefb!MSOUC.EXE
TargetAppVer=2016//09//thirteen:xix:06:38!ada64!MSOUC.EXE
BootId=4294967295
Response.type=iv
Sig[0].Proper noun=Application Name
Sig[0].Value=MSOUC.EXE
Sig[1].Proper noun=Awarding Version
Sig[i].Value=16.0.4444.thou
Sig[2].Name=Application Timestamp
Sig[2].Value=57d84e3e
Sig[3].Proper name=Error Module Name
Sig[3].Value=Csi.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=16.0.4687.thousand
Sig[5].Name=Mistake Module Timestamp
Sig[5].Value=5ac3c128
Sig[six].Proper noun=Exception Code
Sig[vi].Value=c0000005
Sig[7].Proper noun=Exception Get-go
Sig[7].Value=00000000001c4084
DynamicSig[1].Name=OS Version
DynamicSig[i].Value=10.0.14393.2.0.0.144.8
DynamicSig[two].Name=Locale ID
DynamicSig[ii].Value=1031
UI[2]=C:\Programme Files\Microsoft Function\Office16\MSOUC.EXE
UI[iii]=Microsoft Part Upload Eye has stopped working
UI[iv]=Windows can bank check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution after and close the program
UI[7]=Close the programme
LoadedModule[0]=C:\Program Files\Microsoft Role\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[iv]=C:\Windows\System32\KERNELBASE.dll
LoadedModule[5]=C:\Windows\System32\ucrtbase.dll
LoadedModule[vi]=C:\Windows\System32\ADVAPI32.dll
LoadedModule[vii]=C:\Windows\System32\msvcrt.dll
LoadedModule[8]=C:\Windows\System32\sechost.dll
LoadedModule[ix]=C:\Windows\System32\RPCRT4.dll
LoadedModule[x]=C:\Windows\System32\ole32.dll
LoadedModule[11]=C:\Windows\System32\combase.dll
LoadedModule[12]=C:\Windows\System32\bcryptPrimitives.dll
LoadedModule[13]=C:\Windows\System32\GDI32.dll
LoadedModule[14]=C:\Windows\System32\gdi32full.dll
LoadedModule[fifteen]=C:\Windows\System32\USER32.dll
LoadedModule[16]=C:\Windows\System32\win32u.dll
LoadedModule[17]=C:\Windows\SYSTEM32\VCRUNTIME140.dll
LoadedModule[xviii]=C:\Windows\SYSTEM32\MSIMG32.dll
LoadedModule[xix]=C:\Program Files\Microsoft Part\Office16\MSOHEV.DLL
LoadedModule[twenty]=C:\Windows\SYSTEM32\MSVCP140.dll
LoadedModule[21]=C:\Windows\SYSTEM32\VCRUNTIME140_1.dll
LoadedModule[22]=C:\Windows\System32\IMM32.DLL
LoadedModule[23]=C:\Program Files\Common Files\Microsoft Shared\Office16\mso20win32client.dll
LoadedModule[24]=C:\Windows\System32\OLEAUT32.dll
LoadedModule[25]=C:\Windows\System32\msvcp_win.dll
LoadedModule[26]=C:\Programme Files\Common Files\Microsoft Shared\Office16\mso30win32client.dll
LoadedModule[27]=C:\Plan Files\Common Files\Microsoft Shared\Office16\mso40uiwin32client.dll
LoadedModule[28]=C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.ane.14393.4770_none_aecd7b51ddd26054\gdiplus.dll
LoadedModule[29]=C:\Program Files\Mutual Files\Microsoft Shared\Office16\mso99Lwin32client.dll
LoadedModule[30]=C:\Windows\SYSTEM32\SLC.dll
LoadedModule[31]=C:\Windows\SYSTEM32\sppc.dll
LoadedModule[32]=C:\Programme Files\Common 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.mutual-controls_6595b64144ccf1df_6.0.14393.4169_none_7de0bbf28341b1f2\Comctl32.dll
LoadedModule[44]=C:\Plan Files\Microsoft Office\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:\Plan Files\Common Files\Organisation\Ole DB\oledb32.dll
LoadedModule[66]=C:\Windows\SYSTEM32\MSDART.DLL
LoadedModule[67]=C:\Windows\SYSTEM32\DPAPI.dll
LoadedModule[68]=C:\Program Files\Common Files\Microsoft Shared\OFFICE16\ACECORE.DLL
LoadedModule[69]=C:\Program Files\Mutual 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:\Program Files\Common Files\Microsoft Shared\OFFICE16\ACEES.DLL
LoadedModule[82]=C:\Program Files\Common 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
Land[0].Fundamental=Ship.DoneStage1
State[0].Value=i
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 non set the problem
Onedrive is not installed, because we don`t need information technology.
This constelation worked for over two year`s and now it doens`t whatsoever more...
Whatsoever hints, what could cause the trouble?
We had the same Problem in Dec 2022 after installing KB5002099. Removing the KB5002099 solved the Problem. Information technology seems that the January Patch now have the same issue. Our Servers installed the KB5002115 (witch replaces KB5002099) and KB5002116 yesterday. Now we have the same problems over again. Removing the KB5002115 (and to be sure KB5002116) solved the Problem on our Servers. I'm looking forward to the Feb patch, I'm certain we will have the aforementioned Problem once again. ;)
Hi @hanktank-3419,
According to your description, I would suggest you go to this path C:\Users\*<User Proper name>*\AppData\Local\Microsoft\Role\16.0 and delete "OfficeFileCache" binder.
Please make certain that this directory is not synchronized in a RDS farm environment.
Here is a like thread yous could have a look 'The Microsoft Upload Center found a trouble while accessing the Office Certificate Cache".
If the answer is helpful, please click "Accept Reply" and kindly upvote information technology. If y'all have extra questions about this answer, please click "Comment".
Annotation: Please follow the steps in our documentation to enable electronic mail notifications if you want to receive the related email notification for this thread.
Deleting this folder does not resolve this item issue - there's some specific about KB5002099 that has broken the Part Upload Middle or the Certificate Enshroud in a fundamental mode for those of u.s. running RDS farms or similar user virtualization.
0 Votes 0 ·
Hi,
thank you for the respond.
The "OfficeFileCache" folders under C:\Users*<User Name>*\AppData\Local\Microsoft\Function\sixteen.0 go recreated automatically everytime, the upload heart app is started.
sadly enough I don`t take the registry key [HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\FileIO] mentioned in the other post.
the only registry key I could discover is nether [HKEY_LOCAL_MACHINE\Software\Microsoft\Office\sixteen.0\Common\FileIO]; I deleted this key, but it does not go recreated again, when I open the upload center again...
How-do-you-do @hanktank-3419
Thank you for your respond.
Will this issue reproduce after you delete the "OfficeFileCache" folder?
This folder would exist generated back if y'all use Upload Eye.
I deleted this central, just information technology does not get recreated again, when I open up the upload center again...
To get the FileIO registry entry back, delight try to save a file or upload a file to OneDrive or SharePoint Online.
Once I practise one activity above subsequently I delete this FileIO registry entry, it comes back similar following epitome.
Delight note, before yous do whatsoever changes to Registry Editor, please remember to support the registry for restoration in example problems occur.
If deleting the "OfficeFileCache" binder and removing the FileIO* registry entry do not work, I would suggest you repair Part on Command Panel to have a check.
Besides, please kindly share the Function version number to us. Yous could go to one Office app > File > Business relationship > Production Information to get this information.
0 Votes 0 ·
Hello,
as already written, nosotros don`t use onedrive or sharepoint.
Considering of that, onedrive isn`t installed on the servers:
I will requite it a effort and install the onedrive option in the office setup.
Hopefully this will add together teh neccessary function for the office upload heart to work properly once again.
Part repair installation did non fix the problem;
0 Votes 0 ·
We run into the same trouble in our RDS environment. Problem seems to have started later on installing Microsoft Updates from Dec 20th. Deleting the role cache and registry or removing the user profile disk does not solve the problem. The problem only seems to occur when opening an office certificate from a UNC path.
hmm, I think we already had the problem before installing the dec patched on the RDS session hosts.
We practice have some other single RDS test server, which is non configured for the use of "user contour disks".
On this server, with the aforementioned softwre patches installed on, we don`t have the problem with the office upload middle...
I don`t know if this could exist the root of the problem.
Hello,
I´m still messing around with this problem.
For testing I installed ALL the components in the Part 2022 setup, so OneDrive for Business organization now is likewise installed.
The origin Problem notwithstanding persists.
When I try to start the OneDrive app from the startmenu the office upload center opens with the same errors...
What tf is wrong with the system of a sudden? :/
How-do-you-do,
same Trouble over hither. Occurred the showtime time after the Function 2022 december 2022 updates. Only divergence: We´re non using RDS merely Windows 10 with VMware Horizon View over Blast Protocol.
Can confirm that the result only appears with files opened from within a CIFS-Network-Share mapped with a drive alphabetic character or a direct UNC-path.
If you copy the file to a local bulldoze everything works as expected without any issue.
Deleting the OfficeFileCache folder every bit suggested in the posting above does definitely non help. The error reappears immediately leaving the application error 1000 in the issue log with the following faulty files:
C:\Program Files (x86)\Microsoft Function\Office16\MSOUC.EXE
C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE16\Csi.dll
Another hint I've noticed:
If youre using MS-Access-Files theres a new problems using these files via RDS: The Lock-Files (.laccdb) aren't deletetd any more. One of my users had this problem: He opened an Admission-DB over a network path and later endmost the DB the Lockfile wasn't deleted. He had to delete information technology past manus and then other users could admission the DB in the network bulldoze.
Having a look into the binder C:\Users\%username%\AppData\Local\Microsoft\Role\sixteen.0\OfficeFileCache there are as well admission-files and the lockfile (.laccdb) ist nevertheless there.
And so i assume that the Upload Center isn't the root cause of this trouble merely the victim! The existent root cause is the handling of AccessDB-Files after the 2021/12 Office-Patch.
Later on opening and closing an Admission-DB the lockfiles aren't deleted any more which causes the Upload Center to throw an error considering it thinks the AccessDb ist faulty.
Makes that whatsoever sense?
Hi Guys,
We are having the aforementioned consequence after the updates in December 2021. I'm following and will contribute if I find a solution. So far I can say nosotros utilise User Profile Disks and accept a RDS Farm, users accessing shared documents from sharepoint it crashes the office upload heart. I temporarily renamed the exe'south for the upload middle to prevent it from opening only documents still won't open from sharepoint and I come across its related to "UNC" path. Nevertheless I do have a test RDS farm that does not take UPD's and everything seems to work fine.
I have temporarily fixed the issue by removing KB5002099 Role 2022 Patch. I went to https://msrc.microsoft.com/update-guide/releaseNote/2021-December get-go patch listed for Office 2022 was KB5002099 later on uninstalling the patch and renaming the exe's for upload center back I'grand able to open sharepoint files and files from our mapped drives.
- Current Page: Page 1
- Page two
- Page 3
- Next Folio Next Folio
Source: https://docs.microsoft.com/answers/questions/672214/office-2016-upload-center-app-crash.html
simply in add-on, the KB5002140 from the 02.2022 patchday, which superseeds the KB5002116, does not crusade the same trouble;
at least non in our example;
0 Votes 0 ·