DLL conflict between SP and EMC Networker

[Francis Swasey]

On Oct 18, 2012, at 10:13 AM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:

> On 10/18/12 8:51 AM, "Francis Swasey" <Frank.Swasey at uvm.edu> wrote:
>> 
>> 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)
> 
> Well, nobody's right or wrong, it's just that Windows doesn't have a
> standard versioning mechanism nor does it have a standard runtime library.
> 
> The traditional notion of DLL Hell is nonsense, but this aspect is just
> unavoidable.
> 
> It's certainly true that path changes should be at the end, but one of the
> two will end up first, and the other one will break.


Actually, no.  NetWorker does not break when you move it in the path order.  The fact that it updates the path at all is an artifact of EMC's development method.  They use the newer Windows Manifest system, so they don't even reference the path for anything.  They just stick it in there because they never thought to take it out.

-- Frank