RE: Linked Server

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: RobertP (anonymous_at_discussions.microsoft.com)
Date: 05/18/04 

Date: Mon, 17 May 2004 17:41:05 -0700

Trying to create a simple linked server in SQL Server 2000 (SP3a) for an Access 2003 database stored locally on a Windows 2003 server. Had done this many times on older server running Windows 2000 server, but never on this server. Keep getting the error seen in these newsgroups:

Error 7399: OLE DB provider 'SQLOLEDB' reported an error.
OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IDBInitialize::Initialize
returned 0x80004005: ]

Well I've read every post in this newsgroup and tried everything suggested, including security for the TEMP variables, modifying the registry reference to system.mdw, etc., etc...

However, there are a couple of posters who refer to a knowledgebase article that describes an update to Jet, SP8 I believe. However, a recent critical update installed on my server has increased the Jet version beyond what is described in that article to 4.0.8618.0.

Any reason to believe that update has koboshed this functionality?

Relevant Pages

  • Error 7391
    ... The operation could not be performed because the OLE DB ... OLE DB error trace [OLE/DB Provider 'SQLOLEDB' ... If I run just the select part of the query it works just ...
    (microsoft.public.sqlserver.connect)
  • connecting to two adp projects error-
    ... OLE DB error trace [OLE/DB Provider 'SQLOLEDB' ... The operation could not be performed because the OLE DB provider 'SQLOLEDB' ...
    (microsoft.public.access.adp.sqlserver)
  • RE: Linked Server
    ... OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IDBInitialize::Initialize ... Any reason to believe that update has koboshed this functionality? ...
    (microsoft.public.sqlserver.server)
  • RE: Linked Server
    ... OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IDBInitialize::Initialize ... Any reason to believe that update has koboshed this functionality? ...
    (microsoft.public.sqlserver.connect)
  • Re: OLEDB reports IS is not running
    ... Could not execute query against OLE DB provider 'msidxs'. ... OLE DB error trace [OLE/DB Provider 'msidxs' ...
    (microsoft.public.inetserver.indexserver)