Re: Linked Server to Access DB - ERROR

From: Russell Fields (RussellFields_at_NoMailPlease.Com)
Date: 01/16/04 

Date: Fri, 16 Jan 2004 15:51:18 -0500

John

First, there is the obvious BOL message:
Error 7399 at http://tinyurl.com/3292o

However, there are some other problems outlined in MSDN and the KB:
Microsoft Knowledge Base Article - 818182 (wrong version of Jet 4.0
installed on the SQL Server)

Hope that one of these helps you.

Russell Fields
"John" <anonymous@discussions.microsoft.com> wrote in message
news:088701c3dc34$da805740$a601280a@phx.gbl...
> I have created a linked server to a secured Access DB. I
> have the correct registry settings and can normally run
> queries via Query Analyzer against the database. But for
> some particular reason SQL Server will lose the ability to
> access the .mdw file for the secured database, I get this
> error:
>
> Server: Msg 7399, Level 16, State 1, Line 1
> OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an
> error.
> [OLE/DB provider returned message: Cannot open the
> Microsoft Jet engine workgroup information file.]
> OLE DB error trace [OLE/DB
> Provider 'Microsoft.Jet.OLEDB.4.0'
> IDBInitialize::Initialize returned 0x80004005: ].
>
> From within Access I can open the database just fine, but
> I can no longer do it from SQL Server. The only thing that
> corrects this is to restart SQL Server, then presto it
> works again. The .mdw and the Access database are in the
> same directory on a different server. It doesn't just
> happen to my machine it happens to another one as well.
>
> If anyone has any clue, please let me know.

Relevant Pages

  • Re: ERROR: Provider Management - Could not establish a connection to t
    ... If you have not yet created the SQL Server database, ... Can any data provider be used to ... Exception Details: System.Data.SqlClient.SqlException: A connection ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Disabling ASP.net 2.0 Membership
    ... I checked out the article you referenced and implemented my own provider. ... as a FoxPro database, an Oracle database, or other data sources. ... custom connection string so that I can use the Commerce Server SQL Server ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Need Help: Operating system error 3706
    ... Installing an additional component resolved the problem and the software is now able to connect to the database ... The developer is currently doing a complete rewrite/update of the program, including database functions. ... While this would require a modest re-write, it's not that tough to convert to a managed-code provider instead of the COM-based OLE DB provider. ... If the application is not based on .NET, then make sure the application is upgraded to use the SNAC (SQL Server Native Client) provider which is less trouble-prone than the older MDAC-based providers. ...
    (microsoft.public.sqlserver.connect)
  • Re: Replacing VS .NETs SQL Server Express Edition Integration
    ... You could write a custom membership provider. ... You could add the tables you need to your existing database table. ... As for configuring ASP.NET 2.0 membership to connect SQL Server 2000, ...
    (microsoft.public.dotnet.framework.aspnet)
  • RE: Access Databases and ASP.NET 2.0
    ... but I can say that Sql Server Express is free ... and can handle much more traffic than any access database can. ... As for the default provider, its set in the base directory of IIS or in your ... I cannot set up a new website to use an Access Database to hold the site ...
    (microsoft.public.vsnet.general)