ODBC connect from IIS server to Access server

ODBC connect from IIS server to Access server

Post by derrick lakema » Sat, 12 Oct 2002 04:30:12

I am new to this odbc stuff.  I have inherited a NT4 IIS
website that uses asp and links to an access database on a
separate NT4 server.  I have moved the site onto a new W2K
IIS server and set up odbc connections on this server to
the access database server.  The two servers are on the
same domain with administrator and IUSER full control
rights to all directories on both servers. Help? Why do I
keep getting the below error?

-2147467259: [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.

P.S. Whenever I access a copy of the database on the local
D drive it works!

Thank you for any help!


ODBC connect from IIS server to Access server

Post by Rames » Sun, 13 Oct 2002 00:21:36

I do see you mentioning that IUSR has full control on all the directories
on both server.
You do realize that IUSR_Webservername is a local account on the webserver.
Do you have the same account IUSR_WebServerNAME on the database server with
the same password?
if so, do you have the allow IIS manage the password unchecked in IIS.
The following article talks about this specific scenario.
HOWTO: Connect to a Remote Access Database from Active Server Pages

Hope this helps.

Ramesh Thyagarajan, MCSD,MCDBA
Microsoft Developer support

This posting is provided "AS IS" with no warranties, and confers no rights.

Are you secure? For information about the Microsoft Strategic Technology
Protection Program and to order your FREE Security Tool Kit, please visit


1. Visual InterDev / IIS Server/ ODBC Connect to SQL Server 6.5

Here's one that's consumed too much of my life already :)

When creating an Active Server Page to connect to an ODBC Datasource, it is
required to hard-code the SQL Server Login/Password in the VBScript line:

<% objDBConnection.Open "PhoneList", "Username", "Password" %>

Where PhoneList is an ODBC DSN on the IIS Server.  This utilizes SQL
Server's Standard Security model over TCP/IP.  SQL Server also supports NT
Integrated Security through Trusted connections over either Named Pipes or
Multi-Protocol network libraries.  I would like to be able to utilize SQL's
Integrated Security to authenticate a user to a database from the client's

IIS Security allows for an NT Challenge/Response authentication, and you
can even get the name of the currently logged-in NT User from the client's
workstation running the browser. (Request.ServerVariables("LOGON_USER"))
Under standard security for SQL, you can pass this variable as a parameter
to the first line above, and if that SQL Login Name has no password, you're
This requires all login passwords in SQL to be empty, or to manage a
password list yourself in another table somewhere.

Since SQL Server can only establish trusted connections through
Multi-protocol clients, and the browser session is pure TCP/IP, you receive
a general network error when trying to establish a trusted SQL connection
from a browser.

I would like to know if anyone has been able to manage Web-based
authentication to SQL Server through the mechanisms already in place in NT
Server/IIS Server, or if this is an issue to be resolved in future releases
of the products?


3. Visual InterDev / IIS / ODBC Connect to SQL Server 6.5

4. context 8.0.5 vs. context (intermedia text) 8.1.7

5. ODBC timeout when connecting from ACCESS 97 to SQL Server 6.5 (heavy loaded server)

6. DBCC checktable SYSLOGS

7. IIS web server can not connect to DB server

8. Problem with shared memory initializing

9. HELP: Connecting a web server (IIS) to SQL Server

10. sql server connecting to an iis server

11. HELP: Connecting a web server (IIS) to SQL Server

12. IIS Virtual Directoary Management for SQL Server on remote vs local IIS Web Server

13. SQL Server ODBC access via IIS web page errors