Cannot Log into Space Manager on x64 bit PC
Hint Ref: 020901160013
Hint Date: 16/01/2009
Hint Details:
PROBLEM: A client had reported that they had installed the Sybase 10.0.1 client on a Windows Vista 64 Bit PC and that they could not log into a remote Space Manager Database server using a 2.2.3.x version of Space Manager, even though when they 'Tested' the ODBC connection it displayed the message 'Connection Successful'.
ISSUE: Space Manager uses a 32 Bit Borland Database Engine to connect, via the ODBC, to the database and when the Borland Database Administrator was run, the 64 Bit ODBC in question could not be found.
SOLUTION: The Borland Database Engine installed as part of a standard Space Manager Client install is a 32 bit application and this will not 'see' any 64 Bit ODBCs with a 64 bit Driver. The solution is therefore to install a 32 Bit Sybase 10 client. Once done, make a note of all the settings in the original ODBC (host server IP address, timeouts, ODBC name etc.) and then delete it. Next create a new 32 Bit ODBC this time using the 32 Bit Sybase 10 driver, setting all other setting to the same as the original ODBC.
When the customer did this, they could log on to Space Manager successfully.
NOTE 1: When the customer ran the Sybase 10 client install again and just added the 32 Bit driver, it did not solve the problem. They first had to uninstall Sybase 10 (from the Programs icon in the control panel) and then reinstall ALL the necessary Sybase 10 components this time including the 32 bit driver.
NOTE 2: The ODBC administer in the Control Panel of a 64 Bit PC will only allow 64 Bit ODBCs to be maintained. The new Space Manager ODBC set up above MUST be created within the 32 Bit ODBC Administrator. This version of the administrator can be found in the following location:
C:\WINDOWS\SysWOW64\odbcad32.exe
(Please Note: This Procedure can be destructive and should only be used by Advanced Users. RADical Systems (UK) Limited or its Partners cannot be held responsible, in anyway, for any consequence of using this or any other Database Function, Procedure or SQL command. Responsibility resides solely with the user.
IT IS HIGHLY RECOMMENDED THAT A FULL AND VALID SPACE MANAGER DATABASE BACKUP IS TAKEN AND VERIFIED AS VALID BEFORE MAKING ANY CHANGES TO THE DATABASE.)