- Joined
- Jul 18, 2009
- Messages
- 391
- Reaction score
- 129
Sup everyone.
I've seen people with this problem appear left and right so I decided to finally make a simple tutorial to explain WHY these errors pop up and what you can do to fix this.
Why this error occurs so much on 64-bit systems
First of all you need to know what's the difference between 32-bits and 64-bits systems.
Operating Systems that run on 64-bits have a slightly different folder/registry structure than 32-bits systems do.
Most of the system files (including your ODBC connections!) are in a different place on 64-bits systems (C:\Windows\SysWOW64\odbcad32.exe) than they are on 32-bits systems (C:\Windows\system32\odbcad32.exe).
This specific error is very, very often caused because you created your Database connections in the 32-bits version of your ODBC connections.
What happens?
You launch your server and it will look for the ODBC connection in the 64-bits version and it can't find them.
So it generates this lovely error.
The fix...(kinda)
It's quite simple if you know the previous information.
Navigate to your Windows folder and find the folder "SysWOW64".
Within that folder look for "odbcad32.exe" and launch it.
These are your 64-bits ODBC connections.
Add the necessary ODBC connections in this program's System DSN and the error should be gone.
What if this didn't fix it?
That's still possible. It's not 100% certain that this is the cause of the error.
Other things to check are:
- Can you actually connect to the SQL server from where your binaries are hosted?
- Did you enter the right SQL user/password in your config-files? (Check them, even if you think they are right!!)
- Does your security software allow your server binaries to establish a connection to your SQL server?
I've seen people with this problem appear left and right so I decided to finally make a simple tutorial to explain WHY these errors pop up and what you can do to fix this.
Why this error occurs so much on 64-bit systems
First of all you need to know what's the difference between 32-bits and 64-bits systems.
Operating Systems that run on 64-bits have a slightly different folder/registry structure than 32-bits systems do.
Most of the system files (including your ODBC connections!) are in a different place on 64-bits systems (C:\Windows\SysWOW64\odbcad32.exe) than they are on 32-bits systems (C:\Windows\system32\odbcad32.exe).
This specific error is very, very often caused because you created your Database connections in the 32-bits version of your ODBC connections.
What happens?
You launch your server and it will look for the ODBC connection in the 64-bits version and it can't find them.
So it generates this lovely error.
The fix...(kinda)
It's quite simple if you know the previous information.
Navigate to your Windows folder and find the folder "SysWOW64".
Within that folder look for "odbcad32.exe" and launch it.
These are your 64-bits ODBC connections.
Add the necessary ODBC connections in this program's System DSN and the error should be gone.
What if this didn't fix it?
That's still possible. It's not 100% certain that this is the cause of the error.
Other things to check are:
- Can you actually connect to the SQL server from where your binaries are hosted?
- Did you enter the right SQL user/password in your config-files? (Check them, even if you think they are right!!)
- Does your security software allow your server binaries to establish a connection to your SQL server?
