Question Error: Access 2007 on Windows Server 2008 - has anyone seen this?

[Rx_]

Has anyone seen this error? The error came from MS Access.

Your network access was interrupted. To Continue, close the database and then open it again

The IT staff whrere I consult sent me a screen shot. They are setting up Windows Server 2008 to run Access 2007. Sorry I don't have more information.

Soon, we will run Access 2010.

 

[boblarson]

Is this a citrix machine and is the database split andthe backend on a separate file server?

 

[Rx_]

thanks for the speedy response. The IT staff validated:
it is citrix and FE and BE database are on the same File server

 

[boblarson]

thanks for the speedy response. The IT staff validated:
it is citrix and FE and BE database are on the same File server

So the frontend isn't on the Citrix server? If that is the case then the error is due to a network connection that failed. It can be a very tiny disruption but anything can cause Access to have issues. If the drop happens just at the time someone is in the database and the program is attempting to communicate with its backend then it will throw up its hands and return that error.

We've had that issue here as well (we're on Citrix and have a similar setup to yours, although we copy the frontend file from the file server to a temporary folder for that person's login on the Citrix machine. But it still can happen as the backend is on a different server and then it will have a problem. It doesn't matter that the frontend and backend are on the same file server as Access is being run from the Citrix box and it has the frontend running in its memory space.

 

[Rx_]

Forgot to mention that we also use a script that copies the Front End into a file folder for each user every time each user logs in. So, it does sound like the same setup.
Thanks again. A second location's experience is very valuable.

 

[gemma-the-husky]

the user might be able to test whether he can still access (ie get at) the back end folder directly from my computer/explorer.

if he can't it shows that there really is a network error.

 

[boblarson]

the user might be able to test whether he can still access (ie get at) the back end folder directly from my computer/explorer.

if he can't it shows that there is a newtwrok error.

That would only show if it is a continuous one. But the error will occur even if it drops for perhaps even milliseconds while an operation is in process which is moving data between locations. There may be a timeout period which it will wait before throwing the error, but if there is, I don't know what it is and from all observations it isn't very long.

 

[Banana]

Just to provide a perspective - because I run all of my development in virtual machines, i've observed that regardless of what OS / Access version I'm running if I'm not careful to quit Access before I suspend the virtual machine (to change for another virtual machine). Whenever I return back to that VM, Access gives me the same error even though in theory Access should have never even noticed it was "suspended" but freaks out when it wakes up.

Therefore, what I would want to look into is whether Citrix server allows some kind of suspension/sleep/whatever that may cause Access to loses its connection and return that error.

Hope that helps.

 

[Rx_]

The comments on the VM is very useful for my upcoming VM server to test Access 2010. All of the comments are truly appreciated.

Thanks everyone and have a great Fridy the 13th.
"I thank my Lucky Stars that I am not superstitious"