on 04-20-2010 4:12 AM
hi,
I have BO installed in 64 Bit windows OS and the mysql data server in 32bit windows OS. i created DNS on the server for the data server. when i click on test connection, I'm getting a message
DBD:[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified.
i think this error is due to Os .
so how do i resolve this issue?
regards
sunil kumar koneru
Try running the 32bit ODBC admin tool:
c:\windows\sysWOW64\odbcad32.exe
or
c:\windows\system32\odbcad32.exe
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Facing the issue that maxDB client is 64Bit only. So it won't show up in the 32Bit ODBC admin client and therefore can't be set up. Installing 32Bit maxDB client or ODBC driver isn't possible, while the setup refuses the install:
example (this is true for all TGZ contained including base and ODBC)
WRN: software in package "Fastload API" (FASTLOAD.TGZ) isn't runnable on your system
magic string: MS Windows 32-bit i386 executable dll
YOUR SYSTEM: architecture = AMD64
YOUR SYSTEM: subversion = Service Pack 2
YOUR SYSTEM: system = Windows
YOUR SYSTEM: version = NT 5.2
Yep! That's the ugly truth.
One workaround could be to install the rather outdated 7.6.00.35 version that is shipped with many ERP DVD install sets.
This versions setup routines don't complain about a 32bit package that is not installable under a 64bit OS.
I guess maxDB dev guys should re-consider to allow at least 32 Bit client installations (or BASE + ODBC part) for Win x64 as long as BOBJ depends on 32Bit drivers while being 32 Bit itself.
Alternatives could be to install BOBJ on 32 Bit host OS only (if you know that before and can live with the memory management of a 32 Bit OS)
Hi you should install on your local mashine the same version of ODBC driver for MySQL likу in the server (in my situation it was 3.51)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In this case with maxDB it was not possible to match source DB version. While the system that needed connection to BOBJ was rel7.7 it was not possible to install ODBC drivers from the maxDB client installer > 7.6.00.35
Higher patch levels or releases went
INSTALLER_INFO: Version = 7.6.06 Build 008-123-224-525
INSTALLER_INFO: Changelist = 224525
INSTALLER_INFO: MakeId = 435925
INSTALLER_INFO: Type = kit
SYS_INFO: Host name = BOBBY
SYS_INFO: System = Windows
SYS_INFO: Architecture = AMD64
SYS_INFO: Version = NT 5.2
SYS_INFO: Subversion = Service Pack 2
MSG: InstallRegistry: space check ok: 29758306 kb on E: (567023269 kb total) available
MSG: install registry successfully locked
MSG: read 17 PACKAGES
MSG: net registry size = 120750 bytes
MSG: InstallRegistry: reserved 1024 kb disk space
MSG: collector found 18 archives
WRN: software in package "Base" (SDBBAS.TGZ) isn't runnable on your system
magic string: MS Windows 32-bit i386 executable
YOUR SYSTEM: architecture = AMD64
YOUR SYSTEM: subversion = Service Pack 2
YOUR SYSTEM: system = Windows
YOUR SYSTEM: version = NT 5.2
WRN: software in package "ODBC" (SDBODBC.TGZ) isn't runnable on your system
magic string: MS Windows 32-bit i386 executable dll
YOUR SYSTEM: architecture = AMD64
YOUR SYSTEM: subversion = Service Pack 2
YOUR SYSTEM: system = Windows
YOUR SYSTEM: version = NT 5.2
The maxDB guys should do something about this or it least point out proper solution(s).
Edited by: SAP SAPBASIS on Jun 28, 2010 8:54 AM
User | Count |
---|---|
83 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.