Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Backend crash 1

Status
Not open for further replies.

gransbpa

Programmer
Jun 5, 2001
98
NL
Hi there,

I have a backend database which keeps 'crashing'. When this happens, users can't log on anymore. The backend can be repaired, but after a few hours it usually crashes again. I know from the past that sometimes network errors can cause this to happen (this backend resides on a server and is approached from several client computers), but this does not seem to be the problem right now. Does anyone have an idea what is going on here?

Thanks
 
I have a similar problem. Check CPU usage on the server. We have found that it sometimes peaks at 100% and causes the Blue Screen. Is the server crashing? If the server crashes then the backend will probably become corrupt.

Do you compact on a regular basis? I find that this sometimes helps.

Is this a critical application? Consider moving to SQL Server as a back end. This was our decison and I am working out the plan right now.

Flash1.
 
What are you using for a server?

I have a NT4 sp6 server and have had very few problems since I made the following change to the registry:
--------------------
REGEDIT4

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters]
"CachedOpenLimit"=dword:00000000
"EnableOplocks"=dword:00000000
--------------------

I believe this disables opportunistic locks and caching. You can just copy the lines above into a .reg file and execute it to set the registry.

A software vendor had me do this for another application running on our network and it seems to have helped my Access db corruption problems.

I'm sure you are aware that changing the registry can be hazardous. So please use caution if you decide to do this.


 
Oh, yes, and make sure you compact your db.
I have seem many times that the repair function will work, but compact will fail.
This seems to be either because a relationship is being violated or some table just gets in a weird state.

You may have to resort to createing a blank db and then importing all your tables from the corrupt one. You would then have to reestablish all the relationships and set any security you have enabled.
 
Are you running mixed versions of Access?

I had a 97 backend with 97 and 2002 frontends accessing the data; it would crash at least once a week.

The company finally upgraded it all to Access 2002 (so now it's 2002 backend and frontends) and there hasn't been a crash since (4 months).

And I haven't compacted the backend for some time (I really should; it's about 8 MB whereas that would get compacted down to about 1.5..... I'm a slacker).
 

Thanks for all the help! I got some valuable tips.
 
Kraeg,
Thanks for the info.

I am running Access 97 but in the process of converting to 2002.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top