Hallo All, can anyone of us help me in understanding if there is the possibility to install my SQL Anywhere v. 5.5.04 on a machine with Windows 7, and if yes, how to? Thanks a lot for your kind answer. Warmest Regards Ciao Fabio asked 13 Jul '11, 04:25 AidaEpi Volker Barth |
Version 5.x is "not supported", but it may work reasonably well on Windows 7. You will be operating in an environment that we have never tried and won't be able to help with. When Windows Vista first came out, we had to make some changes to SQL Anywhere 9 and up. These changes may identify issues you will encounter. This page from the SA10 documentation may provide additional insights: Windows Vista support issues In particular, you require administrator privileges more often under Windows Vista and Windows 7. In supported versions of SQL Anywhere, we added code to request permission to proceed with certain activities (called "elevated operations"). Without this code, the activity may simply fail. There were also issues with shared memory. Using TCP/IP may work better. If it is possible to move to 5.5.05 latest EBF, that would make a more stable platform to continue with, but as mentioned it is not easily available. You would have to open a support case. answered 13 Jul '11, 12:26 Steven McDowell Volker Barth |
have a look at SQL Anywhere Supported Platforms and Engineering Support Status. 9.0.2 is also officially supported on Windows 7 if you have the latest EBF 3924 So for 5.5.04 you might be lucky but I would suggest to upgrade, you will get lots of good stuff doing so. answered 13 Jul '11, 09:03 Martin If moving to 9.0.2 is not an option - I would at least recommend a "newer" version - For v5, the last EBF for Windows is 5.5.05.2817 from end of 2001, IIRC. Unfortunately (but understandably), it does not appear anymore on the SQL Anywhere download page. FWIW, running that old 5.5.05 EBF on Windows 2003 Server is mostly successful in my experience (though officially unsupported) but running on Windows 7 seems rather instable.
(13 Jul '11, 09:58)
Volker Barth
|
I've got it working on Win7 64bit with some registry entries culled from various places including http://www.developer.com/db/article.php/3712461/Installing-a-Custom-ODBC-Driver-on-Windows-for-SQL-Anywhere.htm. 1) Install as normal as an administrative user. 2) For good measure, I marked the executable files in %installfolder%\sqlany50\win32 as running in compatibility mode for WinXP SP3 and 'Run as administrator'. 3) Added a new string-value 'Sybase SQL Anywhere 5.0' at 'HKLM\Software\Wow6432Node\ODBC\ODBCInst.INI\ODBC Drivers' with a value of 'Installed'. 4) Added a new 'Sybase SQL Anywhere 5.0' key to 'HKLM\Software\Wow6432Node\ODBC\ODBCInst.INI'. 5) Added a new string-value 'Driver' with a value of '%installfolder%\sqlany50\win32\wod50t.dll'. 6) Added a new string-value 'Setup' with a value of '%installfolder%\sqlany50\win32\wod50t.dll'. 7) Added a new 'Sybase SQL Anywhere 5.0 Translator' key to 'HKLM\Software\Wow6432Node\ODBC\ODBCInst.INI'. 8) Added a new string-value 'Setup' with a value of '%installfolder%\sqlany50\win32\ wtr50t.dll'. 9) Added a new string-value 'Translator' with a value of '%installfolder%\sqlany50\win32\wtr50t.dll'. Paul. answered 07 Jun '13, 09:59 Pauly Breck Carter I may be wrong, but - would a normal install of the ODBC drivers not automatically add the entries 3-9 (and possibly more) you have made above - somewhat manually? FWIW, a "custom ODBC driver for SQL Anywhere" would be one with a non-standard name, however, the entries above (named "Sybase SQL Anywhere 5.0" and "Sybase SQL Anywhere 5.0 Translator") are exactly the same as on my box with a standard SA 5.5 install...
(07 Jun '13, 11:42)
Volker Barth
Step 2 may be the key, since I've been running SQL Anywhere 5.5 off-and-on for a long time on Win 7 64-bit, with all those registry entries, and it never stays up for more then a few minutes... long enough to do regression testing of Foxhound, but not long enough for, say, production work. Is it stable for you? ...if so, then I gotta try Step 2 :) FWIW steps 3 through 9 may be automated with a *.reg file that looks something like this (your folders may vary): Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBCINST.INI\ODBC Drivers] "Sybase SQL Anywhere 5.0"="Installed" [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBCINST.INI\ODBC Translators] "Sybase SQL Anywhere 5.0 Translator"="Installed" [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBCINST.INI\Sybase SQL Anywhere 5.0] "Driver"="C:\\Program Files (x86)\\Sybase\\SQL Anywhere 5.0\\win32\\wod50t.dll" "Setup"="C:\\Program Files (x86)\\Sybase\\SQL Anywhere 5.0\\win32\\wod50t.dll" [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBCINST.INI\Sybase SQL Anywhere 5.0 Translator] "Driver"="C:\\Program Files (x86)\\Sybase\\SQL Anywhere 5.0\\win32\\wtr50t.dll" "Setup"="C:\\Program Files (x86)\\Sybase\\SQL Anywhere 5.0\\win32\\wtr50t.dll"
(07 Jun '13, 11:42)
Breck Carter
|
Hi, all. I thought this thread might have expired long ago. I 'filed' my answer here for future reference in case I lost my notes! Re the ODBC drivers creating the registry entries, I can only go by what I found (or didn't find) in my own registry - they definitely weren't there so I popped them in and all seems well. Might be that the install routine was blocked from accessing the registry? Regarding stability, it seems okay on my test box - none of our production staff are running 64bit as yet for me to give the all clear. answered 12 Jun '13, 07:56 Pauly |
the easiest solution is to install Sybase Anywhere in "c:\Program Files\Sybase\SQL Anywhere 5.0". during Sybase Anywhere setup/installation change destination directory to "c:\Program Files\Sybase\SQL Anywhere 5.0" . answered 29 Jul '13, 23:40 captain |
Thanks all! I make up my mind: I will install Windows XP and then 5.5.04, and I think it will work.
Thanks again for your precious help.
Best Regards
Ciao
Fabio
Note that for v5.5 under XP the official support starts with build 5.5.05.2816, so you still might try to get that or a newer build.
IIRC, v5.5.04 had a major security issue when running several databases on the same server.