Quote:
Originally Posted by Tanis
As per Alex's comments on the bug I filed, it looks like there's no need to do anything with the database.
Simply restarting the two FMS services resolves the issue for me.
|
I may have overlooked that in the process of creating the database workaround. I'l be testing that out at our event tomorrow and confirm.