I'm having a hell of a time getting a legacy wise installer to work. Near the end of the process the installer runs a vb script and the following steps happen
- cscript - runs vbs file called runscriptupdates.
- Runscriptupdates.vbs - calls a COM dll named Remote.dll
- Remote.dll - Calls another dll called libmcl.dll
- An error message is pumped out
failed to insert xyz.csv error 53 File not found: libmcl-2.7.0.dll, line 0, file=C:\DATA\CLIENT\xyz.csv
So the conclusion is that the cscript/vbs/remote.dll can't find libmcl-2.7.0.dll. I can reproduce the same behaviour of the installer by running the script manually and here's what I've tried so far but I'm still getting the same failure message.
- Copied libmcl to directory of cscript
- Copied libmcl to directory of remote.dll
- Copied libmcl to directory of runscriptupdates.vbs
- I turned on fusion logs to see if that had any pointers but because it's not .NET there's nothing of use
- Tried to register libmcl with regsrv but it can't
At this moment if I check the path from a command prompt the folder holding libmcl isn't in the path. However if I check it through the myComputer->Advanced->EnvironmentVariables the folder is in the path.
If I restart the machine after the attempted install and then run the installer again it works no problem. I feel like it must be the path not being updated properly at the time of install or something like that. Is there a way to force an update after making an addition to the path?
Thanks, Neil