Page 1 of 1

errors installing to network drive

Posted: Fri Sep 08, 2006 1:41 pm
by stampy
Hi,

I can’t install my setup to a drive (e.g. Z:\\) which is mapped to a network share on a different machine. I get a series of installer error messages saying that each of my COM components can’t be installed: “Error. Module z:\\<path to one of my COM dlls> failed to register...contact your support personal”. If I select [Ignore] and continue through installation till completion, and then attempt to reinstall I still get the same errors. If I install directly to my local drive it works. If I go to the other machine and install directly there, it works. I was thinking that installing to this mapped network drive would be transparent.

If I run the dependency walker on the DLL, no errors are reported. Manually registering these COM dlls (using regsvr32) works – this is after I select [Ignore] to all of the errors and finish the installation. If I manually register all my COM dlls, my app will work fine.

I suspect either something with InstallAware or something with Windows Installer. I’m thinking that one or more of the dependent system dlls and side-by-side runtimes aren’t getting properly located during the IA “File is Self Registering DLL”/”Install Files” operation. I suppose I could use “Register Library” operation (I haven’t tested this yet), but I was wondering if anyone else had this problem? Any ideas?

Thanks!

Posted: Fri Sep 08, 2006 3:17 pm
by jimo
If I had to venture a guess, Window INstaller is the culprit.
I believe I read somewhere that com components should be installed locally and registerd locally because you can not always be assurred that the network resource will be available.

Just a guess.