Microsoft Access 2003 Disk Or Network Error

here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more disk or network error access about Stack Overflow the company Business Learn more about hiring developers or posting ads disk or network error 3043 with us Super User Questions Tags Users Badges Unanswered Ask Question _ Super User is a question and answer site for microsoft odbc microsoft access driver disk or network error computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to

Runtime Error 3043 Your Network Access Was Interrupted

the top MS Access 2003 - Disk or Network Error - NOT a Network Issue - Remote App - Win 2008 up vote 0 down vote favorite We have a Windows 2008 running terminal services, but as remote apps, not full desktops. There is a single database file, calc.mdb, that gives "Disk or Network Error". If it is accessed by a user with MS Access 2003 installed, it runs just creative solutions accounting disk or network error fine. However for our traveling users that access via the RemoteApp, then they get "Disk or Network Error". I have searched and just about everyone comes to a couple of conclusions: 1. It's a network error. 2. Recompile and/or compact it. It is certainly not #1 because I can verify that the network is fine. I have recompiled and compacted with no success (and besides you can open the database). From a client computer: A) Has no issue running another RemoteApp (such as Word, WordPad, or even another Access DB) B) Has no issue logging in via full remote desktop. C) Can run the database from Access 2003 locally installed D) Receives "Disk or Network Error" when opening via Remote-App. The event log shows nothing of any help that I could find. With all the various logs in Windows Server now, maybe somewhere else to look? It certainly seems related to the RemoteApp setup. Again, this is NOT A NETWORK ISSUE! This has been going on for months. I have verified it is not a network issue. And yes, as soon as I complete my current project, the next is to update these aging apps. EDIT: Additional Test based on comment: Copied offending DB to local computer. Re

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link error 3043 network access was interrupted above to proceed. To start viewing messages, select the forum that you want

Error 3043 Access

to visit from the selection below. Page 1 of 2 12 Last Jump to page: Results 1 to 40 of

Runtime Error 3043 Visual Basic

42 Thread: [RESOLVED] Disk or Network Error with CORRECT connection string Tweet Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode Feb http://superuser.com/questions/787474/ms-access-2003-disk-or-network-error-not-a-network-issue-remote-app-win 11th, 2010,01:35 AM #1 rack View Profile View Forum Posts Visit Homepage Thread Starter Fanatic Member Join Date Jul 2006 Location Anchorage, Alaska Posts 545 [RESOLVED] Disk or Network Error with CORRECT connection string So, entire situation. [ASP.NET] code (Shown below) running on an [IIS server] [Microsoft Access Database] sitting out on the company network folder I've gotten 1 of 2 seperate errors. 1. Disk or Network http://www.vbforums.com/showthread.php?603125-RESOLVED-Disk-or-Network-Error-with-CORRECT-connection-string Error 2. The Microsoft Jet database engine cannot open the file '\\---\---\---\---\test.mdb'. It is already opened exclusively by another user, or you need permission to view its data. For the first error, I made sure that IUSR, IWAM, and ASPNET have full access to the TMP and TEMP System Variable folders. It depends on how I specify the path. However, if I just type in gibberish in the path name, it gives the correct "invalid path" error below. '\\abcdefg\adsf\ehdsf\test.mdb' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides. So this leads me to belive that A) the path I am specifing is working B) the connection string is written correctly C) no one is accessing the file, I created it myself just to test this and no one would randomly go to this folder location and open it. What am I missing? Are there settings in IIS that I need to adjust on the ASP.NET IIS server machine? VB.NET Code: <%@Page Language="vb" Explicit="True" Debug="True"%><%@Import Namespace="System.Data"%><%@Import Namespace="System.Data.OleDb"%>