DLL conflict between SP and EMC Networker
Francis Swasey
Frank.Swasey at uvm.edu
Thu Oct 18 08:51:00 EDT 2012
On Oct 17, 2012, at 6:52 PM, Elliot Kendall <elliot.kendall at ucsf.edu> wrote:
> I just spent a couple of hours tracking down an installation problem
> with the Windows SP. The install would stop at "Starting services" and
> then roll back with an uninformative error message. The event log would
> show:
>
> Faulting application shibd.exe, version 2.5.0.0, time stamp 0x501c1959, faulting module MSVCR80.dll, version 6.0.6002.18541, time stamp 0x4ec3e3d5, exception code 0xc0000142, fault offset 0x00009f5d, process id 0xdbc, application start time 0x01cdabc5b4b6c444.
We've tripped over this and argued with EMC about it to no end. The problem (as we've experienced it) is that NetWorker (arrogantly) puts its install directory at the start of the Windows PATH. The solution (for us) is to manually put the NetWorker directory where it belongs... (which I assure you is not FIRST IN LINE)
-- Frank
More information about the users
mailing list