We have a customer that has already budgeted a server/client upgrade from 5.5.05.2817 to 12.0.1 for 2013. They are using our 32-bit application in XP workstations that creates local and network connections with NW servers (using Novell client 2 SP2).
Meanwhile, they need to install 5.5.05.2817 in their brand new Windows 7-64 bit boxes but the application is creating the errors below. They are currently using the same version of files accessing the NW servers without any issues.
Everything seems to be installed correctly on the 64-bit boxes and the required ODBC entries can be seen from the administrator at c:\windows\SysWOW64\odbcad32.exe.
The problem happens when the application tries to create the local and network database connections that seem to be dropped intermittently or can't be established at all.
We have isolated the application to only local connections during the troubleshooting phase but the issue is still being always recreated. We are now in the process of checking for antivirus and firewall settings that might prevent the connections to be established.
Windows 7 64-bit workstations Novell Client 2 SP2 Error: -100 Sqlstate: 08001 Unable to connect to database server: database engine not running Error: -101 Sqlstate: 08003 Connection not open: not connected to SQL database
We were able to replicate the issues reported in this forum that were relared to the incompatibilities of the Novell client 2 SP2 installed in the 64bit Windows 7 workstations.
Since other unanswered questions in this forum might refer to the same NW client causes I am adding the link for the Novell Client support for Windows 7 and Windows x64 incompatibility issues.
The Novell Client for Windows XP/2003 (4.91 SP5) is a 32 bit application, and is not supported on 64 bit operating systems. Novell has no plans to develop a client for Windows Server 2003 x64 or Windows XP Professional x64 Edition.
answered 22 Nov '12, 11:28
You may not have any luck running V5.5 on Windows 7 with reliability.
My experience has been that the V5.5 engine will run for a while, but will eventually crash even if it is idle... I have extensive experience with this because Foxhound is repeatedly tested on Version 5 databases and these tests are usually run on Windows 7 because I don't really care if the target crashes... the tests are quick and can be easily run again.
answered 13 Nov '12, 17:22
You're pushing your luck too far ;). Stick with NT/2000/XP or move from 5.5 to something more modern. And there is no sense to install 5.5 on the 64-bit OS anyway.
answered 14 Nov '12, 04:27