A
Andy Fish
Hi,
I have an application that runs word as a windows service <gasp>. The last
couple of places I have installed it, word crashes as soon as it starts up,
and I get a dw20 process appearing (obviously dr watson is trying to popup
on the screen but there is no screen). If I switch the service to run as a
normal user rather than LocalSystem it all works fine.
Normally I wouldn't think anything of it and would just assume that word
won't run as LocalSystem at all. However, I have at least 10 other
installations of this software, and all have word running as LocalSystem
with no problems. It's only the recent ones that have a problem.
Anyone else noticed this problem? Has there been a recent patch to word or
windows that has caused this behaviour?
TIA for any hints.
Andy
P.S. If you would like to preach to me that I shouldn't be running word as a
service, please start a separate thread
I have an application that runs word as a windows service <gasp>. The last
couple of places I have installed it, word crashes as soon as it starts up,
and I get a dw20 process appearing (obviously dr watson is trying to popup
on the screen but there is no screen). If I switch the service to run as a
normal user rather than LocalSystem it all works fine.
Normally I wouldn't think anything of it and would just assume that word
won't run as LocalSystem at all. However, I have at least 10 other
installations of this software, and all have word running as LocalSystem
with no problems. It's only the recent ones that have a problem.
Anyone else noticed this problem? Has there been a recent patch to word or
windows that has caused this behaviour?
TIA for any hints.
Andy
P.S. If you would like to preach to me that I shouldn't be running word as a
service, please start a separate thread