Ultimately, what you need to have happen is for the Clients in question to properly synchronize with the actionsite version that is being hosted by the Root Server. This will update the actionsite’s ‘epoch’ on the Client, and will allow it to match that of the Server.
So, in the Client log, where it is indicating that it is unable to update the actionsite, are there more details you can share?
If the BES Server itself is exhibiting this issue, you’ll want to ensure that the actionsite is being properly hosted by the BES/Root Server (sounds like it might not be).
As Jason suggests, this really warrants a support case