I have the same issue and it looks like it might have been related to a minor release.
View solution in original post
