Ask a questionAsk a question
 

QuestionFetch data from SQL Server 6.5

  • Wednesday, November 04, 2009 12:17 PMOlof Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    In SSIS 2005, connection manager i get 'Test connection failed because of an error in initializing provider' when I try to connect to a SQL Server 6.5 database using Microsoft OLE DB provider with a SQL server account. I'm trying to do this on a Windows 7 64 bit machine.

    What do I need to do?

All Replies

  • Wednesday, November 04, 2009 4:55 PMRaj Kasi - MSFTModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    What is the OLEDB Provider that you are using SQL Native Client (SQLNCLI) (or) Microsoft OLE DB Provider for SQL Server (SQLOLEDB)?
    This posting is provided "AS IS" with no warranties, and confers no rights
  • Friday, November 06, 2009 5:54 PMDan BenediktsonMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I believe SQL Native Client does not support SQL Server 6.5 - it supports only as far back as SQL Server 7.0. I'm honestly not sure about what is supported by SQLOLEDB.
    This post is provided 'as is' and confers no express or implied warranties or rights.
  • Friday, November 06, 2009 8:39 PMRaj Kasi - MSFTModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Yes Dan is correct. SQL Native Client does not support connecting to SQL Server 6.5, but with SQLOLEDB you can (you will not be able to access new functionality and features introduced with SQL Server 2005). Also based on the error message you reported it is not very clear what the exact issue is, so if you want you can tell us the provider you are using then we might be able to help better
    This posting is provided "AS IS" with no warranties, and confers no rights
  • Monday, November 09, 2009 10:06 AMOlof Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Thank you for your answers.(The alert system seems to be out of order :( )

    'Native OLE DB\Microsoft OLE DB Provider for SQL Server' is the provider chosen.
    I was trying to open a colleagues work when I first experienced it, and when I created I new package(and new connection) I experience same thing.

    Any ideas?