What steps will reproduce the problem?
1.
Create a handler to the Nameserver.AuthenticationError
2.
Sign in with wrong credentials.
What is the expected output? What do you see instead?
I would expect the Nameserver.AuthenticationError event would be raised.
What version of the product are you using? On what operating system?
2.5.3
Please provide any additional information below.
The event Nameserver.ExceptionOccurred is raised but the
Nameserver.AuthenticationError isn't
Original issue reported on code.google.com by freakysm...@gmail.com on 18 Jan 2009 at 12:36
Original issue reported on code.google.com by
freakysm...@gmail.com
on 18 Jan 2009 at 12:36