Re: No SQL OLE DB connectivity

From: John Boatner, MCSD, MCDBA, MCSE, MCSA, MCDST (john.boatner_at_-nospam-j2tech.com)
Date: 04/08/04

  • Next message: Paul: "using a SUM function with a oledb.oledbConnection"
    Date: Thu, 8 Apr 2004 15:10:12 -0400
    
    

    Did you try everything I suggested? Renaming the dlls (they're in System32,
    and they're not ActiveX DLLs so using regsvr32.exe is pointless) will work,
    but Windows file protection will keep overwriting...you can install MDAC 2.8
    in safe mode, too.

    -- 
    Regards,
    John Boatner
    MCSD, MCDBA, MCSE, MCSA, MCDST
    J2 Technologies, Inc.
    http://www.j2tech.com
    "farqua" <farqua@news.com> wrote in message
    news:pan.2004.04.07.19.24.21.166885@news.com...
    > On Tue, 06 Apr 2004 22:49:17 -0400, John Boatner, MCSD, MCDBA, MCSE, MCSA,
    > MCDST wrote:
    >
    > > The behavior you are experiencing is probably caused by DLLs not being
    > > registered (specifically SQLSRV32.DLL and ODBCBCP.DLL). You can try
    > > installing the MDAC (http://www.microsoft.com/data) 2.7 SP1 Refresh, or
    2.8
    > > (I recommend 2.8).  If running the MDAC setup doesn't cure this, try
    > > renaming SQLSRV32.DLL and ODBCBCP.DLL in the %winroot%\system32 folder,
    and
    > > sqloledb.dll and oledb32.dll in %ProgramFiles%\Common Files\System\Ole
    DB -
    > > then try the installer again.
    > >
    > > As a last resort, extract MDAC_TYP.EXE to a temp folder (e.g.,
    mdac_typ.exe
    > > /t:c:\mdac_tmp) - open the temp folder where you extract mdac in
    Explorer,
    > > then right click on SQLNET.INF and select Install - this will "force
    feed"
    > > the SQL Net libraries into Windows.
    > >
    > > Regards,
    > > John Boatner
    > > MCSD, MCDBA, MCSE, MCSA, MCDST
    > > J2 Technologies, Inc.
    > > http://www.j2tech.com
    > >
    > >
    > > "farqua" <farqua@news.com> wrote in message
    > > news:pan.2004.04.04.07.31.02.941196@news.com...
    > >> I've loaded MSDE from the Office Pro 2003 CD onto my XP box. I haven't
    > >> been able to get MS Access to connect with the MS SQL Server at all. In
    > >> researching through Microsoft's site I find a test of the SQL OLE DB
    > >> provider where I create an empty desktop text document called Test.udl
    and
    > >> double click it. When I double click it, I get an error about not
    having a
    > >> provider. I would like to know how I can add or start the provider so
    that
    > >> I can use MSDE.
    > >>
    > >> Thanks
    >
    > I've tried multiple times to reload MDAC 2.8 to no avail. I even tried
    > MDAC 2.7. When I tried to register the dll's I get a dialog box message
    > that the dll was loaded but, "DllRegisterServer entry point was not found.
    > This file cannot be registered." I tried renaming and reloading the MDAC.
    > I tried extracting MDAC to a directory and forcing the SQL Net libraries.
    >
    > Unfortunately, I'm in some kind of configuration hell.
    >
    > What's interesting is that I can actually access the MS SQL Server using
    > osql and can actually create databases and tables using the commandline.
    > However, I think I'm more productive using MS Access, especially since I
    > am trying to convert an existing MS Access databases to MS SQL Server.
    >
    > I notice that I have ODBC connectivity (if the test connection is
    > correct). But I am unable to get in using ODBC.
    

  • Next message: Paul: "using a SUM function with a oledb.oledbConnection"

    Relevant Pages

    • Re: Sql Server Agent (2000) erroring out on DTS Packages
      ... DTSRun: Package execution complete. ... and a problem with a missing MDAC dll. ... On Sql Server 7, this was SQLAgentCmdExec. ... Specified driver could not be loaded due to system error 126 (MERANT MSSS ...
      (microsoft.public.sqlserver.dts)
    • Re: SQLDMO with VB6
      ... Tibor Karaszi, SQL Server MVP ... client side functionality without the need to install the SQL Server Client Utilities. ... MDAC does not install the Sqldmo.dll file or any of the many dependent DLLs associated with the ...
      (microsoft.public.sqlserver.tools)
    • Re: Any help here???
      ... > start looking for things that are non standard (like having MDAC installed). ... > Format your drive, do a new/clean install of XP, and go from there. ... >>> data provider is optimized for SQL Server. ... >>> I've never had any SQL Server connectivity problems since I've switch to ...
      (microsoft.public.dotnet.framework.aspnet)
    • RE: SQL server Login connection failed sqlstate 28000 sql server e
      ... mdac 2.8 - ran the mdac checker and everything is fine ... and reconnect to the sql server using odbc - dsn connection. ... Now when we make mods to the database, reconnect, then we get that error. ... please download Component Checker from the link below to make sure ...
      (microsoft.public.sqlserver.odbc)
    • Re: Help Please Wit Error
      ... Occasionally I receive the error you are mentioning when the SQL Server ... I have had to completely remove the MDAC and re-install it as well ... see an example of the connection string you are using. ... Please install Microsoft Data Access Components ...
      (microsoft.public.dotnet.csharp.general)