Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

error message which couldnt be solved 1

Status
Not open for further replies.

gunalan

Technical User
Jun 29, 2004
52
US
hi,

for some reasons we are getting this error message...


Vbscript Runtime error 'ASP 0185 : 3219'

[Microsoft][ODBC Microsoft Access Driver] The database has been placed in a state by an unknown user that prevents it from being opened or locked.

PPSurvey_conn.asp,line 21

what is reasons for this error...


Thank you...
 
db might be corrupt, folder permissions may have been altered

[thumbsup2]DreX
aKa - Robert
if all else fails, light it on fire and do the happy dance!
 
Since you're using Access, it could be as simple as someone on the server opening the .mdb file directly, openng a table in design view, and then just leaving it open, something that seems to lock the database up. It seems that if that temporary .ldb file exists, the web server can't access the database.

Assuming this is what happened and the database isn't still open in Access on the server, you may be able to just delete the .ldb file. That or open the database in Access on the server and then close it again (which should allow Access to clean things up and eliminate the .ldb file on its own).

Or what DreXor said.
 
One more thing. I have had to copy the db and delete the original as it was too corrupt to even open. Then open it and close it like previously mentioned.
 
come to think of it, the error might result from the folder not having delete permissions, without them the db can open and close but not get rid of it's .ldb ( cache ) file, and without being able to delete it, it cant overwrite it, and by the time the db is re-accessed it would be left in an unknown state by an alternate process.

problem is, if you've got that error, you'll have residual access to the folder, easiest thing to do is a mix of the prior posts ( without trying to convert to another DB system ) is make a new data folder for it, apply ISUR_Webservername change/modify permissions to the new folder, copy the .mdb from the original folder to the supplimental ( cant move it, it will be in use by system/IIS ) and try repointing your DSN/DSNLess Connection to the new location.

if you care to try not moving the data, you will need to stop IISAdmin / ( and put them on manual so no autostart ) , possibly reboot, go and delete the .ldb file, apply the permissions mentioned above, and re-starting your web services again... the reboot is to ensure all active connection attempts and so forth are completely cleared.



[thumbsup2]DreX
aKa - Robert
if all else fails, light it on fire and do the happy dance!
 
try checking/changing permissions on both the db and the folder...

Bastien

Cat, the other other white meat
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top