[lnkForumImage]
TotalShareware - Download Free Software

Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

microsoft.public.dotnet.framework.odbcnet

ASP.net error in OledbConnection with access 2000 db. db is on shared folder

BizWorld

12/7/2005 11:09:00 PM

My ASP.net application reads data from access 2000 db and write data in
SQL server.
Access Db application is on Network share folder. network share folder
permission is set to fullControl for Everyone. when i try to connect
with Access DB using OleDBConnection, it fails with the
message..................................................................

'H:\prodDB\prodData.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.....................................................................


While H is a mapped drive to network share. I run the same code in
Windows application, it worked fine. but when i Put this in ASP.net, it
fails with above error. I changed ProcessModel tag in Machine.config to
run under "system" user. and added identity tag in web.config file but
it work only on Dev machine. when i access dev URL from other machine
then this code fails.

I am stuck in this since last two days, it is very URGENT.

1 Answer

Paul Clement

12/8/2005 2:11:00 PM

0

On 7 Dec 2005 15:09:11 -0800, "BizWorld" <moonis.tahir@gmail.com> wrote:

&#164; My ASP.net application reads data from access 2000 db and write data in
&#164; SQL server.
&#164; Access Db application is on Network share folder. network share folder
&#164; permission is set to fullControl for Everyone. when i try to connect
&#164; with Access DB using OleDBConnection, it fails with the
&#164; message..................................................................
&#164;
&#164; ''H:\prodDB\prodData.mdb'' is not a valid path. Make sure that the path
&#164; name is spelled correctly and that you are connected to the server on
&#164; which the file
&#164; resides.....................................................................

I believe I responded to a similar message in another group. In any event you cannot use a mapped
path since IIS knows nothing about it. Use a UNC path instead.


Paul
~~~~
Microsoft MVP (Visual Basic)