Re: 0x80040e4d(DB_SEC_E_AUTH_FAILED) from ADOX::Catalog::Create



DB_SEC_E_AUTH_FAILED means that
The provider required initialization, but an authentication failed. The data
store was not created.

You may want to check this link to see if any of the conditions apply to you
that is causing authentication to fail:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q306269

Thanks
Suroor

--
This posting is provided "AS IS", with no warranties, and confers no rights.

Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

"Alexander Melentyev" <AlexanderMelentyev@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in message news:3D413553-6AC4-4D0F-A2B9-2E12E2C6237A@xxxxxxxxxxxxxxxx
> Hi All,
>
> In my application I use ADOX to create password protected database using
> code below:
>
> CComPtr<ADOX::_Catalog> spCatalog;
> spCatalog.CoCreateInstance(__uuidof(ADOX::Catalog)));
> ..
> HRESULT hr = spCatalog->raw_Create(bstrConnectionString, &vtConnection);
>
> The connection string which I supplied for
> Provider=Microsoft.Jet.OLEDB.4.0; Data Source="database.mdb"; Jet
> OLEDB:Create System Database=False; Jet OLEDB:Database Password="password"
>
> On some client's machines I have got error 0x80040e4d
> (DB_SEC_E_AUTH_FAILED)
> The error description provided by Jet: "Microsoft JET Database Engine
> Cannot
> start your application. The workgroup information file is missing or
> opened
> exclusively by another user."
> The problem is because I cannot reproduce this behavior on any my machine.
> The client and I both use the same versions of MDAC, Jet, Access Windows,
> SP.
> I didn't use user level security, the database is only password
> protected .
> so I don't understand what may be a reason for this error. It looks like
> authentification failed during provider initialization. Why?
>
> On my current machine I can remove any *.mdw files and database creation
> still successful.
> I found out that during database creation Jet tries to find (NOT CREATE)
> "system.mdb" in the current directory and if this file exists and is
> locked
> by another process then I got the 0x80040e4d HRESULT, but error
> description
> is quite different.
>
> So the question is: do you know the reason to return DB_SEC_E_AUTH_FAILED
> ADOX::Catalog::Create?
>
> Any thoughts are helpful.
>


.



Relevant Pages

  • 0x80040e4d(DB_SEC_E_AUTH_FAILED) from ADOX::Catalog::Create
    ... The connection string which I supplied for ... The error description provided by Jet: “Microsoft JET Database Engine Cannot ... I found out that during database creation Jet tries to find ...
    (microsoft.public.data.oledb)
  • Re: Database Connectivity
    ... Never was Jet mentioned anywhere at anytime. ... >> Microsoft Access Database Solutions, with not a single mention of Jet. ... front end, and the underlying database engine, JET. ... like SQL Server, Sybase, MySQL, etc. ...
    (comp.lang.python)
  • Re: Do not want data to auto sort
    ... you are deluding yourself if you think viewing data in the Access ... > in for a shock here but Access is not a database. ... The 'database' in question in usually Jet (it could be ... > then open a recordset write a the first portion of the data to a grid ...
    (microsoft.public.access.tablesdbdesign)
  • Re: Any reason why accessing Access should slowdown?
    ... On the MSACCESS / JET OLEDB front, you responded to a query I had about the ... Declared connection to Access database using string based on Jet OLDB ... Set up recordset filter in response to earlier input / selection ... ¤ I am writing a VB6 App using an Access database backend ...
    (microsoft.public.vb.database)
  • Re: Explorer CPU Usage while accessing database
    ... Since Jet is a file-based database, the answer is: ... I suspect you are seeing the Jet delayed-write system in action. ... creates an idle period, during which Jet (and any other processes that are ... opening your connection before each insert and closing it immediately after ...
    (microsoft.public.scripting.vbscript)