TekServer
asked on
Outlook 2007 hangs and/or crashes on specific messages
I have a client that is having a problem with just a few messages in Outlook. When these messages are opened, either with the Reading Pane or by double-clicking, it takes 45-60 seconds for the message to open, during which time Outlook is completely unresponsive (additional clicking will yield the all-too-familiar "Not Responding" in the title bar until the message finishes opening). Once open, the message can be browsed and the attachment opened with no hesitations or delays, but Outlook crashes on any attempt to Reply or Forward (the crash doesn't occur until you hit "Send").
I thought at first it was an attachment issue: each of the affected messages has an attached Excel spreadsheet that is about 600 KB in size. But I don't think that's the issue, because there are other messages in the same mailbox with similar Excel attachments that open up immediately.
I've compacted the .pst file, run the Office Diagnostics, reregistered ole32.dll (some of the messages had tables in them, so I thought that might be relevant at the time) and ensured that all the latest patches and service packs are in place. I've tried restarting Outlook in Safe Mode. I even defragged the hard drive (desperation move). None of this made the slightest difference.
I dug through the message headers, and compared them to headers in other messages that open immediately, and I found one consistent difference that I think may be relevant: In the affected (slow to open) messages, the "Thread-Index" header is HUGE. Here is a sample of the Thread-Index header from one of the affected messages:
Thread-Index: AcjiFIEKqRcCkJDiTP6aECNc4B gHRQAsv+Vt AC9RqBoABj kHTQCGJhE9 AAIABCMAB1 tZNgADJCUd ACr3kJgABs EmXQAmaqpt AAhaLCIALI /0WAAGwuHE ACuZRqYACQ aLawCJjn46 AAU3pb0AA/ qA+wAC5IwD E3XAKKYNkl h0GQAv5CLg BrGtjR0AIa oqWgAAGJkw AAQnZXkAk0 EQEgAIsOIM AASykqQAAF T8bQCLH9/c AAM6iNoABn /S8QAA6Gy3 ACPjyNcABZ 1aOQAAsmtY AATxcHsAA7 bqFwAA+uHA ACdbSlQABV g8fgACq42u AAFZ/bAAKf 2//wAAWEGJ AABcYCoAAe 3AtQAyW1VM AARzZ2EAAu REQwDtE8Qe ADSRIZ4AA0 IK4AACyI9H AABWURkAAT XySADzdrl8 ADJHTqAABt t0mwABQvpn AO5YnXUAAJ OLUAAAA/qQ AAGijuoADE j+TwAlquwj AAhbIToAKy r/tgAB/Kfx AAArU48AK/ 8liAA6rBpr AAgyp2kAiB kvUwAAiQLw AADmH44ADQ 0QIAAm0bfs AAUckQUAXg tbtQAB2jPi AAp2BM0AuY fNowALndbj AAJkOnMAAq 61hgAktb/g ADDvXNoACa RDigACCnpC ACgoFq0AAe 5h0QAAMYYJ AAZU+YcAKN 4CzgAL/Wpu AL/5cwcAB1 QHJQACe4Me ACjV+44ABz WRDAACNa5l ACJ68xAABD bCyQAFzNOH AATpFPAABD /LUQAfuFq1 AAOSbYIAAM y8ogAFvxcN AAkBJ8wAhC KI1gACdvr6 AAH4vskAAF CMXAALLjac ACU2orsALj WCJwAAWwC2 AASvFbsACA jezQAAMEUu AAP2tKUAK2 ahuwAdHTGw AKe5E48ALy ozaQABNyT3 AAfIHlcAAB y8kwABY45/ AC+HT5gAA8 TE+gAqXw7q ADE3SAwABT 0CpgCQ7icL AAEE+6gABY tY2QAEraKl AC6c9UAA
LVo1WAAEx7bcAASK9woAKIYG5Q AFhlCzAAVf +J8AJhybLQ CbS28mAC1E anoABkONKQ ACykJIAAOg eU8AJCbjPA AGrPskAAgj TD0AVhAAdg CYllgSAASY gw0AA3Rrzg ADTQf3ACPa ZlEACEg2xw ABrVsmAAWv xL8AI9UwRw AGc4jGAAHi 7GEAJ/l/CQ AIQC/yAATT wyYALb8cng ADZ52tAAR3 OhkAh1+fsw AJAyooAAex Lq4AK39R6w Ao7GKUAACX X8cAACSKqg AArb0bAAog cq4AAFsoRA Ao82chAAW+ qPwABdsO/w ABzPpoAADl UMIAuD3RcQ AAXMDXAAQq xoYAA7QmPA AAdZ+7AAaK NSMAKryVww AD+2dCAC1c yDkABDTNjg AAU14aACTi LHsACduMjg AFSMaxAAFm n/AAIgKg1w AEL/mmAAGf aIoAC+DPnQ C2u9x6AACD j1QABoTumQ AxTcnbAGL2 EuoABbH9Nw AAixHoAAhW hXMAhtC9ag AKHrqpAC4v TIwABb5grQ AvZ+vvAAKw 4fQAAFoF0Q AtWmJFAAQa CPEAJcVRFw ACVMv9AACw SnMAAgTing AGKd1jAAB+ 3jIAA56udA CI1ahiAAeW q4IAAIxWZw AE36WOACmt uXYALly2tw AH1t7iAAIW SVcAKhWsag ACL+l0AAxo 6EcAISGKkA ANZRd4AAEJ wUQAjZSCjA ADG8/XAAF+ S7EAAUEUvg AnQWxuAAdb WqAABEbosA AluF8tAA4I X2sAAIRTWg ArgBYwADRp Tt0AjHu9QA ACgfG+AAB5 aFwAAqQg6A AD1dNfAAFF s4UAAFDKYA AB4Ej0AABL wuoAYX1jZQ ABojHbADII 9vQABX42qQ AAhUQxAhmP QjQACkIyLA ADQKKBAAJm MEYAJLiB9w AAfbrtAASo iWEAATir2Q ABfc7SAAIv JrgAAcUPjQ AoLcASAAMO S/IABr/ujQ Au2JSGAAA/ 9kgABJNrKw Ar9uyxAAFq TH
EAjVbyLgABDCFbAC/RB/YAALB9 rAAMfpTLAC afXxUAAxtA 3AABFRbGAA MiUesAAG6i MAArYsF6AA 4P6NcAKC9m 9AAEmJ0tAA ESASkAAayr pgACOE7IAI iLDNsAAiq2 kQAFYaRAAA ExtDoAAgJe TAAA19wNAA NT+oYAIQVp mgAJcJdPAV jrpVgAAVR4 kwABDad8AA qyIOcAAiFZ CwAhpQBQAA BTKE4AAJme SQABOffBAC 66c7YANGhD ewAKDgGIAA UVf20AhksA 7gAC0G3bAA IaYUMAANqQ sQAK7/eYAC K0hIYABwru IwAA2FaPAA JUFsgAKRDn lAAMRaDmAC SVJJAAAOgE xwAI+NDsAA ER4G0AKROv mgAHZOBkAA H25IsAjeHn /AACLK8vAA RSeewAAR2A LQBevwFYAA Egq5oAB5LY 5gACTQcAAC K3fNMABSBA 6QACiqMQAA JXstMAJzTj ZgAM1TGzAA Hn3xEAAGiJ XQCJD+ZCAA ckfpsAAFZL wAABjQ5xAA Cgqi0AAh78 PgAE0RhCAA C4itcAH/zj 5QAB90lRAA BEdd8AC1xL ngAEBpbqAC K/an0AAExR KQABixYoAA ilWAEAKVTJ OQACADXVAD fI5fAABh79 1wCJm51PAA CYyY8ACPqk XwABnhHTAA FGhoUAI7dP HgAH8WcmAA BkEEEABPHX ugAn7a8AAA gEZhoAA0hG cgABodSiAC rvYmYAAbeA swAsOhlEAA L2vmcACReQ ZACEvSJbAA RPDW8AAqNF DAAFyV+LAA OLxUwAIe9D ZAADBw30AA r+BnMAJoY/ HgAHCqSMAA VpHsoAJGDn GAAATv22AA CaJ9oAAJvw vgABISAHAA BnYhwAB6FH 8QA1fMXiAJ S7UJoAJ2ZG lAACxFnvAC +BknsAAE4T OwAI6jQTAA AxcSgAKQfO bgAHcn4nAA Z97ysAKEuB +gAEhg2FAA LbKXQAAJbc GgAA77g5AA CpNMUAh4iU JAAC923lAA Wm
nXEAALroGQACZtn1AAF5DR0AJp CY5gADi/5j AAAfglEACb qDpQADByoV ACE9rPYAM5 8irAABod23 AAHOsfYAAP x08QAtSHZH AAjFNIoABO IwfQCHco7C AADZRFEAAB 6PZwAC+dJ5 AAHDJvMAAS Nw9wAEG8cr AAGHKFEABO npVQAJ4FWC ABognDQAB+ WOBAAAr19e AAAy3c0ABZ nf4AAiW8zV AAG2Vb0APH uY2QAAwa0O ACz9GmQACA gRkAABhCkZ AAJop5EAhc h2xAACmjL/ AAVuCJMAAk GsMAADvapw AABfU2YAJU u55wAAjvWV AA3QRYcAAI EgeQBUEC2C AA1D4jcALM c6AwAEaK0W AIp6+2UAAT nfewAF0HSW ACfgXNEAAz zmTwALzGlT AACimwUAKK Fw0QAHdfN7 ACrqHDAAAD HOygAscOOi AANJMSYACO CENQCUiO2i AAE6DM8AA8 pysAACfktr AAB8PTEAIL qe1QAJSXZL AABJjoQAAE nJyAAsxB1E AAfxLOkAA+ tGcwArcDkb AC/Y3U4ABH IkXQCNEI6m AAI3tuoALe xUiwAEnXg5 AAjG8tMAKu 9iwwAEUXBH AAKYtDQABM Z1kwAjDbYr ADH1jGwAA5 wewwABQD/Y AAP4gQ8Ajk TiowA3dIPj ACxG5GAAAb YodgAGJhzt AAIrac0AMa 7jBAAFCRFf ACSLzVgAB5 GWrgACr1cs AI3ToC8ACS PiLAABjDAZ AAE9jDIABY 6hxgAhEuQo AAj6I9kAMP DLAQAFBJfv ACPloDgABn Is6QACyWXW AAbObH4AK2 XxfwACmYMd AAHoF9oAAy mgPQAA2OYI AIYqjSAAAu zvrgAAf2CM AAggMFUALh Go3AADUnPs AANXhTEAL6 WJMgAEbTWz ACJbEKQAA1 W+bAAA1srr AAlLBaIAAp QVwgAhmR64 AADH240ABU OUtQAFvEv6 AL7EA3gABv 7RDQAuzTfi AAVoY80AB/ txFgAnbBXw AA
JBhykAM/57SgCP/hWFAAH0srQA LES42AABTb syAAGvZJsA CDbLCwAAJl 2oAACBHk0A BDpD/QAihU +yAAA2/jkA CONRWAACRL t9AAB10hwA AM+27wDzyb cGAAB4hCUA BmWOKwAp7Y k8AAS7Ze8A AH4qLwAF5r SgAAHPeykA ASzYdABUv8 MdAAhgMoMA BHP3UwABOZ VrAC39mhoA lZff0gADdo ZyAAIDFKQA LFcQngAAwR CXAAMy9IwA ARoIrQAsX6 5HAAKV6HkA BgNzZAAkpJ /7ADJ/FGAA CC+mIQCbxX OfAC3ppqYA ATcKVQAy5a mwAANhFi4A HoDmawA4fA hFABEWRzcA ge0KXAAE/9 00ADLOHq8A ClYrGAJ9/a vdAAgc7T0A AzgU0AAFvg DpAC2MLAwA LiD3HQAElW YBAAEd8vkA AHvtkgAC6u KcAOmaHxIA ASwN+gAKOL YSAASk4LIA MCnUugAA2z QgAANPzUkA LHAFcAAAsM eoAAC1M9cA ATnwwgAnfU M2AAkDBqAA KGUP7gANTF coALlkcNsA DHeKGgAA9I CGAAWGboEA KbpXIQACFK C3ADE4WOsA AYVvdAAE87 mfACOXGRQA Cr88LQABZB LlAAH1JMYA jtjgZgABiw KfAAC2IBkA AWBnYQAj9q 4WAAn5BaAA KJykqQALj6 NOAAQaVOkA IyGvpQAARH MUAADhT5MA CbJBYAABKP vGADA0w4AA BiAmcwCP5k v4AAJj5xIA BZx2vwAsL+ W5AAIzbf0A MI8aSwAAU3 8yAATKfJoA AU8QOwAo4L 7sAAYZ25wA Jn7D1QCUbx WpAAlRx1wA BOf1SgAi1e K7AAkDBo0A A4mYtgABnu q5AAPXUF8A IKiYbgAEMh NaAAgqGVgA LH01BwAEDz 1/AAcdQYQA LeKdPgCK41 UdAArAqBYA M9UV1gAAjk DXACP8L6oA AbP6rgAAv3 NbAAZQIHIA LiaYfwAIle rdAAIo5bMA JOzafwAHS/ vS
AJqg3foAAMui7gAp4HTZAAgrJC YAAUzqYgAA 7fINACRkF3 wADYa+iAAl IXssAAgmUP IAAq079QAF EaXtACki3E QAAJZ/dQCZ xhr1AAEyd7 UAAgy35gAl GCa6AAXQMf 4ABzdXkQAp CqrgAAYCTc 4AKVriBAAG /8znAACsiv kAArdyzwAB hFbdAAGPog 8AKEb0RwCa ziHbAAIBMi kAAZRRSAAx LLydACkKeV gABul7kwBc qqciAAk1x5 oAAuIQkACS 8I47AAC4IR MAMjiDEAAx lmZJAC9jHq kAJ4/E/AAJ 79OxAAd3jF 8AAZ1bMAAA 4VuoAIOSgu 8AANufIgAD MrYsAAnNbQ wALIpW3gAF 9tqaAAFxpH sAKLKwBwAH 40FBAAC/NI YALFRiYQAF bHSZACQ3go MADFyIQgAB tDfIAImc+e QACN3ZNgAE 1GvlACrYNj MACiRsbgAA J1afACSnRc UAAHLjbQAA t/x9AAsIwK gAAYYI9gAt CsRRAARcKG kAuzPYUAAC 40fUAAgwVV 4AAko2rgAA h1+RAC+4UY 4AAfIAmwAl TuldAAF0tc 8ACslcsAAx MuAjAADnOI oAJzzRpQAG pRGgAAK0a+ 4AjsbxRAAG jHrAAAJdF+ 8AAVv1hAAA iFEAAC3xkO oAAOkhPgAq W8kNAADBhj wAB4cz7AAE hoGdAAC7z/ QAJLE06AAI M181AAHmA7 8ABC4CjQAo dLNRAAPNya kAitL20gAJ sHKgAARqV/ kAAY1V3gAA 6MgKACJA0P MACtHiVwAy GvnLAANH6f I=
Now, I'm no authority on e-mail headers, but I'm pretty sure this isn't normal. A little Google research revealed that this header is apparently used by Microsoft mail servers (i.e. Exchange) to track a threaded conversation - a chain of replies and forwards and such. Based on the contents of the e-mail (which doesn't show a long chain of replies or forwards at all) and from what I could tell from the Google results, this header should be much, MUCH shorter.
But that's where I'm stalled. I have no idea what to do about this. As far as I know, other recipients of this message aren't having the same problem, so I'm reluctant to start pointing fingers at the sender. On the other hand, the recipient wouldn't have anything (directly) to do with this header, would it?
And for that matter, I'm not completely certain that this header is what's causing the symptoms. I mean, it seems to be the most likely culprit. So, if anyone has any suggestions, either for alleviating the symptoms or for dealing with the over-sized Thread-Index header (which will, hopefully, alleviate the symptoms), I am all ears.
:)
P.S. I don't have direct physical access to this machine; but I can do just about anything we might need to do remotely through TeamViewer (the machine is in a somewhat distant geographical location). I can get physical access if it becomes necessary, but it will take a bit of time. Also, for the convenience of the user, I'm mostly working on this after hours. On top of that, I have a number of school projects coming due this weekend. So my follow up responses may be a little slow, and may come at odd hours. Bear with me! Oh, and thanks in advance for your help! ;)
I thought at first it was an attachment issue: each of the affected messages has an attached Excel spreadsheet that is about 600 KB in size. But I don't think that's the issue, because there are other messages in the same mailbox with similar Excel attachments that open up immediately.
I've compacted the .pst file, run the Office Diagnostics, reregistered ole32.dll (some of the messages had tables in them, so I thought that might be relevant at the time) and ensured that all the latest patches and service packs are in place. I've tried restarting Outlook in Safe Mode. I even defragged the hard drive (desperation move). None of this made the slightest difference.
I dug through the message headers, and compared them to headers in other messages that open immediately, and I found one consistent difference that I think may be relevant: In the affected (slow to open) messages, the "Thread-Index" header is HUGE. Here is a sample of the Thread-Index header from one of the affected messages:
Thread-Index: AcjiFIEKqRcCkJDiTP6aECNc4B
LVo1WAAEx7bcAASK9woAKIYG5Q
EAjVbyLgABDCFbAC/RB/YAALB9
nXEAALroGQACZtn1AAF5DR0AJp
JBhykAM/57SgCP/hWFAAH0srQA
AJqg3foAAMui7gAp4HTZAAgrJC
Now, I'm no authority on e-mail headers, but I'm pretty sure this isn't normal. A little Google research revealed that this header is apparently used by Microsoft mail servers (i.e. Exchange) to track a threaded conversation - a chain of replies and forwards and such. Based on the contents of the e-mail (which doesn't show a long chain of replies or forwards at all) and from what I could tell from the Google results, this header should be much, MUCH shorter.
But that's where I'm stalled. I have no idea what to do about this. As far as I know, other recipients of this message aren't having the same problem, so I'm reluctant to start pointing fingers at the sender. On the other hand, the recipient wouldn't have anything (directly) to do with this header, would it?
And for that matter, I'm not completely certain that this header is what's causing the symptoms. I mean, it seems to be the most likely culprit. So, if anyone has any suggestions, either for alleviating the symptoms or for dealing with the over-sized Thread-Index header (which will, hopefully, alleviate the symptoms), I am all ears.
:)
P.S. I don't have direct physical access to this machine; but I can do just about anything we might need to do remotely through TeamViewer (the machine is in a somewhat distant geographical location). I can get physical access if it becomes necessary, but it will take a bit of time. Also, for the convenience of the user, I'm mostly working on this after hours. On top of that, I have a number of school projects coming due this weekend. So my follow up responses may be a little slow, and may come at odd hours. Bear with me! Oh, and thanks in advance for your help! ;)
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Unfortunately, the recipient is a dispatcher for a small trucking company, and the messages are delivery requests from one of their clients. She usually only gets a few of them each day, but they are a regular occurrence, so we'll need to figure out something more permanent than a copy/paste solution (though I like the idea).
Also unfortunately, I never got the chance to contact the customer today; I wanted to verify whether or not other recipients were having the same symptoms or not. (Just because that information wasn't volunteered doesn't mean it's not happening, as I'm sure you all well know ... )
And yet more unfortunately, apparently she turned her machine off when she left this afternoon, so no remote access this weekend. So happy weekend all, and we'll start this up again Monday!
;)
Also unfortunately, I never got the chance to contact the customer today; I wanted to verify whether or not other recipients were having the same symptoms or not. (Just because that information wasn't volunteered doesn't mean it's not happening, as I'm sure you all well know ... )
And yet more unfortunately, apparently she turned her machine off when she left this afternoon, so no remote access this weekend. So happy weekend all, and we'll start this up again Monday!
;)
Oooh so it's coming up in new messages?...hmm. Does this problem manifest itself only within pst's or will the message do the same thing if it was still in the exchange mailbox?
Also, does the pst reside on that local computer?
Also, does the pst reside on that local computer?
ASKER
I have only seen the problem on the recipient's end (POP mailbox stored in a .pst file), but I have no access to or control over the sender. I'm relatively certain, given the header information, that the sender is using an account on an Exchange box.
And yes, the .pst is on the local computer; it resides in the default location (c:\documents and settings\<user>\local settings\application data\microsoft\outlook\out look.pst).
:)
And yes, the .pst is on the local computer; it resides in the default location (c:\documents and settings\<user>\local settings\application data\microsoft\outlook\out
:)
ASKER
Sorry, it took me a while to get back to this. Okay, new results from troubleshooting and/or more info:
Oh, one other bit of info that's probably not relevant (but I'll include it just in case): Apparently there is an issue with Outlook where you can only open attachments with the same name up to 99 times - on the 100th attempt Outlook won't open the file, because of naming issues in Outlook's temp files (it will only append the numbers (1) through (99) to identically named attachment files). The solution, if identically named files are received often, is apparently to find and manually clear the Outlook cache periodically. The client experienced this issue (because the Delivery Request attachment always has the same name), and has been trained by a previous technician to clear the Outlook cache herself every 2 weeks or so.
Thanks so much for helping me out with this. Let me know if you think the "copy/paste" issue is separate and unrelated and needs its own question, and I'll open it in a Related Question. (Personally, at this point I think it's related, but I'm not sure how; maybe an OLE issue?) As always, I welcome any suggestions!
:)
- Outlook.exe /CleanProfile - no difference
- Reregister inetcomm.dll - no change
- I successfully saved the message as a .msg file, and file transferred it to my shop. I tried it on two different computers, one with Outlook 2007 and one with Outlook 2003. The first (2007) showed exactly the same symptoms - long time to open, crash on attempt to forward. The one with Outlook 2003 opened the message much faster, but was still a bit slow, and still crashed on attempt to forward. So overall, the symptoms seem to follow the message.
- I tried (for the heck of it) to run a repair install on Office (Add/Remove Programs -> Change -> Repair). No change.
- The client claims that no other recipients are experiencing this problem. I find this difficult to believe, given the above observations, so I'm going to clarify this again to be sure.
- The client also told me about another symptom, which either wasn't mentioned before or else I missed it, and which may or may not be related. (This will take a bit of explaining, so bear with me ... ) Apparently, when the client receives these e-mails, she opens the attachment (an Excel spreadsheet), copies a half dozen or so cells to the clipboard, then opens a spreadsheet she maintains on her desktop and pastes the copied cells into it. (This part is working). Then, apparently, she creates a new e-mail (or possibly a Reply or Forward; I need to clarify that part too), and Copies/Pastes those same new cells into it (apparently right into the body of the message) to send off to someone else. This process is reportedly causing the computer to "Lock Up". (I tested this: I opened the Excel spreadsheet on her desktop and a brand new, blank e-mail; I copied 6 cells from the spreadsheet, and pasted them into the body of the blank e-mail, and waited. After about 10 minutes of watching the hourglass, the cells finally showed up in the e-mail, but the hourglass was still present and the e-mail window unresponsive. For the next 45 minutes, the hourglass remained, and the Outlook, new mail, and Excel windows all remained unresponsive. Task Manager showed Excel using 25-30% CPU usage, and Outlook using 5-10%; terminating Excel freed the Outlook windows.)
Oh, one other bit of info that's probably not relevant (but I'll include it just in case): Apparently there is an issue with Outlook where you can only open attachments with the same name up to 99 times - on the 100th attempt Outlook won't open the file, because of naming issues in Outlook's temp files (it will only append the numbers (1) through (99) to identically named attachment files). The solution, if identically named files are received often, is apparently to find and manually clear the Outlook cache periodically. The client experienced this issue (because the Delivery Request attachment always has the same name), and has been trained by a previous technician to clear the Outlook cache herself every 2 weeks or so.
Thanks so much for helping me out with this. Let me know if you think the "copy/paste" issue is separate and unrelated and needs its own question, and I'll open it in a Related Question. (Personally, at this point I think it's related, but I'm not sure how; maybe an OLE issue?) As always, I welcome any suggestions!
:)
ASKER
Update: I have confirmation from the client that no one else is experiencing ANY of the symptoms of these problems.
I've asked her to have one of the other dispatchers send a copy of the Delivery Request e-mail they received both to her and to me, for comparison purposes. I also asked that she have them send me and her a copy of their spreadsheet, so I can test the second issue on their file as well.
The logical conclusion at this point, it seems to me at any rate, would be that something is corrupting these files (or has already done so) on her computer. I'm thinking that if we can't figure this out by the weekend, it'll be time to cut our losses, rip Office 2007 out of the computer by its roots, and reinstall it.
Let me know what you think!
:)
I've asked her to have one of the other dispatchers send a copy of the Delivery Request e-mail they received both to her and to me, for comparison purposes. I also asked that she have them send me and her a copy of their spreadsheet, so I can test the second issue on their file as well.
The logical conclusion at this point, it seems to me at any rate, would be that something is corrupting these files (or has already done so) on her computer. I'm thinking that if we can't figure this out by the weekend, it'll be time to cut our losses, rip Office 2007 out of the computer by its roots, and reinstall it.
Let me know what you think!
:)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
@MidnightOne: No Exchange server on the recipient side (it's just a basic POP account), so no OWA.
I tried to forward the message to my account, and Outlook crashed every time I clicked "Send". Oh, hey, that gives me an idea, though; I'm going to save the message off as a .msg file, file transfer it to my computer, and then open it up with my Outlook and see if it does the same thing ...
The .pst file was nearly 4 GB; compacting it reduced it to just under 2 GB, but made no difference in the symptoms. And I agree about the inadvisability of using .pst files in an Exchange environment, but unfortunately that doesn't apply here.
I'll post back here once I get a chance to try these things and let you know what happens.
Thanks!
:)