odjau Posted December 13, 2010 Report Share Posted December 13, 2010 Hello all, During package installation test on coworker's PC, I've came across this error. I'm just trying to open it from network HD. Copying it to the local HD fix the issue. Workaround is easy, but behavior may be surprising for the end-user. Regards, Olivier Link to comment Share on other sites More sharing options...
Michael Aivaliotis Posted December 13, 2010 Report Share Posted December 13, 2010 Which version of VIPM are you using? 2010.0.0 or 2010.0.1? Also, please elaborate on the "open it from network HD" comment. Did you open it directly from the network drive by double-clicking on it? Link to comment Share on other sites More sharing options...
odjau Posted December 14, 2010 Author Report Share Posted December 14, 2010 Which version of VIPM are you using? 2010.0.0 or 2010.0.1? I'm using 2010.0.1 (build 1581) version. Also, please elaborate on the "open it from network HD" comment. Did you open it directly from the network drive by double-clicking on it? I use an explorer window to browse our LAN to find a shared directory on colleague's PC containing vip file. Then I double-click on it and obtain the error message. I've got the same behavior browsing a local directory via "Microsoft Windows Network". I'm running windows XP Pro SP3. Let me know if you need more information about our network settings. Link to comment Share on other sites More sharing options...
Jim Kring Posted December 16, 2010 Report Share Posted December 16, 2010 I can reproduce this behavior if I try to double-click either a VIPC or VIP file that's on a network drive that uses UCN paths. I've filed an official bug report: Case 10539: Can't open VIP or VIPC files by double-clicking them if their on a network drive (UNC path issue) I'm pretty sure that this is a bug in VIPM -- I'll we'll deeper into this and let you know what we find. Thanks so much for reporting this issue! Link to comment Share on other sites More sharing options...
Michael Aivaliotis Posted December 21, 2010 Report Share Posted December 21, 2010 This issue is definitely a VIPM problem and is now resolved. The fix will show up in the next release of VIPM. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.