S
Skeet
We just upgraded our Word 2000 with all the security
updates etc. from Microsoft. Since that time, we have
been experiencing a crash "sorry for the inconvenience".
the crash occurs in module mso9.dll. The following is the
basic crash information:
AppName: winword.exe AppVer: 9.0.0.8216 ModName:
mso9.dll
ModVer: 9.0.0.6926 Offset: 001d17b1
This is a very complex document, and this behavior seems
attached to the document file itself. We have been unable
to determine how the files are becoming corrupted, as it
happens as we modify this newsletter the same way each
week. Just pressing the "show hidden characters" button
is enough to set it off. It seems that anything that
causes the whole document to be analyzed will do it (ex:
printing). We have attempted to rebuild this document a
number of times by going back to an early version (without
the behavior) and reworking it. Whenever we do, the
program eventually crashes and perverts the document.
What is frustrating is that there is nothing in the
knowledge base to help - and I can't get Microsoft to look
at it because the web site rejects my product ID number!
Grrr!
Anyway, if anyone out there has any clues that would help,
we would sure appreciate it!
updates etc. from Microsoft. Since that time, we have
been experiencing a crash "sorry for the inconvenience".
the crash occurs in module mso9.dll. The following is the
basic crash information:
AppName: winword.exe AppVer: 9.0.0.8216 ModName:
mso9.dll
ModVer: 9.0.0.6926 Offset: 001d17b1
This is a very complex document, and this behavior seems
attached to the document file itself. We have been unable
to determine how the files are becoming corrupted, as it
happens as we modify this newsletter the same way each
week. Just pressing the "show hidden characters" button
is enough to set it off. It seems that anything that
causes the whole document to be analyzed will do it (ex:
printing). We have attempted to rebuild this document a
number of times by going back to an early version (without
the behavior) and reworking it. Whenever we do, the
program eventually crashes and perverts the document.
What is frustrating is that there is nothing in the
knowledge base to help - and I can't get Microsoft to look
at it because the web site rejects my product ID number!
Grrr!
Anyway, if anyone out there has any clues that would help,
we would sure appreciate it!