Yes, we have ranges set up already, but thanks for the advice. 

Actually, we finally found the answer by calling Microsoft directly. It is a known (but not public) bug...