In a Windows Service executing on a production server, within a Try Catch block, while reading XML into a strongly typed dataset, an error was popped on top of the logon screen on the server. The code stopped executing and just hung there. I stopped the
service in which the error had occurred, deleted the bad pickup file, and restarted the service to get past the problem.
In the XML, there was a space before one of the node names < myNodeName> and one of the nodes that is not set to
minOccurs="0" was missing. Still, this should have just caused it to hit the catch block, not raise an error all the way up above the Logon Screen, right?