AWill Posted October 29, 2013 Posted October 29, 2013 (edited) Hi all, We are using the latest MSI installer to install ActivInspire across our network. This works absolutely fine on machines without ActivInspire installed at all. On machines running 1.6 (which we want to upgrade), we get an error related to a UNC path (Cannot access \\\\sharename\\studioshare). I think this is when it is trying to remove the old version. When installing the 1.6 version of the software (also using MSI installation), we used the UNC path "\\sharename\studioshare" for our shared resources. I saw a post about the same issue while back on Edugeek about the issue but never found a solution after searching through these forums. If anyone can shed some light on this for me I'd really appreciate it, thanks! Edited October 29, 2013 by AWill
pete Posted October 29, 2013 Posted October 29, 2013 Recreate \\server\studioshare so it holds the 1.6 install point?
phillyrovers Posted October 30, 2013 Posted October 30, 2013 Hi AWill, This issue is one that is caused by the MSI installer itself. Below you will find a link to the 1.7.6219 network intallation directoey. (this link is only valid for 5 days) Please try this version. Your password is: uUtDMPQh Name: 1.7B Net.rar Size: 335.11 MB Expires: November 04, 2013 Download: https://promsendit.com:443/download?domain=emea&id=d1yH49X46Jmq2PDhqJOa-LfX9jhrMybSP If you are still getting issues, please check the registry, under: HKLM\Software\Activ Software\Inspire\App\1.0 Look for the AppSharedResDir key and ensure that the path shown in this key is correct before starting the install for Inspire v1.7. Let me know how you get on. 1
AWill Posted October 30, 2013 Author Posted October 30, 2013 Thanks a lot, I'll let you know how i get on!
AWill Posted November 7, 2013 Author Posted November 7, 2013 Sadly I couldn't get this to work. I tried the file you provided and it didn't work - same issue - and seems to be the network installer I have already. That said, changing the registry key also seems to have mixed results. In some cases it is fixing the problem and in others it isn't. I must add that I can actually run a manual uninstall on machines to fix the issue too so I might just go ahead and run the registry change, then uninstall on machines where it didn't work. Thanks for all your help!
Recommended Posts