M
Mark
Hi...
Someone asked me to look into why a .net windows service we use in a lot of
places was failing to start on a box he just had built fresh. It's running
W2k3 Web Edition Sp 2 with IE 8.
Since it's a production box, we don't have any of the debuggers installed
there, but it doesn't seem like the software is even firing up far enough to
do any logging.
Depends shows 2 missing dlls: IESHIMS.dll and WER.dll.
I haven't found anything definitive, nor any solution, but a lot of Googling
seems to point to the IE 8 installs messing things up. It introduces a new
version of MSHTML.dll/IEFRAME.dll with a dependency on IESHIMS.dll which
doesn't exist on the system.
Without a lot of debugging tools how does one prove it's the missing
unmanaged dlls several levels away from our softwre causing the trouble? And
what do we do about it?
Thanks
Mark
Someone asked me to look into why a .net windows service we use in a lot of
places was failing to start on a box he just had built fresh. It's running
W2k3 Web Edition Sp 2 with IE 8.
Since it's a production box, we don't have any of the debuggers installed
there, but it doesn't seem like the software is even firing up far enough to
do any logging.
Depends shows 2 missing dlls: IESHIMS.dll and WER.dll.
I haven't found anything definitive, nor any solution, but a lot of Googling
seems to point to the IE 8 installs messing things up. It introduces a new
version of MSHTML.dll/IEFRAME.dll with a dependency on IESHIMS.dll which
doesn't exist on the system.
Without a lot of debugging tools how does one prove it's the missing
unmanaged dlls several levels away from our softwre causing the trouble? And
what do we do about it?
Thanks
Mark