Results 1 to 3 of 3
  1. #1
    New Lounger
    Join Date
    Feb 2004
    Location
    Franktown, Colorado, USA
    Posts
    6
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Split Database - Disk/Network Error (2000/2003)

    I'm a SQL Server DBA that has inherited a 2000 split database that has been installed on 7 WinXP Pro boxes with Office 2003 connected in a peer-to-peer config via wireless network adapters. The front end machines will chug along just fine, then suddenly crash big-time and generate dozens of popup windows stating simply "Disk or network error". No errors are logged to either the system or the application logs so I have no idea what blew. All of the 7 PCs have 512MB RAM, and are totally isolated from the outside world so it is unlikely that a virus has been introduced.

    Just in case some of the old 2000 bugs might have made their presence known in 2003, I removed all of the subdatasheet names on the backend tables. I also turned off Name AutoCorrect just in case. The primary form used in this system is extremely functional but highly complex form with dozens of subforms and a really ugly user interface. This same split database seems to run just fine at another facility although there it runs under 2000 (without any of the "bug" fixes). The front-end database seems to work just fine on the PC that contains the backend component.

    I've spent 3 very long days and have managed to stabilize the system to where it only blows up every hour or so. Any ideas, anyone?

  2. #2
    Star Lounger
    Join Date
    Jun 2001
    Location
    Christchurch, New Zealand
    Posts
    73
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Split Database - Disk/Network Error (2000/2003)

    I have only struck this message when we have rebooted both the SQL Server/Network and I have had a database open.

    You say a wireless connection is it possible that the network is resetting the wireless connection each hour maybe? and therefore dropping the active connection between front-end/backend

    Could you test this by having a version of the front-end open on the server maybe, when the other PC's go down see if the server front-end version is still responding?

  3. #3
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,623
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: Split Database - Disk/Network Error (2000/2003)

    Did you manage to solve your problems? Access is very sensitive to network problems, and all it takes is a minor network error for it to start complaining - in fact that is one of the most common causes of corruption in Access databases. I take it that the backend is also in Access - you might consider moving the backend to SQL Server as the ODBC connection to SQL Server tables is much less prone to these kind of problems.
    Wendell

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •