Wendy -
When we enabled SQL Server logging of the VPN Logs it created the same error. Sounds like an MS Glitch? In our case we moved the logging option back to basic log files and everything began to work fine!
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.