Matthew Harrison Posted October 28, 2008 Report Share Posted October 28, 2008 I have had VIPM working fine under Vista for several months, but recently I have started to have a problem where I cannot add any new packages. Whenever I try, I get an error message "There was an error adding packages to the package list." I'm correlating this with an automatic update to SP1, but I suppose that I'm not positive that is the problem because I don't use VIPM every day. I'm not aware of anything else that has changed on my computer except these automatic updates since I knew it was working. I have tried completely uninstalling and reinstalling VIPM, but that didn't seem to make any difference. I have also verified the permissions for the JKI directory. I also tried installing and running with "Run as Administrator." I notice that when I check the network for available packages, I see all the .bmp and .spec files added into the cache directory. Also, I see .pdi2 files added to the LV 8.x directories in "databases" when I try to add packages. The point at which I get errors always seems to be the point where an .ogp file would normally be unzipped, or at least opened and read. I've double checked that nothing is read-only, and it seems like permissions should be allowed to everything that I can think of. An error log file is created, which I've attached. I'm really not sure what else to try at this point, but I've really come to depend on VIPM, so I'd love to get it working again. October_28_2008.txt Link to comment Share on other sites More sharing options...
Matthew Harrison Posted October 29, 2008 Author Report Share Posted October 29, 2008 It looks like I solved my particular problem, although I don't have a perfect root cause analysis. It appears that VIPM must be able to write various files to the Temp directory. I don't think that there was a permission problem, but somehow it was failing to overwrite some file that already existed. Unfortunately, I'm not sure how that bad file got there or why VIPM could not overwrite it. If I get more information, I'll post again. For my purposes, I solved the problem by blowing out the entire Temp directory, and verifying that it was not write only. Link to comment Share on other sites More sharing options...
Jim Kring Posted October 30, 2008 Report Share Posted October 30, 2008 It looks like I solved my particular problem, although I don't have a perfect root cause analysis. It appears that VIPM must be able to write various files to the Temp directory. I don't think that there was a permission problem, but somehow it was failing to overwrite some file that already existed. Unfortunately, I'm not sure how that bad file got there or why VIPM could not overwrite it. If I get more information, I'll post again. For my purposes, I solved the problem by blowing out the entire Temp directory, and verifying that it was not write only. Hi Matthew, First, I'm sorry that it took so long to respond. I was traveling to the Boston NITS event when you posted. I'm happy to hear that you got it working. There are a couple possible "root causes": 1) It might have been a permissions issue with files/folders in the Temp directory 2) It might have been that there were files in the Temp directory that were "in the way" and even though VIPM had permission to delete them, it wasn't trying to delete them before writing. If the problem was #2, then this might affect all users -- not just Vista. I'll take a look under the hood and see if I can find anything that looks suspect. Thanks, -Jim Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.