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

Hi, I have an access 2007 database that I have been developing a front end for in vb.NET for the past 3-4 weeks using vs2008 in a Windows 7 enviroment.

Yesterday I started getting an error of "Your network access was interrupted. To continue close the database and then open it again." This happens in the Form Load on the line:


Code:

I can go into access 2007 and view all the data fine and in vs2008 I can view the server explorer and browse the tables. However, under data sources if I try and preview the data, I get the same error message as before.

What confuses me the most is that the database is not stored on a server is just stored in My Documents. It was origionally stored on my desktop pc but has been copied to the My Documents on my laptop. But as I mentioned previously it has been working fine and has just all of a sudden started throwing this exception by my Try Catch routine.

FYI I have tried creating a new DB and importing the tables from the old DB but this hasn't solved the problem either.

I have literally worn out google trying to find an answer to my problem and really can't find anything. I'm hoping someone here will have a solution!!

Thanks in advance,

Paul Pitchford

A poster named schulter on another forum wrote:


Quote:

I have had the same problem, even on XP, but ONLY on 64-bit machines when
running the app as a Windows Service, i.e. userid SYSTEM. It took us a while
to figure it out and if we hadn't had a related issue concerning process
creation, we may have never figured it out.

Anyway, ACE/JET ODBC drivers need access to a Temp folder. Usually this is
not a problem as it goes to "C:\Documents and Settings\username\Local
Settings\Temp" or, on Vista and beyond to "C:\Users\username\AppData\LocalTemp". However, when you are running as SYSTEM, this location changes to: "C:Windows\system32\config\systemprofile\Local Settings\Temp" (on XP) or "C:Windows\system32\config\systemprofile\AppData\Local\Temp" (Vista+). Now, if
you are running the 32-bit ACE/JET-using app (must be 32-bit since ACE isn't
available in 64-bit) on a 64-bit PC, there's an automatic and hidden
translation of the "system32" path component to "SysWOW64", so the actual
path becomes "C:\Windows\SysWOW64\config\systemprofile\Local Settings\Temp"
or "C:\Windows\SysWOW64\config\systemprofile\AppData\Local\Temp". On some
machines that path may not exist.

Solution: *if* you are running on a 64-bit PC under userid SYSTEM, then
manually create the missing path components (no files needed, just the
folders) to create "C:\Windows\SysWOW64\config\systemprofile\Local SettingsTemp" (on XP) or "C:\Windows\SysWOW64\config\systemprofile
 

Does this offer any assistance?

Quote:

Posted by btseb2008 on 11/23/2009 5:22:34 AM (PST):


Does this offer any assistance?

Thanks very much for your assistance but I'm affraid the solution hasn't helped. What confuses me the most is that this has worked fine for quite sometime and only just has started to fail. It's not even as though the system has changed (to my knowledge... unless Windows has done something in the background).

Thanks,

Paul

Hi,

Well after a Windows 7 reinstall on my laptop the bloody thing still didn't work. With a new day and a fresh head I set about checking the source code as it had to be something there as everything else had been checked.

Beleive it or not I found the problem within about ten minutes! It was the connection string. It was pointing to the wrong path!! How silly. None the less as soon as I changed it, it worked immediatly!!

I just thought I'd share my silly problem incase someone has the same mental block as me!! :thumb:

Paul