We have an Access DB installed on an XP machine (this is an IE accessable
application). Tables are replaced nightly via an automated process. This
has been working successfully for a couple months - now we are getting this
error... The autoprocess is unable to create the new tables.

Run-time error - '2147467259 (80004005)':
Failure creating file.

And...

We have another mdb on the 2003 Server, which has recently started giving us
the same error #, but with a different message. this one is manually
updated, so not as critical as the first one???
this one is:
Run-time error - '2147467259 (80004005)':
The MS Jet database engine cannot open in the file
'\\ipaddress\Inetpub\wwroot\property\db\TaxData.mdb'. It is already opened
exclusively by another user, or you need permission to view its data.

Any idea what might be causing this? since these both started happening
recently - of course updates come to mind... but I'm not identifying anything
that looks like it might be the source of the problem.
Any suggestions or references would be appreaciated - thanks in advance for
your time...

Cindy
--
Cindy B

Le 20 févr. 2008, =?Utf-8?B?Q2luZHkgQg==?= nous a si bien dit:

> We have an Access DB installed on an XP machine (this is an IE
> accessable application). Tables are replaced nightly via an automated
> process. This has been working successfully for a couple months -
> now we are getting this error... The autoprocess is unable to create
> the new tables.
>
> Run-time error - '2147467259 (80004005)':
> Failure creating file.
>
> And...
>
> We have another mdb on the 2003 Server, which has recently started
> giving us the same error #, but with a different message. this one is
> manually updated, so not as critical as the first one???
> this one is:
> Run-time error - '2147467259 (80004005)':
> The MS Jet database engine cannot open in the file
> '\\ipaddress\Inetpub\wwroot\property\db\TaxData.mdb'. It is already
> opened exclusively by another user, or you need permission to view its
> data.
>
> Any idea what might be causing this? since these both started
> happening recently - of course updates come to mind... but I'm not
> identifying anything that looks like it might be the source of the
> problem. Any suggestions or references would be appreaciated - thanks
> in advance for your time...
>
> Cindy

I found this on a website:


-It's a SQL Server error timeout error.

-Not sure why you're getting it. Possibly the user desk computer cannot
"see" the drive that SQL Server is on.

-Do you have the odbc drivers installed on the users pc
Assisted Solution

-Is it running of a Trusted connection with SQL Server?