Problem Description: Word closes with the following message: Microsoft Word has encountered a problem and needs to close.
I recently upgraded to Office XP Professional. All applications with the exception of Word work flawlessly. Word crashes within a few seconds whenver it is opened. I reinstalled multiple times following directions I found in Microsoft's knowledge base and got the same result. I have tried the installation using the command line
prior to using the control panel ADD NEW Software and
after installation. Using the install mode commands or not makes no difference.
I decided to try Office 2000 Professional and use the transform file that is available with the Office 2000 Resource kit. The only difference in the result is that Word now causes a Doctor Watson instead of the message above. I am running Windows NT 4.0 build 1381 with Service Pack 6 and Windows Terminal Server build 419.
I am relatively new to Citrix and I inherited this installation and problem. Office 97 had the same issue and my predecessor was unable to fix the problem. I have contacted Microsoft vial email/online support and they have directed me to the same knowledge base articles I have already viewed and used.
Anyone seen this problem before.
I recently upgraded to Office XP Professional. All applications with the exception of Word work flawlessly. Word crashes within a few seconds whenver it is opened. I reinstalled multiple times following directions I found in Microsoft's knowledge base and got the same result. I have tried the installation using the command line
Code:
change user /install
Code:
change user /execute
I decided to try Office 2000 Professional and use the transform file that is available with the Office 2000 Resource kit. The only difference in the result is that Word now causes a Doctor Watson instead of the message above. I am running Windows NT 4.0 build 1381 with Service Pack 6 and Windows Terminal Server build 419.
I am relatively new to Citrix and I inherited this installation and problem. Office 97 had the same issue and my predecessor was unable to fix the problem. I have contacted Microsoft vial email/online support and they have directed me to the same knowledge base articles I have already viewed and used.
Anyone seen this problem before.