Forums

ASP

This topic is locked

HTTP 500.100 - Internal Server Error

Posted 23 Aug 2001 21:06:14
1
has voted
23 Aug 2001 21:06:14 Viktor Farcic posted:
Until now, I had permanent internet connection and I did everything directly on hosting server. Now, for the first time, I tried to work localy (problems with connection) and I'm getting following message when trying to preview page with IIS on my comp.

**********
HTTP 500.100 - Internal Server Error - ASP error
Internet Information Services

------------------------------------

Technical Information (for support personnel)

Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
[Microsoft][ODBC Microsoft Access Driver] The Microsoft Jet database engine cannot open the file '(unknown)'. It is already opened exclusively by another user, or you need permission to view its data.
/mapalocal/index.asp, line 5
**********

As I know that DB in question isn't open. What can be the problem?????


OS: Windows 2000 Advanced Server
DB: MS Access 2000

Edited by - vfarcic on 08/24/2001 11:55:27

Replies

Replied 24 Aug 2001 20:16:25
24 Aug 2001 20:16:25 Viktor Farcic replied:
Anybody?!?!

Replied 24 Aug 2001 22:09:30
24 Aug 2001 22:09:30 Owen Eastwick replied:
Remember you can always search microsoft.com with your error messages.

Results for <b>Microsoft OLE DB Provider for ODBC Drivers (0x80004005)</b>

<b>SYMPTOMS</b>
An Active Server Pages (ASP) page returns the error:

Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC Microsoft Access 97 Driver] Couldn't use '(unknown)'; file already in use.
-or-
Microsoft OLE DB Provider for ODBC Drivers (0x80004005) [Microsoft][ODBC Microsoft Access Driver] The Microsoft Jet database engine cannot open the file '(unknown)'. It is already opened exclusively by another user, or you need permission to view its data.
This error can occur when the database is open in Access, or when a Visual InterDev project is open that contains a data connection to the database.



<b>CAUSE</b>
This is a Windows NT permissions problem. The account that is accessing the page doesn't have sufficient permissions to lock the database. The account would be either the anonymous account, by default the IUSR_&lt;machinename&gt;, or a specific user account if the page has been secured for authenticated access.



<b>RESOLUTION</b>
If the page is meant to be accessed anonymously, give the IUSR_&lt;machinename&gt; account full control to the ASP page, and the folder and files where the database is located. Additionally, if the path to the database is being referenced using UNC (\\Server\Share), ensure that the Share Permissions allow the IUSR_&lt;machinename&gt; account full access. This step applies even if the share is on the local Web server.

If the page has been secured such that the IUSR_&lt;machinename&gt; can't access the file or database, then ensure that the user's account that is being authenticated has full control to the appropriate folders and files.

At a minimum, the account being used needs Create, Destroy, Read, Write to work with the .ldb file. Specific permission can be applied to the database to limit access.

Regards

Owen.

Edited by - oeastwick on 08/24/2001 22:16:39
Replied 25 Aug 2001 09:59:58
25 Aug 2001 09:59:58 Viktor Farcic replied:
I tried that and it didn't help. In the meantime I managed to find the solution. It's simple and here it goes if anybody gets in same trouble. Go to advanced options of ODBC Setup and insert your Windows LogIn Name and Password.
Thanks anyway oeastwick.

<BLOCKQUOTE id=quote><font size=1 face="Verdana, Arial, Helvetica" id=quote>quote:<hr height=1 noshade id=quote>
Remember you can always search microsoft.com with your error messages.
<hr height=1 noshade id=quote></BLOCKQUOTE id=quote></font id=quote><font face="Verdana, Arial, Helvetica" size=2 id=quote>

Replied 02 Sep 2006 20:18:47
02 Sep 2006 20:18:47 elliott benzle replied:
I get the feeling that there is more than one solution to this problem. I'm very new to ASP and I don't really know the details of why this works but after messing around for a while this is what fixed the problem for me.

-using either internet explorer or windows explorer browse to the folder on your local server where the database is stored
-you'll find a small file with the same name as your database with a lock on it which is sub titled Microsoft Office Access Record-Locking Information (I don't know where this came from but it's there)
-right click on this and go to properties
-there will be a list titled "Group or user names" which looks something like this:

Administrators(shatter-kh97cor\administarators)
User name (shatter-kh97cor\user name)
Internet guest account (shatter-kh97cor\iusr_shatter-kh97cor)

(It will probably have more listings than this but I didn't want to type them all)

-Select the first option in the list (ie. Administrators(shatter-kh97cor\administrators))
-In the second list titled "Permissions for internet guest account" select the "allow"
check boxes for all choices
-Go down the top list and select "allow" for all the groups/user names for all the categories that are available
-then click the "apply" button and close the properties box
-now try connecting to your database again

-hopefully this will help you, I'm not sure why it works but it did for me

Good Luck

Reply to this topic