Corrupt database

Looking for possible causes and remedies to a certain type of corruption in an Access 2000 db.

It's happened to the same customer 3 times in a year but I've never seen this before and it happens only to this customer.

Once damaged, the db can't be opened in Access. AOIndex is missing from MSysAccessObjects and about half of the indexes on user tables are missing. Aboult half of the relations are also missing. The damage seems to be centered on one table that has many (10) foreign keys.

The last time this happened we used VB to programatically import the data into a new copy of the database, and assumed that the problem was left behind in the old db. But now it has happened again. There are well over 1,000 customers using this same db structure, so what's up with this one customer?

Any ideas of what might cause this?

Thanks

Hi,

If you are comfortable with the fact it's not the database application
itself (how the data is accessed/manipulated/etc..) then I would look into
the following:

- ensuring all workstations have the latest version of JET, see
http://support.microsoft.com/?id=239114

- make sure the database file resides on a robust file server

- make sure network connectivity is solid (very possible that
there could be a workstation in that environment that is sporadically
dropping network connections)

Also, see the knowledge base article
http://support.microsoft.com/default...b;en-us;300216

There's also a known hotfix available in regards to Windows Redirector.
But before you open a support ticket to see if that hotfix applies to you
use the above first.


I hope this helps! If you have additional questions on this topic, please
respond back to this posting.


Regards,

Eric Butts
Microsoft Access Support

"Microsoft Security Announcement: Have you installed the patch for
Microsoft Security Bulletin MS03-026? If not Microsoft strongly advises
you to review the information at the following link regarding Microsoft
Security Bulletin MS03-026
http://www.microsoft.com/security/security_bulletins/ms03-026.asp and/or
to visit Windows Update at http://windowsupdate.microsoft.com/ to install
the patch. Running the SCAN program from the Windows Update site will help
to insure you are current with all security patches, not just MS03-026."

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

--------------------
| Thread-Topic: Corrupt database
| thread-index: AcRIAbVAQUltZjhjTKSE1RKUj+NU8A==
| X-WN-Post: microsoft.public.access.tablesdbdesign
| From: "=?Utf-8?B?SmF5IFZpbnRvbg==?="
| Subject: Corrupt database
| Date: Tue, 1 Jun 2004 10:56:04 -0700
| Lines: 11
| Message-ID:
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.access.tablesdbdesign
| Path: cpmsftngxa10.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.access.tablesdbdesign:80089
| NNTP-Posting-Host: tk2msftcmty1.phx.gbl 10.40.1.180
| X-Tomcat-NG: microsoft.public.access.tablesdbdesign
|
| Looking for possible causes and remedies to a certain type of corruption
in an Access 2000 db.

It's happened to the same customer 3 times in a year but I've never seen
this before and it happens only to this customer.

Once damaged, the db can't be opened in Access. AOIndex is missing from
MSysAccessObjects and about half of the indexes on user tables are missing.
Aboult half of the relations are also missing. The damage seems to be
centered on one table that has many (10) foreign keys.

The last time this happened we used VB to programatically import the data
into a new copy of the database, and assumed that the problem was left
behind in the old db. But now it has happened again. There are well over
1,000 customers using this same db structure, so what's up with this one
customer?

Any ideas of what might cause this?

Thanks
|

Eric, thanks for your fast reply. Much appreciated.

The user has begun the process (over dial-up) of getting their Win/Jet updates. In the meantime, can you give some possible ways that our app could have caused this?

Our backup routine includes a compact/repair. I talked to a guy at a data recovery shop who said that, if there happened to be garbage in a PK, the compact/repair could leave the db in this condition (AOIndex gone, some relations gone, some indexes gone).

With Access (VB as front end), all our PKs are autonumber so, based on this guy's advice, I don't know how we could have caused this. But, if there is a way for our code to be trashing this database, I need to know.

Any ideas?

I've seen cases where the code would cause corruption. However, unless you
are able to develop a repro of the code routine that causes corruption it's
very difficult to say what type of code routines can cause it.

Best bet is to ensure the workstations are uptodate and the File Server is
robust.

Regards,

Eric Butts
Microsoft Access Support

"Microsoft Security Announcement: Have you installed the patch for
Microsoft Security Bulletin MS03-026? If not Microsoft strongly advises
you to review the information at the following link regarding Microsoft
Security Bulletin MS03-026
http://www.microsoft.com/security/security_bulletins/ms03-026.asp and/or
to visit Windows Update at http://windowsupdate.microsoft.com/ to install
the patch. Running the SCAN program from the Windows Update site will help
to insure you are current with all security patches, not just MS03-026."

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


--------------------
| Thread-Topic: Corrupt database
| thread-index: AcRIK54VyL0yOtcpRGSGr3ek+Agldg==
| X-WN-Post: microsoft.public.access.tablesdbdesign
| From: "=?Utf-8?B?SmF5IFZpbnRvbg==?="
| References:

| Subject: Corrupt database
| Date: Tue, 1 Jun 2004 15:56:04 -0700
| Lines: 10
| Message-ID:
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.access.tablesdbdesign
| Path: cpmsftngxa10.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.access.tablesdbdesign:80118
| NNTP-Posting-Host: tk2msftcmty1.phx.gbl 10.40.1.180
| X-Tomcat-NG: microsoft.public.access.tablesdbdesign
|
| Eric, thanks for your fast reply. Much appreciated.

The user has begun the process (over dial-up) of getting their Win/Jet
updates. In the meantime, can you give some possible ways that our app
could have caused this?

Our backup routine includes a compact/repair. I talked to a guy at a data
recovery shop who said that, if there happened to be garbage in a PK, the
compact/repair could leave the db in this condition (AOIndex gone, some
relations gone, some indexes gone).

With Access (VB as front end), all our PKs are autonumber so, based on this
guy's advice, I don't know how we could have caused this. But, if there is
a way for our code to be trashing this database, I need to know.

Any ideas?

|

Eric,

The immediate problem may be solved thanks to this ADOX code I found:

http://allenbrowne.com/ser-40.html

I re-wrote it for VB/DAO and sent it as a patch. It seems to have fixed the problem for both customers (a second complained after my first post) because both had problems with duplicate autonumber PKs. I'll also include it the startup for our app to make sure there are no lurking issues.

Jay