That narrows it down. I gave it a try and ran into the same error. After some quick searching, I found that this appears to be related to a software bug introduced in an update around May 2017. I also found a suggested fix, but I’ll need to investigate it further when I have time - probably Friday - since it will involve making a code change and doing some testing.
Thanks for taking the time to report this. I’ll post back to this thread when I have more information to share.