Most of my use of the servers is automated, using dns-compliant server names (because the code yelled at me a few months ago). I only encountered this exception doing some manual testing and tweaking and it's mostly cosmetic, so the workaround for me is to simply ignore the error and move on!

Hopefully the "proper fix" finds its way into some future version!

On 8/14/14, 9:43 PM, Zack Shoylev wrote:
...as a workaround, after deleting the server, you could ...
Of course, the proper fix is ...

Reply via email to