You can look at my similar thread here:
Does yours always occur, or just once in awhlie?
I wonder if there is some sort of timing issue. Mine occurs after it tries to copy, so I wonder if it's trying to start something, or scan itself, before it's actually finished copying?
I did see that post but it was with VSE 8.5 seeing as my issue is with VSE 8.7 V2 DATs and BOC shouldn't be an issue
My particular issue only occurs now and then. I've yet to determine any pattern, yesterday my issue occurred with 5 GEMs. I've just tried it just now and it's thrown the same error attempting to down load 1 GEM.
Update: Attempting to update from 5950 to 5951, GEM fails and begins to download avv DAT, i cancel the download, VSE gets its knickers in a twist and now says that there is no engine or DAT installed, re-apply 5950 superdat and reboot, VSE now quite happily downloads GEM and updates....Go Figure! We'll see what happens tomorrow.
1 of 1 people found this helpful
There might be some diagnostic log levels you can increase, which might give more information about the errors. Have a look at :
(The agent side of things of course!).
As I've posted in the other thread, I'm actually curious why so many of these types of issues seem to be reported. Is there an issue with patching the dat file, now that it's growing in size? Is there a timeout when copying? etc etc etc.
~150kb for a gem update is a huge bandwidth difference from ~61Mb for the zip update... so really it's something that needs to be worked out!
I have been going through the logs but there was absolutely nothing that stood out as errors around the time of the DAT update.
I've increased the logging level of the agent. Hopefully i'll get some insight into the cause.