It sounds like the activation response is failing. A couple things on activation responses: (1) they only work for a short period of time (so if they don't activate right away with them -- within a couple of days -- then they will no longer be valid) and (2) all paths for offline requests/responses must be full paths on the filesystem and (3) activation responses are per-machine.
Lastly, it looks like the error is happening with the activation response, but because they're using all of the requests right in a row it's hard to tell where the problem is.