ASP DB Connection Error 80004005

[Fary4u]

Hi any body know's where is the problem in following code ?
it's so simple but can't figer it out ? giving this error ?

[PHP]
Microsoft JET Database Engine error '80004005'
Cannot open database ''. It may not be a database that your application recognizes, or the file may be corrupt.
dbfile.asp, line 3
[/PHP]

[PHP]

dim db, strConn, Path
Path = Server.MapPath( db.mdb )
strConn = "PROVIDER=MICROSOFT.JET.OLEDB.4.0;DATA SOURCE=" & Path
Set db = Server.CreateObject("ADODB.Connection")
db.open strConn

[/PHP]

[DrBunchman]

Do you need to put quote marks around the name of your database? e.g.

 Path = Server.MapPath("db.mdb")

Dr B

[Fary4u]

Thx for the reply i've tried it but now giving new error on line 5
i think so it's same line error

i've just put some " " but still

well actually it's works on the local host & giving error on the NET Hosting server

[DrBunchman]

Is it a new error? If so what is it?

[Fary4u]

same error nothing else

[PHP]
Microsoft JET Database Engine error '80004005'
Cannot open database ''. It may not be a database that your application recognizes, or the file may be corrupt.
dbfile.asp, line 5
[/PHP]

[DrBunchman]

What version of Windows and what version of IIS are you running on the server?

There is a known problem using JET with Windows Server 2003 and IIS 6.0 which intermittently doesn't return used database connections to the pool, causing it to run out of resources. If this is the case with your set-up the helpful advice from MSDN is to change your database to SQL Server!

Dr B

[Fary4u]

it's working fine on windows xp iis 5 & DB is Access 2002

when i upload onto the webserver don't know why giving the same error ?

[DrBunchman]

What about the IIS and Windows versions on the server? What are they?

[Fary4u]

iis 5 & windows server 2003

[DrBunchman]

Have you got another server you could try it on? Have you done any googling on that error message?

Dr B

[jeffstl]

Have you tried opening the .mdb file itself ?

In other words download the copy being accessed by the code, and try to open it.

See if the database actually did get corrupted? Are you able to access the database at ALL anywhere in the application?