I wrote this post around one year back but never posted here, no specific reason..somehow missed it. Today when I was checking the uncompleted posts on my blog, came across this, as this was already a complete post so thought of posting it.... :)
As most of us would be aware, for VMware Update Manager and some other applications, we still need 32-bit Database Source Name (DSN)/ODBC connection to point the application database.
Nowadays for various reasons you will get/choose a 64-bit OS/system to install and configure your application, so here the question is how one would create a 32-bit DSN on a 64-bit System.
A 64-bit Windows operating system has two odbcad32.exe files:
As most of us would be aware, for VMware Update Manager and some other applications, we still need 32-bit Database Source Name (DSN)/ODBC connection to point the application database.
Nowadays for various reasons you will get/choose a 64-bit OS/system to install and configure your application, so here the question is how one would create a 32-bit DSN on a 64-bit System.
A 64-bit Windows operating system has two odbcad32.exe files:
- %SystemRoot%\system32\odbcad32.exe is used to create and maintain data source names for 64-bit applications.
- %SystemRoot%\SysWOW64\odbcad32.exe is used to create and maintain data source names for 32-bit applications, including 32-bit applications that run on 64-bit operating systems.
To set up a 32-bit DSN, launch the 32bit version of the ODBC Data Source Administrator (to create a 64-bit DSN open the 64-bit ver of ODBC Data Sourse Administrator).
From here you can create a 32-bit ODBC connection.
For detailed step by step guide, click HERE.
Reference: VMware vSphere 5.5 Documentation, MSDN.
That's it.... :)
From here you can create a 32-bit ODBC connection.
For detailed step by step guide, click HERE.
Reference: VMware vSphere 5.5 Documentation, MSDN.
That's it.... :)
No comments:
Post a Comment