Each of the operators in your deployment have an “opsite” with a different number (in this case, opsite70 and opsite74). These errors are from clients trying to see if there are any new actions from these operators (if you look in your actionsite.afxm file, you will see the sequence number that matches up with each operator.)
These errors are not a big deal, they cause the client a short delay in normal work every few hours as they re-check to see if something is new. If there are lots of these failures, it could cause the agent to appear slow (because it is spending lots of time checking lots of sites), but generally it is not a big deal if you only have a few of these.
These errors tend to be caused by one of two things:
You created an operator in BES Admin, but when it asked to propagate the changes, you clicked “No”. Additionally, the operator has never sent out an action. This is why you get the “empty directory” error because there is nothing there for the agent to check.
You switched a user from a normal operator to a master operator. This generally causes you lots of problems (for various digital signature reasons) and BES 6.0 prevents you from doing this. This might be the “no authorized signature error”.
To remove the #1 error situation:
Either log in as that operator send out any action (doesn’t matter what kind of action as long as it propagates) -or- run
besadmin.exe /propagatealloperatorsites
(BESAdmin.exe is in the a subfolder of the BES Server), which will re-propagate an action for every operator. If you run besadmin with the command line option, it could take quite a while before it finishes and it makes the system busy for a while so you might want to do it at night when you don’t expect a lot of activity in the system.
It is probably best to delete the operator 70 and re-make the user with a different name. Look in actionsite.afxm and you will see something that looks like this:
“username1” is opsite70 and username2 is opsite74.
Note: the errors are not removed from this log automatically so if you fix the problem, the errors will stay in the logs, but the time will not be updated.