Problem (APPCRASHES) with 64-bit Add-In for MS Word 2010 x64

Add-in Express™ Support Service
That's what is more important than anything else

Problem (APPCRASHES) with 64-bit Add-In for MS Word 2010 x64
 
Grey Wolf




Posts: 6
Joined: 2009-09-20
I'm using Add-In-Express for VCL Version 7.1 Release (build 1211), along with Delphi XE2 SP4, with installed bug fix for EventDispatchInvoke function in System.Win.ComObj.pas unit (thank you for providing this fix). I need to add support for MS Word 2010 64-bit to my Add-In. For this goal, I've created a 64-bit Add-In Stub in Delphi XE2 SP4. This Add-In stub is successfully loaded into MS Word 2010 64-bit, Ribbon Tab with my buttons is shown in the appropriate Ribbon pane, and buttons work as expected. I decided to leave the main functionality of my Add-In in 32-bit DLL which was written in Delphi 7, in order not to revise and edit all source code to make it compatible with 64-bit compilation mode. So I just invoke my 32-bit main Add-In DLL via using CreateOleObject function to get COM Object interface which do actual work. My 32-bit DLL gets loaded into address space of DllHost.exe process, marshalling of standard types is performed automatically. When invoking these functions from within MS Word, all works fine. I also have a separate 32-bit batch converter (EXE), which allows users to perform operations on MS Word files in batch mode. When user presses "Go" button, this stand-alone batch converter creates an invisible instance of MS Word via CreateOleObject, iterates through list of loaded Add-Ins, finds my Add-In, and invokes functions from it on every document which must be processed. The problem is that when I try to test this function with 64-bit MS Word 2010 and 64-bit Add-In, sometimes MS Word just crashes due to obscure reason. Sometimes batch mode runs without errors; sometimes crash occurs immediately after loading MS Word 64-bit with my Add-In; sometimes crash occurs after processing of all files during closing MS Word and unloading of My Add-In. In Standard MS Windows Application Event Log, I can see reports about these crashes.

The problem is that I do not have experience in debugging APPCRASH logs, and do not see what should I do with this information. Could you suggest any steps that would help to troubleshoot this situation?
Posted 24 Jul, 2012 01:59:38 Top
Grey Wolf




Posts: 6
Joined: 2009-09-20
In Application Event log, crashes messages look like this:

Version=1
EventType=APPCRASH
EventTime=129874366878606963
ReportType=2
Consent=1
ReportIdentifier=accac604-d3ff-11e1-a24e-d04ff1b6ac1d
IntegratorReportIdentifier=accac603-d3ff-11e1-a24e-d04ff1b6ac1d
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=WINWORD.EXE
Sig[1].Name=Application Version
Sig[1].Value=14.0.4762.1000
Sig[2].Name=Application Timestamp
Sig[2].Value=4bae25cd
Sig[3].Name=Fault Module Name
Sig[3].Value=msvcrt.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=7.0.7600.16930
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=4eeb01e3
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=00000000000012a1
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7600.2.0.0.256.1
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=8695
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=8695d77f60aada5aa17d252d23262d39
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=8d25
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=8d25499b29747616764b49ab71dd8638
UI[2]=E:\Program Files\Office2010x64\Office14\WINWORD.EXE
UI[3]=Microsoft Word has stopped working
UI[4]=Windows can check online for a solution to the problem and try to recover your information.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=E:\Program Files\Office2010x64\Office14\WINWORD.EXE
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\system32\kernel32.dll
LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll
LoadedModule[4]=C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4926_none_08e1a05ba83fe554\MSVCR90.dll
LoadedModule[5]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7600.16661_none_a44e1fc257f685f6\Comctl32.dll
LoadedModule[6]=C:\Windows\system32\ADVAPI32.dll
LoadedModule[7]=C:\Windows\system32\msvcrt.dll
LoadedModule[8]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[9]=C:\Windows\system32\RPCRT4.dll
LoadedModule[10]=C:\Windows\system32\GDI32.dll
LoadedModule[11]=C:\Windows\system32\USER32.dll
LoadedModule[12]=C:\Windows\system32\LPK.dll
LoadedModule[13]=C:\Windows\system32\USP10.dll
LoadedModule[14]=C:\Windows\system32\IMM32.DLL
LoadedModule[15]=C:\Windows\system32\MSCTF.dll
LoadedModule[16]=E:\Program Files\Office2010x64\Office14\wwlib.dll
LoadedModule[17]=C:\Windows\system32\ole32.dll
LoadedModule[18]=C:\Windows\system32\OLEAUT32.dll
LoadedModule[19]=E:\Program Files\Office2010x64\Office14\gfx.dll
LoadedModule[20]=C:\Windows\system32\WTSAPI32.dll
LoadedModule[21]=C:\Windows\system32\MSIMG32.dll
LoadedModule[22]=E:\Program Files\Office2010x64\Office14\oart.dll
LoadedModule[23]=C:\Program Files\Common Files\Microsoft Shared\office14\mso.dll
LoadedModule[24]=C:\Windows\system32\msi.dll
LoadedModule[25]=C:\Windows\system32\SHLWAPI.dll
LoadedModule[26]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16661_none_fa62ad231704eab7\Comctl32.dll
LoadedModule[27]=C:\Program Files\Common Files\Microsoft Shared\office14\Cultures\office.odf
LoadedModule[28]=E:\Program Files\Office2010x64\Office14\1033\wwintl.dll
LoadedModule[29]=C:\Windows\system32\uxtheme.dll
LoadedModule[30]=C:\Program Files\Common Files\Microsoft Shared\OFFICE14\MSPTLS.DLL
LoadedModule[31]=C:\Windows\system32\dwmapi.dll
LoadedModule[32]=C:\Program Files\Common Files\Microsoft Shared\office14\riched20.dll
LoadedModule[33]=C:\Program Files\Common Files\Microsoft Shared\office14\MSORES.DLL
LoadedModule[34]=C:\Program Files\Common Files\Microsoft Shared\office14\1033\MSOINTL.DLL
LoadedModule[35]=C:\Windows\system32\mscoree.dll
LoadedModule[36]=C:\Program Files\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform\OSPPC.DLL
LoadedModule[37]=C:\Windows\system32\CRYPTBASE.dll
LoadedModule[38]=C:\Windows\system32\Winspool.DRV
LoadedModule[39]=C:\Windows\system32\SXS.DLL
LoadedModule[40]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[41]=C:\Windows\system32\rsaenh.dll
LoadedModule[42]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[43]=C:\Windows\system32\CLBCatQ.DLL
LoadedModule[44]=C:\Windows\system32\SHELL32.DLL
LoadedModule[45]=C:\Windows\system32\VERSION.dll
LoadedModule[46]=C:\Windows\system32\propsys.dll
LoadedModule[47]=C:\Windows\system32\ntmarta.dll
LoadedModule[48]=C:\Windows\system32\WLDAP32.dll
LoadedModule[49]=C:\Windows\system32\SETUPAPI.dll
LoadedModule[50]=C:\Windows\system32\CFGMGR32.dll
LoadedModule[51]=C:\Windows\system32\DEVOBJ.dll
LoadedModule[52]=C:\Windows\System32\msxml6.dll
LoadedModule[53]=E:\Program Files\Office2010x64\Office14\msproof7.dll
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Microsoft Word
AppPath=E:\Program Files\Office2010x64\Office14\WINWORD.EXE
Posted 24 Jul, 2012 02:05:30 Top
Andrei Smolin


Add-in Express team


Posts: 18818
Joined: 2006-05-11
Hello,

The whole composition looks a bit complicated.

On the log. The faulting module name is msvcrt.dll, the exception is c0000005 = "Access violation". Latest Word updates aren't installed; this may or may not be essential. I don't know how to debug this. No ideas, absolutely. Anyway, I'd install all latest updates. Just in case.


Andrei Smolin
Add-in Express Team Leader
Posted 24 Jul, 2012 09:45:58 Top
Andrei Smolin


Add-in Express team


Posts: 18818
Joined: 2006-05-11
Also consider revising your 32-bit code and creating a full-scale 64bit add-in in order to avoid potential problems at bitness/process borders.


Andrei Smolin
Add-in Express Team Leader
Posted 24 Jul, 2012 10:06:47 Top
Grey Wolf




Posts: 6
Joined: 2009-09-20
Thank you, I'll try to install the latest updates for MS Word, and then see whether the problem will remain.
Posted 25 Jul, 2012 11:58:11 Top