Legacy App that uses .NET 2.0, Microsoft Office Primary Interop Assemblies v. 11 ... going to Windows 7/Office 2010, and crashing Office 2010!
Friday, June 29, 2012 8:28 PM
Sorry if I posted this in the wrong forum.
I inherited a custom application that was built using Visual Studio 2003 and .NET 2.0. It uses Microsoft Office PIA version 11 (for Office 2003), and it originally ran on Windows XP. The application relies on reading Excel, Word, and Powerpoint files, as well as Outlook for reading .PST files
Now I am trying to get this application to work on a 64-bit, Windows 7 machine that has Office 2010. For the most part, the application works--it correctly reads the .PST files and uploads emails and attachments (along with correct metadata) to a Sharepoint. It's just that after I close the application and try to open Microsoft Office 2010 products (Word, Excel, Powerpoint, Outlook), these programs tend to crash. The error message would say "Microsoft ____ has stopped working."
Looking at event viewer, the logs usually look like this:Faulting application name: OUTLOOK.EXE, version: 14.0.6109.5005, time stamp: 0x4e79b881
Faulting module name: ntdll.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba58
Exception code: 0xc0000005
Fault offset: 0x0002e3fb
Faulting process id: 0x1b20
Faulting application start time: 0x01cd5631d6ed41d9
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office14\OUTLOOK.EXE
Faulting module path: C:\WINDOWS\SysWOW64\ntdll.dll
Report Id: 2f11010e-c226-11e1-8b8d-9cb70de93ccf
After doing lots of browsing, I am guessing that it has to do with the application referencing PIA version 11 for Office 2003, and the version that I have on this computer is PIA version 14 for Office 2010. Also, I am 100% sure that it's this application that is causing Office 2010 applications to crash since it happens every time I run that legacy application. Restarting the computer fixes these crashes but I would rather not have to restart every time I run this application!
Short of actually updating the source code, is there anything I can do to fix this problem? I don't actually have the source code files (nor do I have access to Visual Studio!) since the person who wrote this was a vendor.
Thanks for your time.
- Edited by msftcat Friday, June 29, 2012 8:28 PM