Hello,

Environment: Windows 2003 R2 Terminal Server that has a 32bit Visual FoxPro Application installed with a SQL Server 2008 Express backend.

If you start a Terminal Server session via RDP and log into the Visual FoxPro Application, everything works just fine.

If someone else starts a second Terminal Server session and tries to start the Visual FoxPro Application, you immediately get a "Sorry, We are unable to login to the SQL server at this time." message and when you click "OK," the message goes away and the Visual FoxPro Application does not start.


Now, If you start Terminal Server Session 1 and start the Visual FoxPro Application without logging in;

Then, start Terminal Server Session 2 and start the Visual FoxPro Application without logging in;

Then, you log in to Terminal Server Session 1 Visual FoxPro Application, you can get in with no problem;

Then, you log in to Terminal Server Session 2 Visual FoxPro Application, you can also get in with no problem.

The ODBC driver is set with the 32bit ODBC found in C:\WINDOWS\SysWOW64.

Any idea why this is happening and how to fix it?

Thanks,

TFISHER