D
DLN
Hello all,
I'm stuck on a problem that I can't for the life of me figure out. I'm
running a fully patched version of Office 2003 on a fully patched copy of
Windows XP Pro SP2. Any time I attempt to open an MS Word document from our
internal WSS 3.0 site (regardless of whether it's read-only or in edit
mode), Word opens the document and then after a few seconds, crashes and
brings up the Microsoft error reporting tool. The behavior is only present
with MS Word - every other Office 2003 component such as Excel, PowerPoint,
Visio, etc... all function without error. Additionally, opening a local MS
Word document doesn't cause Word to crash.
Every time there is a crash, the Application log reports mso.dll as the
culprit and returned error code is 0xC0000005. A lookup of that error code
corresponds to either an access violation or
"USBD_STATUS_DEF_NOT_RESPONDING" ... neither error code is of very much
help. I haven't been able to locate any additional log files that I can use
to troubleshoot this issue further.
I have been able to get Word to behave properly if I log into the same
system as a local user instead of my domain user account. Aside from the
domain versus local account difference, the only other difference between
the two accounts is that my domain account uses folder redirection for the
desktop, My Documents, and Application Data folders. I don't know if this
has anything to do with the error I'm seeing, but I figured I would mention
it just in case.
Has anybody run into this type of error before or do you know how I could
troubleshoot it further? Is there a way to enable verbose logging for the
Office products?
Thanks,
DLN
I'm stuck on a problem that I can't for the life of me figure out. I'm
running a fully patched version of Office 2003 on a fully patched copy of
Windows XP Pro SP2. Any time I attempt to open an MS Word document from our
internal WSS 3.0 site (regardless of whether it's read-only or in edit
mode), Word opens the document and then after a few seconds, crashes and
brings up the Microsoft error reporting tool. The behavior is only present
with MS Word - every other Office 2003 component such as Excel, PowerPoint,
Visio, etc... all function without error. Additionally, opening a local MS
Word document doesn't cause Word to crash.
Every time there is a crash, the Application log reports mso.dll as the
culprit and returned error code is 0xC0000005. A lookup of that error code
corresponds to either an access violation or
"USBD_STATUS_DEF_NOT_RESPONDING" ... neither error code is of very much
help. I haven't been able to locate any additional log files that I can use
to troubleshoot this issue further.
I have been able to get Word to behave properly if I log into the same
system as a local user instead of my domain user account. Aside from the
domain versus local account difference, the only other difference between
the two accounts is that my domain account uses folder redirection for the
desktop, My Documents, and Application Data folders. I don't know if this
has anything to do with the error I'm seeing, but I figured I would mention
it just in case.
Has anybody run into this type of error before or do you know how I could
troubleshoot it further? Is there a way to enable verbose logging for the
Office products?
Thanks,
DLN