I assume that the reason for the failure could be in superdat.log, which you can look for by default in %TEMP% folder.
Actually, the excerpt looks like rather a form of an update task and not a deployment task, which - for me - you seem to have suggested in your description. Also, it looks like you download the superdat and the extra.dat in your master repository update task, and these are tried to get installed by the update task. You could check the settings in the Update Master Repository server task, and see if these are set to be downloaded.
I would say, normally these are not needed, as there is a order of trying to install things in the update task, and DAT and engine might precede the superdat and extra dat update attempts. Once the normal DAT is installed, there could be no use trying to install superdat again. An extra dat is only needed for added protection for newly discovered threats between DATs until a new DAT incorporates the signatures. An extra.dat further has a lifetime of several days, afterwards it won't be taken into account by VirusScan.