I believe this is a known bug:
I think you may be able to re-enable it by editing the internal db, if you're comfortable with that. Otherwise, it sounds like you're stuck calling support.
I believe this is a known bug:
I think you may be able to re-enable it by editing the internal db, if you're comfortable with that. Otherwise, it sounds like you're stuck calling support.