none
Server Connectivity issues RRS feed

  • Question

  • I have several access databases that I have been developing for my office. I have an issue where when they stay open after random intervals, I get a message that the network was interrupted. I started to try and troubleshoot the network which seemed to be okay. So I tried the following test where I made copies of the databases and saved them on another Windows 2012 server which is our WSUS server so doesn't really have any other services running. I loaded two instances of Access and opened the same database from the Shared location of the WSUS server as well as the shared location of the original File Server. When the Access instance lost connection, I was still able to use the copy which was on the WSUS server. Since the servers on the same network being access from my workstation, I can assume that the issue is not with the network connectivity but rather something on  the file server.

    Does anyone have any idea how I can about troubleshoot this issue to see what may be causing this.

    Thanks,

    Sam

    Thursday, June 2, 2016 2:47 PM

Answers

  • "The lockfile is a result of the disconnect. I delete the lock file, but it disconnects later again. I need to find the cause of the disconnect"

    You are perfectly correct!

    There are no networking issues with that server?  Have you checked the Event logs?
    Is it fully patched?  How does it compare to the other server for updates?
    It could be even something as silly as a defective patch cable (seen it in the past).


    Daniel Pineault, 2010-2012 Microsoft MVP
    http://www.cardaconsultants.com
    MS Access Tips and Code Samples: http://www.devhut.net





    Friday, June 10, 2016 1:24 PM

All replies

  • The database files might be corrupt in some way. When I've experienced that "network interrupted" error it usually meant there was a problem with the file, not the network.

    Import everything into a new database and compact to see if that makes the error go away.


    Bill Mosca
    www.thatlldoit.com
    http://tech.groups.yahoo.com/group/MS_Access_Professionals

    Thursday, June 2, 2016 3:37 PM
  • I will try but I have tried that already and since i am having this issue with multiple different databases, I didn't think it would be this.
    Thursday, June 2, 2016 4:16 PM
  • Hi Sam 7,

    Have you resolve your issue? If not, I suggest that you could open Access databases on other machine to check that this issue can be reproduced.

    Friday, June 3, 2016 9:48 AM
  • I can reproduce this on several machines. When the file is opened on the file server, it randomly gives this error. But on the WSUS server it works just fine.
    Friday, June 3, 2016 12:59 PM
  • My mistake. The file server is Windows 2008 R2

    Can this be the cause?

    https://support.microsoft.com/en-ca/kb/2956344

    Thanks,

    Friday, June 3, 2016 6:43 PM
  • My mistake. The file server is Windows 2008 R2

    Can this be the cause?

    https://support.microsoft.com/en-ca/kb/2956344

    Thanks,

    Could be. Check out your server's version number to see if it has been patched.

    Bill Mosca
    www.thatlldoit.com
    http://tech.groups.yahoo.com/group/MS_Access_Professionals

    Monday, June 6, 2016 6:13 PM
  • Applied the patch and rebooted but still have the issue
    Thursday, June 9, 2016 3:55 PM
  • The database is being run across a LAN (not wireless, and not WAN)?
    What's your network saturation like?  Any problems opening/saving large Excel or Word documents at different times of the day?
    I doubt it will help, but, your db compiles without any errors, and has been Compact and Repaired?
    Do you establish a persistent connection at the startup of your db?
    What's the file size of your database?


    Daniel Pineault, 2010-2012 Microsoft MVP
    http://www.cardaconsultants.com
    MS Access Tips and Code Samples: http://www.devhut.net

    Thursday, June 9, 2016 4:47 PM
  • One more idea, just as a test, create a share on a PC and place the BE there and see if you have the same issue.

    Daniel Pineault, 2010-2012 Microsoft MVP
    http://www.cardaconsultants.com
    MS Access Tips and Code Samples: http://www.devhut.net

    Thursday, June 9, 2016 4:49 PM
  • I did create a share on another Windows 2012 server and loaded up both instances of the file and the Windows 2012 did not lose connection.

    As I test I create a share on a different windows 2008 server and I am now testing. If it also loses connection I can safely assume it is a Windows 2008 setting somewhere. If not, than it would be specific to the first server that it was on.

    Regarding your first questions

    1. On a GB Lan
    2. No problems with any other applications
    3. Compacted and repair fine. But not using compiled db
    4. Not sure what persistent database setting is.
    5. around 6 MB

    Thursday, June 9, 2016 5:07 PM
  • So the original 2008 lost connection but the new 2008 stayed up, so it is an issue with something on this specific server as opposed to Windows 2008 Server
    Thursday, June 9, 2016 5:37 PM
  • >>>So the original 2008 lost connection but the new 2008 stayed up, so it is an issue with something on this specific server as opposed to Windows 2008 Server

    According to your description, if you access database loses the connection abruptly, you will often get the "Disk or Network" error, could you find the lockfile to be left hanging? I suggest that you could do is delete that lockfile, and allow Access to recreate it as needed.
    Friday, June 10, 2016 7:13 AM
  • The lockfile is a result of the disconnect. I delete the lock file, but it disconnects later again. I need to find the cause of the disconnect.
    Friday, June 10, 2016 1:16 PM
  • "The lockfile is a result of the disconnect. I delete the lock file, but it disconnects later again. I need to find the cause of the disconnect"

    You are perfectly correct!

    There are no networking issues with that server?  Have you checked the Event logs?
    Is it fully patched?  How does it compare to the other server for updates?
    It could be even something as silly as a defective patch cable (seen it in the past).


    Daniel Pineault, 2010-2012 Microsoft MVP
    http://www.cardaconsultants.com
    MS Access Tips and Code Samples: http://www.devhut.net





    Friday, June 10, 2016 1:24 PM