[AccessD] Troubleshooting network issues

This wasn't one of my db's...and it was not a FE/BE scenario...just a single 
db.  And 'No' they couldn't do a Compact/repair...the record would not allow 
it...for some reason they did backups without compact repair...and when I 
said it 'crashed' I meant they could no longer even open the db.  The reason 
I brought it up was incase they were restoring...their backup db would run 
for a little while then completely crash.  I finally tried a repair on the 
backup db...it failed...and this is when I discovered the single bad record.

Sorry,

Mark


>From: "JWColby" <jwcolby at colbyconsulting.com>
>Reply-To: Access Developers discussion and problem 
>solving<accessd at databaseadvisors.com>
>To: "'Access Developers discussion and problem 
>solving'"<accessd at databaseadvisors.com>
>Subject: Re: [AccessD] Troubleshooting network issues
>Date: Tue, 20 Mar 2007 16:36:30 -0400
>
>Compact/Repairs.  The users can usually all get in, but some get issues 
>with
>specific error messages when they do specific things, and once anyone sees
>these kinds of things, no one can log in, get "BE not recognized / valid
>database" kind of messages.
>
>Are you saying that even after a compact / repair that there was a bad
>record?  The main Be has probably 150 tables.  I am not going to "discover"
>one specific bad record.
>
>
>John W. Colby
>Colby Consulting
>www.ColbyConsulting.com
>
>-----Original Message-----
>From: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark A Matte
>Sent: Tuesday, March 20, 2007 4:16 PM
>To: accessd at databaseadvisors.com
>Subject: Re: [AccessD] Troubleshooting network issues
>
>i.e. starting just
> >this morning, suddenly the main database be is getting corrupted, as in
> >more than a dozen times today.
>
>Were these 'dozen' corruptions fixed by the repair function...or restoring
>the db?
>
>Had a problem a couple of years ago... where db crashed...tried to do a
>repair/compact...both failed...finally restored from backup...db ran for an
>hour...then crashed again.
>
>Turned out that the backup had a single record that was corrupt(memo field 
>I
>think), but didn't immediately impact the performance...it would run for
>about an hour...then just crash(hard).
>
>I used a combination of sorting and misc functions to locate the offending
>record/field and loaded good records into new db.
>
>Just thought I'd share.
>
>Good Luck,
>
>Mark A. Matte
>
>
> >From: Jim Lawrence <accessd at shaw.ca>
> >Reply-To: Access Developers discussion and problem
> >solving<accessd at databaseadvisors.com>
> >To: "'Access Developers discussion and problem
> >solving'"<accessd at databaseadvisors.com>
> >Subject: Re: [AccessD] Troubleshooting network issues
> >Date: Tue, 20 Mar 2007 13:02:17 -0700
> >
> >Hi John:
> >
> >I have run into many similar issues in the past. In my case the
> >problems were around flaky NIC cards and in one case it was an IT guy,
> >in the evenings whom would keep rebooting the server to test some backup
>scripts.
> >Naturally not everyone had logged out of the Access application at the
> >end of the day.
> >
> >We used a packet-analyzer to spot the problem... not necessarily what
> >the product is designed for but its ability to keep an ongoing
> >transaction file of network traffic proved invaluable. There are some
> >similar open-source products out there that will do the same thing.
> >
> >HTH
> >Jim
> >
> >-----Original Message-----
> >From: accessd-bounces at databaseadvisors.com
> >[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of JWColby
> >Sent: Tuesday, March 20, 2007 12:12 PM
> >To: 'Access Developers discussion and problem solving'; 'Discussion of
> >Hardware and Software issues'
> >Subject: [AccessD] Troubleshooting network issues
> >
> >One of my clients is apparently having network issues, i.e. starting
> >just this morning, suddenly the main database be is getting corrupted,
> >as in more than a dozen times today.  The common wisdom is that
> >corrupted BEs is a network issue - NICS, cables, switches, routers etc.
> >Does anyone have any experience tracking down such a problem, any
> >recommendations for tools that would watch for intermittent network
> >connections, troubleshooting suggestions for trying to isolate the
> >offending piece of the puzzle?
> >
> >John W. Colby
> >Colby Consulting
> >www.ColbyConsulting.com
> >
> >--
> >AccessD mailing list
> >AccessD at databaseadvisors.com
> >http://databaseadvisors.com/mailman/listinfo/accessd
> >Website: http://www.databaseadvisors.com
> >
> >--
> >AccessD mailing list
> >AccessD at databaseadvisors.com
> >http://databaseadvisors.com/mailman/listinfo/accessd
> >Website: http://www.databaseadvisors.com
>
>_________________________________________________________________
>Get a FREE Web site, company branded e-mail and more from Microsoft Office
>Live! http://clk.atdmt.com/MRT/go/mcrssaub0050001411mrt/direct/01/
>
>--
>AccessD mailing list
>AccessD at databaseadvisors.com
>http://databaseadvisors.com/mailman/listinfo/accessd
>Website: http://www.databaseadvisors.com
>
>--
>AccessD mailing list
>AccessD at databaseadvisors.com
>http://databaseadvisors.com/mailman/listinfo/accessd
>Website: http://www.databaseadvisors.com

_________________________________________________________________
Live Search Maps – find all the local information you need, right when you 
need it. http://maps.live.com/?icid=hmtag2&FORM=MGAC01