Connection to Sybase ASE 12.5.0.3 from Windows Server 2008

Generally speaking you should be able to connect to an ASE dataserver anywhere on your network assuming a) your local interfaces/sql.ini file has the correct address for the dataserver (or alternatively you have a valid ODBC data source defined) and b) you have OS-certified software loaded/configured locally that can create the necessary network connection to the dataserver. ("Duh, Mark!" ?)

What's not clear (to me) is what you're trying to do ...

- is this Windows2008 32bit or 64bit?

- are you trying to install ASE 12.5.0.3 on Windows2008 and if so, what's the name of the installation program and where did you get it from? [need to determine if you've got a valid installation program and whether it's supported on Windows2008; platform certification @ sybase.com seems to indicate you need 12.5.4 ESD 4+ if running ASE on Windows2008]

- are you trying to install a client application/program on Windows2008 and if so, what is the name and version of the client application/program and where did you get it from? [need to know if this is a Sybase installation program vs a 3rd party application; will then need to determine if said software is certified on Windows2008]

12.5.3 is rather old for now.

But you can still use it in win2008. I assume you have installed ODBC components in your ASE database server on windows system.

All the thing you need do is to copy the subdir ODBC from %SYBASE%

into the target win2008 machine, like:

d:\SybaseASE_ODBC, and the ODBC is its subdir.

Then you can populate the following registry entry by execute it with admin privilege.

1. Windows Registry Editor Version 5.00
4. [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBCINST.INI\ODBC Drivers]
5. "SYBASE ASE ODBC Driver"="Installed"
8. [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBCINST.INI\Sybase ASE ODBC Driver]
9. "AltDefaults"="1"
10. "APILevel"="1"
11. "ConnectionFunctions"="YYY"
12. "CPTimeout"="60"
13. "DriverODBCVer"="04.10"
14. "FileUsage"="0"
15. "SQLLevel"="0"
16. "Driver"="d:\\SybaseASE_ODBC\\ODBC\\SYODASE.DLL"
17. "Setup"="d:\\SybaseASE_ODBC\\ODBC\\SYODASES.DLL"
18. "HelpRootDirectory"="d:\\SybaseASE_ODBC\\ODBC\\help"

For 32bit win2008, please remove Wow6432Node from the above reg path.

After poplute the above .reg,

On 32bit win2008, you can use odbcad32 to configure ODBC directly.

On 64bit win2008, just run c:\windows\syswow64\odbcad32 to configure ODBC DSN.

Hope it can help.

Hi Carl,

If your MSSQL 2008 is 64 bit you need to use our 64 bit drivers. If your MSSQL 2008 is 32 bit you can use the 32 bit drivers.

Sybase didn't offer 64 bit drivers until the later version 15.0.

So please see what bit your MSSQL 2008 is.

Then from there you can decide what to install.

PC-Client 15.5 and SDK 15.5 and higher are certified for a Windows 2008 machine.

When you install the PC-Client or SDK(Software Developers Kit for ASE) you need to make sure right click the autorun or setup.exe and run as administrator or the registery entries will not be put in due to the security on the Windows 2008 machine.

Once you get the drivers installed you also need to make sure the MDA scripts on the ASE are updated to your most current version of the drivers. These MDA scripts for odbc and oledb/ado.net contain fixes and improved performance for connectivity to the new drivers and the applications that use these drivers.There was a great ISUG article written by Wayne Smith called 'Hitching a ride' from 2008 that explains this whole procedure step by step.

Thanks,

Dawn

Hi Carl,

I don't know if you have been able to get the version 12.5.x client software installed yet.

However, there is an old problem with the installer in version 12.5.x where when you clicked on the setup.exe in the Windows Explorer, it would show a command window for about 1/2 second and then dissapear. The workaround for that problem was to go into the directory from a command prompt. Then set this environment variable.

set JAVA_COMPILER=NONE

Then run setup.exe from the command prompt.

That might resolve your problem.

Thank you,

Kevin