Post
by ddog800 » Thu Apr 19, 2012 2:07 pm
Well, I hate to say it, and I'm not 100% certain, but this looks to be an unhandled exception in the Connect client source code which could require an update from the developers. It looks like that error is a Python exception that occurs when Python attempts to convert a Unicode character into another format. If no format is specified, then it assumes ASCII. In this case, as with MANY Unicode characters, there is no ASCII equivalent, so it throws an exception. I'd suggest submitting this as a bug to the Connect client devs along with as much information as possible regarding the exact OS version and which language version of the OS is being used. Out of curiosity, which language version of the OS are you guys using on the systems where it's failing?
I'm not sure what the rules are here regarding posting links to other forums and blogs, so I'll refrain from doing that, but if you do a Google search with the meat of that exception ( from 'ascii'...(128) ) and in the context that you're searching for Python/Unicode issues and not an OpenVPN issue, then you'll find numerous results that describe this problem, Unfortunately, as I mentioned, it typically wouldn't be something that can be fixed without a recompile.