I have a very simple VB.Net app that does a query on a remote SQL Server 2005
database and displays query results in a grid and prints a Crystal report. I
have installed it on several different clients on various networks, but it
wil not execute on one of my client's networks - the one where the SQL Server
and the subject database is located and which is running Windows 2003 Server.
In the failing app, I have a logon function that displays a login form,
accepts user ID and password, validates them against an SQL Server table,
displays login errors and then displays a menu form if the login is valid.
The login form is displayed and accepted, the SQL Server lookup works
correctly, the error messages boxes display correctly, but the menu form
display code spawns a CLR "exception has occurred that cannot be handled"
I access the SQL Server database using a UDL file.
The same app installed on most networks/workstations works correctly.
However, it will not run on any workstation in the same domain as the SQL Server that manages the database (the one pointed to by the UDL) is located. All of the failing workstations are running Windows XP Pro and VB.Net Framework 1.1 with
a service pack.
The setup/installation for this app was generated by Visual Studio .Net 2003.