Question

ODBC 32 Bits in Windows Server 2008 64 Bit

Answer 1

ODBC 32 Bit

A problem that we can find very often is having to configure a 32-bit ODBC connection on a 64-bit operating system, such as Windows Server 2008 64-bit or Windows Server 2008 R2 (only about 64 bits) .

For example, if we decide to mount a VMware vCenter Server server on Windows Server 2008 R2, we will see that the platform requirements will be fulfilled since vCenter asks us for a 64-bit operating system. If we use a database connection such as SQL Server to store the database of our vCenter, the ODBC connection to connect to the database must also be 64 bits.

• But we really run into the problem when we need to configure a 32-bit ODBC on a 64-bit operating system. Example: Install a vCenter Update Manager on Windows Server 2008 R2 .

• Interestingly, the vCenter Update Manager requires a 64-bit platform but a 32-bit ODBC. The error that we can find in the installation is the following:

"The DSN, 'VUM' does not exist or is not a 32 bit system DSN. Update Manager requires a 32 bit system DSN. "

• If we create an ODBC with our Windows Server 2008 R2, by default, it will generate a 64-bit connection. To create a 32-bit ODBC with a 64-bit Windows Server 2008 or R2 we run:

"C: \ windows \ syswow64 \ odbcad32.exe"

The executable to create a 64-bit ODBC is:

"C: \ windows \ system32 \ odbcad32.exe"

• As you can see, it is a bit misleading, but knowing these two routes we have already controlled the situation.

With this we could have our 32 BIT OBDC in our Windows 2008 Server R2 system.

---