This error is probably due to running {0} in deployment without {1}/{2} server roles. In this case these errors can be ignored ...