• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2488
  • Last Modified:

SQL Database connection error

I have an application that talks to a backend SQL 2008 server.  This application used to be on a SQL 2005 server, and was moved to a SQL 2008 server.  When I moved it, I did not have all of the users created on the SQL 2008 server so my database had some orphaned users.  I have since resolved that, and everything is working as expected for the most part, EXCEPT:

This database is connected to by a client program called ServiceCEO (Insight Direct).  The SQL server is defined using a system DSN in the client OS ODBC.  For all systems that were previously connected to the application, we were able to change the DSN to the new server and the database connected without any issue.

HOWEVER, for NEW clients (clients that never had the program installed), after we set the DSN to the correct server and try to connect, we get the following error:

ADODB.Command Error: Requested operation requires an OLE DB Session object, which is not supported by the current provider. (3709)

All existing clients are able to connect without any issue, but all new clients get this error.  Does anyone know what I can do to resolve this?  
0
jkeegan123
Asked:
jkeegan123
  • 4
  • 3
1 Solution
 
David ToddSenior DBACommented:
Hi,

What OS are the new clients vs the existing clients running?

Regards
  David
0
 
jkeegan123Author Commented:
A mix of Windows 7 and Windows XP, with it working on both.
0
 
David ToddSenior DBACommented:
Hi,

Have you got the correct version of the netlibrary installed? It used to be the MDAC. Now some comes with the OS. It occurs to me that maybe the new clients need an old driver/netlib/whatever.

Regards
  David
0
Cloud Class® Course: Certified Penetration Testing

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

 
jkeegan123Author Commented:
Where do I get the netlibrary from?  I tried installing the SQL 2008 client tools, and that did not fix it.  What's more, I installed a blank version of the SQL application from the vendor using their default configurations (since this all started with a database move to another server) with a blank DB, etc...I was able to connect to it fine from existing PCs in the office, but new Windows 7 PCs not at all.

SO...is there a client connectivity pack that comes with Windows XP, or with earlier vesrions of Windows 7, that I would be missing on this new Windows 7 factory default x64 PC?  Is it even worth mentioning that it's Windows 7 X64 and all of the other PCs in the office are x86?
0
 
jkeegan123Author Commented:
I figured this issue out,it ended up being the fact that these PC's are x64. Apparently odbc configured in windows 7 64bit is not seen by legacy (32 bit) applications. To fix this,I just ran the 32 bit odbc configurator,duplicated the settings and dsn 's ,and we were set.

The 32 bit configurator is at:
C:\windows\syswow64\odbcad32.exe
1
 
David ToddSenior DBACommented:
Hi,

x64 is great if you can get the drivers.

We have a few legacy systems which only have 32bit odbc drivers. So our x64 SQL needs to go through a x86 32bit instance to connect.

Regards
  David
0
 
jkeegan123Author Commented:
This was the correct answer.
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: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

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