Could not use ''; file already in use. error - strange variation

The error:

Microsoft JET Database Engine (0x80004005)
Could not use ''; file already in use.

I know that there are many posts regarding this issue. As those reading this may have guessed, we are afflicted with this cryptic and useless error message. We have tried many solutions that have been posted at this website and others regarding this issue and have not had complete success in resolving it.

The variation that I mentioned is that this error only appears when we are logged onto a domain. The name of the computer running the IIS server is BRNT and runs Win2k. When we log on as Administrator to the local machine the server seems to run well and does not display the error. However when we log on to a different domain we get the above mentioned error. This leads us to beleive that the error may be related to file permissions, but I wouldn't rule anything out.

Hopefully someone can offer some guidance as to how we might resolve this issue, given this new piece to the puzzle. Thanks in advance for any help that you can offer.

I have some old information on this problem maybe something here will help

http://www.dougscode.com/forum4/topic.asp?TOPIC_ID=16

Hi,
this error comes because of some connection which is left open.. Connection can be left opened in two cases

1. 
   Either you dont have externally close the connection using conn.Close(); command in your code.
   

1. 
   if in between page loading you direct your page to somewhere else.

to solve frstly wait till the open connection closes automatically and than slowly try the page till it loads fully. and check that you dont have any open connection in your code

In my experience I have seen that some time while creating reader, CommandBehaviour.CloseConnection does not close the connection so, keep practice of closing connection using conn.Close(); in bothe the cases ExecuteNonquery and ExecuteReader.

>>

I tried to solve this error approx for a week. Lastly I got the solution.

In most of the cases this error comes due to disabled impersonation in web.config file.

Add following things to enable impersonation in web.config file and your error will disappear.

<configuration>
<system.web>
<identity impersonate="true" />
</system.web>
</configuration>