Database is crashing

  • Thread starter Thread starter Bauji
  • Start date Start date
B

Bauji

We are using a ms access application 10 users is sharing this application and my database crashed many tiome s ia day. Every time I used to repair the database. Is there any way to avoid this error or manage programmatically.

From my findings, when the database is closed, the user leaves the database in a suspect state as discussed on this link (i verified this by using the JetUtils.exe utililty:
http://www.experts-exchange.com/Databases/MS_Access/Q_20694891.html

Let me know if you have any ideas on how to stabilize their database and provide a quote for repairs if you know what needs to be done.

*-----------------------------------------------------------------------------------------------
I am getting following error

"The database 'c:\accessapp\finance.mdb' needs to be repaired or is'nt a Microsoft Access database file.

You or another user may have unexpectedly quit Microsoft Access while a Microsoft Access database was open. Do you want to Microsoft Access to attempt to repair the database."

Once I clicn OK, again I got one more error


"You attempted to open to open a database that is already exclusively by Admin or machine 'AK1'. Try again when database is available"

Once I click ok, then got following error

"The database 'c:\accessapp\finance.mdb' can't be repaired or is'nt a Microsoft Access database file"

Once I clicn OK, again I got one more error
*------------------------------------------------------------------

Please let me know how do I handle this
 
Bauji,

I suspect that you may be having some instability problems
with your network. Do you have a good network person that
can run some diagnostics?

Gary Miller

We are using a ms access application 10 users is sharing
this application and my database crashed many tiome s ia
day. Every time I used to repair the database. Is there any
way to avoid this error or manage programmatically.

From my findings, when the database is closed, the user
leaves the database in a suspect state as discussed on this
link (i verified this by using the JetUtils.exe utililty:
http://www.experts-exchange.com/Databases/MS_Access/Q_206948
91.html

Let me know if you have any ideas on how to stabilize their
database and provide a quote for repairs if you know what
needs to be done.

*-----------------------------------------------------------
------------------------------------
I am getting following error

"The database 'c:\accessapp\finance.mdb' needs to be
repaired or is'nt a Microsoft Access database file.

You or another user may have unexpectedly quit Microsoft
Access while a Microsoft Access database was open. Do you
want to Microsoft Access to attempt to repair the database."

Once I clicn OK, again I got one more error


"You attempted to open to open a database that is already
exclusively by Admin or machine 'AK1'. Try again when
database is available"

Once I click ok, then got following error

"The database 'c:\accessapp\finance.mdb' can't be repaired
or is'nt a Microsoft Access database file"

Once I clicn OK, again I got one more error
*-----------------------------------------------------------
 
Is this database split into a FrontEnd/BackEnd with the
front end on each user's machines or are all 10 accessing
the same program at the same time? It should be the FE/BE
setup with a network and 10 users. If all are accessing the
same program over the network, I can imagine some problems
developing.

Another suggestion would be to import all of the objects
into a new database container and see if the problems
persist.

Gary Miller
 
Bauji said:
We are using a ms access application 10 users is sharing this
application and my database crashed many tiome s ia day. Every time I
used to repair the database. Is there any way to avoid this error or
manage programmatically.

From my findings, when the database is closed, the user leaves the
database in a suspect state as discussed on this link (i verified
this by using the JetUtils.exe utililty:
http://www.experts-exchange.com/Databases/MS_Access/Q_20694891.html

Let me know if you have any ideas on how to stabilize their database
and provide a quote for repairs if you know what needs to be done.

*---------------------------------------------------------------------
-------------------------- I am getting following error

"The database 'c:\accessapp\finance.mdb' needs to be repaired or
is'nt a Microsoft Access database file.

You or another user may have unexpectedly quit Microsoft Access while
a Microsoft Access database was open. Do you want to Microsoft Access
to attempt to repair the database."

Once I clicn OK, again I got one more error


"You attempted to open to open a database that is already exclusively
by Admin or machine 'AK1'. Try again when database is available"

Once I click ok, then got following error

"The database 'c:\accessapp\finance.mdb' can't be repaired or is'nt a
Microsoft Access database file"

Once I clicn OK, again I got one more error
*------------------------------------------------------------------

Please let me know how do I handle this
Click to expand...


As well as Gary's suggestion, have you got this database split into
front and back ends, with the back end Tables on the server and copies
of the same front end on each user's PC. This is how you should
configure Access for multiple users.

hth

Hugh
 
Bauji said:
We are using a ms access application 10 users is sharing this application and my database crashed many tiome s ia day.
Click to expand...

First thing I'd check is the OpLocks setting on the server.

Otherwise see the Access Corruptions FAQ at my website.

Tony

--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
Can you mention you are using what version of MS Access?
did you split the database to front and back end?

May
MCP in Access and SQL Server
-----Original Message-----
We are using a ms access application 10 users is sharing
Click to expand...
this application and my database crashed many tiome s ia
day. Every time I used to repair the database. Is there
any way to avoid this error or manage programmatically.
From my findings, when the database is closed, the user
Click to expand...
leaves the database in a suspect state as discussed on
this link (i verified this by using the JetUtils.exe
utililty:
http://www.experts- exchange.com/Databases/MS_Access/Q_20694891.html

Let me know if you have any ideas on how to stabilize
Click to expand...
their database and provide a quote for repairs if you know
what needs to be done.
*--------------------------------------------------------- --------------------------------------
I am getting following error

"The database 'c:\accessapp\finance.mdb' needs to be
Click to expand...
repaired or is'nt a Microsoft Access database file.
You or another user may have unexpectedly quit Microsoft
Click to expand...
Access while a Microsoft Access database was open. Do you
want to Microsoft Access to attempt to repair the
database."
Once I clicn OK, again I got one more error


"You attempted to open to open a database that is already
Click to expand...
exclusively by Admin or machine 'AK1'. Try again when
database is available"
Once I click ok, then got following error

"The database 'c:\accessapp\finance.mdb' can't be
Click to expand...
repaired or is'nt a Microsoft Access database file"
Once I clicn OK, again I got one more error
*--------------------------------------------------------- ---------

Please let me know how do I handle this
Click to expand...
01/09/2003
 
I have already discussed with this issue my inhouse network person and as
well as also called outside consultant. Network seems to be properly
configured.
 
We had the same problem for months (we did 15 minute backups of the
database) and we were using a FE/BE solution

We replaced machines, switches, everything. Our solution was to buy a new
server (P4), install Small Business Server and migrate to SQL.

We have not had one corruption since.

I realise that I may step on the toes of the guru's, but our situation was
similar, 10 users, and when a corruption puts the database down for an hour,
that's $3k in lost wages per hour, plus any other downtime as we were
handling approximately 2000 write transactions and approx 3000 read
transactions per day. (small number, but large for 10 users)

If there is a good way of stopping Access from not crashing when all of the
clients are good, please let me know.

Cheers,


John
 
Any terminal servers in your environment?

I had one DB crashing due to a corrupted TCP/IP protocol on a machine.
Re-installed TCP/IP, and a whole host of problems went away for that user.

Kevin
 
Back
Top