ODBC Problems with SQL Server 2012 on Virtual Machine

[Joe.OEH]

I am having problem with my application after my IT department upgraded to SQL Server 2012 with error "ConngetDataToModify.vi:1"<ERR>Object 0x2222222 is not valid.  I have 4 servers running the same executable without problem before the upgraded. However, after the upgrade 2 of these Server are having the problem with the ODBC connection. Here are my setup, the application was created using LabView8.5, we have 2 physical server box running Window Server 2003, 2 Virtual Machine on Windows Server 2008, and a Virtual Machine with SQL 2012 Server. The 2 physical server running the executable without a problem after the upgrade, but the 2 Virtual Server were unable to connects to the ODBC connection. Anyone have any idea why this is happening , it is the problem with compatibility between my application with Server 2008 and SQL 2012 Server, or is there a problem with both beings Virtual Servers? As I said, the 2 physical Server seem to be running without any problem with the upgrade.

[tst]

My guess is that the problem is not specifically with LV. This should be relatively easy to check if you create a UDL file and double click it. This opens a Microsoft wizard which allows you to configure and test DB connections (the UDL file itself is basically just a text file which holds a connection string). If it doesn't work there, it won't work in LV.

As for what the actual problem is, a common culprit is the firewall, which is easy enough to check by disabling it. Another option is the surface area configuration of SQL Server, which will not allow network connections unless you tell it to.

It should probably also be noted that LV 8.5 is not officially supported on Windows Server. I'm assuming that's not the issue, but be aware of it.

[mikeporter]

The other thing I would recommend is to not use ODBC. Use the OLEDB drivers. They are newer, faster, more efficient -- all that good stuff...

Mike...