Linked Server

>--Original Message--
>I am getting the following message when trying to use a
linked server with Microsoft Jet 4.0 OLE DB PROVIDER
>Error 7399: OLE DB provider 'SQLOLEDB' reported an error.
>OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
IDBInitialize::Initialize
>returned 0x80004005: ].
>
>Any help i can get would be great.
Did you edit the registry with full path name of the
Workgroup Information
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\JE
T\4.0
\Engines\System DB
Are you trying to connect Access or Excel
If excel read message from "borys.jarzembski@.bunge.com"
Sent: 2/25/2004 7:16:22 title: Microsoft excel Connection
Maybe you both have got the same cause of the problem.It might be permissions related:
814398 PRB: Error 7399 When You Run a Linked Server Query That Uses the OLE
DB
http://support.microsoft.com/?id=814398
Or a driver mismatch:
818182 PRB: Error Message: "Unspecified error" Occurs When SQL Server
Accesses
http://support.microsoft.com/?id=818182
There are several KB articles related to this error message, search
support.microsoft.com for "7399 and linked and IDBInitialize::Initialize".
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.|||Trying to create a simple linked server in SQL Server 2000 (SP3a) for an Acc
ess 2003 database stored locally on a Windows 2003 server. Had done this ma
ny times on older server running Windows 2000 server, but never on this serv
er. 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 d
escribed in that article to
4.0.8618.0.
Any reason to believe that update has koboshed this functionality?