• Status: Solved
  • Priority: High
  • Security: Private
  • Views: 118
  • Last Modified:

Microsoft ODBC

Dear Experts,

My client using Win 7 Pro x64 bit are able to access their inhouse software.

Now with the new Processor, we cannot downgrade to Win 7.

It is a Win 10 Pro x64.

The issue now is in the odbcad32, System DNS, I tried to add the SQL server

It says
"Connection failed:
SQLState: '08002'
SQL Server Error: 0
[Microsoft]ODBC SQL Server Driver]SQL Server version 6.5 and all previous versions are no longer supported
0
Anonymous KH
Asked:
Anonymous KH
  • 7
  • 4
  • 2
  • +3
10 Solutions
 
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
Which SQL Server release is the server?
0
 
Anonymous KHIT EngineerAuthor Commented:
Hi! Qlemo,

The server version is Microsoft SQL Server 6.5
0
WEBINAR: 10 Easy Ways to Lose a Password

Join us on June 27th at 8 am PDT to learn about the methods that hackers use to lift real, working credentials from even the most security-savvy employees. We'll cover the importance of multi-factor authentication and how these solutions can better protect your business!

 
Anders Ebro (Microsoft MVP)Microsoft DeveloperCommented:
Maybe its time to use a newer version than what was released in 1996?
1
 
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
You are out of luck with such old software. The OS integrated MS SQL client in W10 does not support that. You might get SQL Native Client 2005 installed (x64 download: http://download.microsoft.com/download/2/7/c/27c60d49-6dbe-423e-9a9e-1c873f269484/sqlncli_x64.msi, install workaround: https://stackoverflow.com/questions/468538/client-components-for-sql-server-2005-enterprise-x64-wont-install-due-to-native).
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
The only way you can go back is to restore an old backup from the Operating System. Hope that you don't have the SQL databases in C: drive, even I'm afraid that's your case, since when SQL Server 6.5 was released, there were no SQL Server DBA role and was really Windows Administrators the ones that were managing SQL Server. Most of the time they solved issues with a simple reboot!!
0
 
Anonymous KHIT EngineerAuthor Commented:
Hi! Guys,

I don't think I can suggest to my client to upgrade their SQL version as they are using some in-house software to manage their client database and matters.

In Win7 Pro x64, I will go to C:\Windows\SysWOW64\odbcad32.exe

The System DNS tab which is empty I will add 3 records, they are

account, acct2000, and infobase

Under which SQL server to connect to I will select

WLAWSQL, WLAWSQL and X.x.x.x

Click Next

I select With SQL Server authentication using a login ID and password entered by the user user

In Connect to SQL Server to obtain default settings for the additional configuration options,

I enter Login ID: sa and the password.

I will put a tick to Change the default database is Account, Account and Infobase

Click Next and Finish.

Click on Test Data Source -> TESTS COMPLETED SUCCESSFULLY!

Click Ok and Ok

The record will display

Name               Driver
account            SQL Server
acct2000          SQL Server
infobase           SQL Server

When I did this for Win 10 Pro x64, only infobase was added successfully, the other two had the error.
0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
As a responsible consultant or employee, in my opinion, it's a REQUIREMENT that you advise your client to upgrade.  You (and they) should understand that software ages and eventually it WILL NOT WORK.  PERIOD.  Without using older software and eventually the hardware you want to use will also not work.  Further, it's almost certainly a security risk running 20 year old database servers that are YEARS from the last patch.  Data corruption, data theft, data loss are all increasingly possible and even probable.  I understand sometimes software makers go out and people love what they use... but responsible people evolve because they have to.  

You MAY be able to get it working today BUT, Windows 10 updates every 6 months... SOONER OR LATER, it won't work and there will be NOTHING you can do other than go buy older computers on ebay and use them.

Right now, you may find that your most practical solution isn't cheap either.  Setup an RDS server with a compatible version of Windows and run the application on RDS where users can connect to that and don't rely on ODBC drivers on the workstation.  This may be able to buy you time - you COULD downgrade a new server license to 2008 R2 or 2012 and those MIGHT still be (more) compatible than Windows 10.
0
 
Anonymous KHIT EngineerAuthor Commented:
Hi! Lee,

I know what you mean. The server is virtualised in a VMWare environemnt.

The thing is that the developer of the company has left a few years so there is no one who has the knowledge of upgrading their SQL servers to a new version.

We are hoping to get the user connected to the SQL database first, the upgrading will come until Microsoft ends the use of Win 7 Pro.
0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
They've ALREADY started to end Windows 7 - it won't run on new hardware!  Waiting until the last possible moment is also not a good strategy.  The feet dragging has to stop.  This is clearly posing a problem now - and it shouldn't be one because it should have been moved YEARS ago.  Now, understanding this is a problem TODAY, a migration should be SERIOUSLY undertaken while it only affects a minimal number of systems, not waiting until it's going to bring the company to a screeching halt.
0
 
Anonymous KHIT EngineerAuthor Commented:
My boss told me that the Windows 7 Pro is using a different driver

In the SQL Server driver, - it shoud be version 6.01.7601.17514, hopefully can find this driver for Win10 is there any compatibility issue where it does not Win10?
0
 
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
Did you have a try on installing a SQL Native Driver as I told above? That is an older driver than what you get with W10.
0
 
Anonymous KHIT EngineerAuthor Commented:
Hi! Qlemo,

I am tring to find v6.01.7601.17514 for Windows 10.
0
 
Anonymous KHIT EngineerAuthor Commented:
Hi! Qlemo,

After installing the native client software and after keying in the password and hit next this is the error message.

MS-SQL-Native-Client-error.JPG
0
 
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
The versions were 6.5, 7.0, 2000, 2005, ... so my hope was the client allowing access to 6.5, but no. Bad luck. You cannot change the OS driver, and Native Client cannot be used either.
Using a VM for RDS or clients are your only options, I guess.
0
 
Anders Ebro (Microsoft MVP)Microsoft DeveloperCommented:
I doubt anyone here can tell you about compatibility issues between a 20 year old driver and windows 10. Why? Because you are very unlikely to find anyone running that old software, for very good reasons. I'm surprised its managed to keep running so far.

I realize an update/upgrade can be expensive, but ask your client like this: "If the system dead stops tomorrow, and it takes between 2 weeks and 2 months to get it updated and tested, what will the cost be? These migration projects needs to be undertaken well in advance.
0
 
Anonymous KHIT EngineerAuthor Commented:
We are thinking of installing a Virtual Winj7 Pro PC inside Win10.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 7
  • 4
  • 2
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now