Article ID: 271459
Article Last Modified on 6/30/2006
APPLIES TO
- Microsoft Internet Information Server 4.0
- Microsoft OLE DB Provider for Jet 4.0
- Microsoft Open Database Connectivity Driver for Access 4.0
This article was previously published under Q271459
We strongly recommend that all users upgrade to Microsoft Internet Information Services (IIS) version 6.0 running on Microsoft Windows Server 2003. IIS 6.0 significantly increases Web infrastructure security. For more information about IIS security-related topics, visit the following Microsoft Web site:
SYMPTOMS
A Microsoft Access database exists on a Netware 5 Server volume that is running only the TCP/IP protocol. By using either Open Database Connectivity (ODBC) or OLE Provider for Jet, an error message is returned that states that the file cannot be found. There are no errors in the event logs and the ODBC connection tests successfully. If you are using ODBC Driver for access, the error message is:
If you are using the OLE DB Provider for Jet, the error message is:
CAUSE
For access to be granted to the Netware File System, credentials must be passed that have the appropriate rights to the databases that you are attempting to access. By default, IIS attempts to pass credentials for the IUSER_MachineName account.
Netware uses the Netware Directory Service to authenticate users to its servers. In order to access any file systems, a legitimate account for the credentials being passed must exist on the Netware server.
RESOLUTION
To properly communicate with Microsoft Access Databases on a Netware 5 server by running only TCP/IP, please follow these steps exactly:
- On the IIS server that you want to communicate with Access, install Novell Netware Client for Windows NT (Required). During setup, choose a Custom Installation, choose to install into a NDS system, and choose only ip for the protocol.
Important Do not install Workstation Manager. - Install the latest version of MDAC. For more information, visit the following Microsoft Web site:
- Create an ODBC System DSN using the Microsoft Access Database driver. To do this, use one of the following methods:
- Click Select, and then enter the path to the database by using Universal Naming Convention (UNC) in the database name field to give the DSN a name. -or-
Add an OLE DB Provider for Jet Connection String to the asp page that is failing. An example of a Access Connection String is:
set conn = server.CreateObject("ADODB.Connection") conn.open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source='UNC Path to Netware 5 Goes Here';Persist Security Info=False"
- Click Select, and then enter the path to the database by using Universal Naming Convention (UNC) in the database name field to give the DSN a name. -or-
- On the Windows NT IIS server, use User Manager to change the IUSR password:
- In the Internet Service Manager, open the properties of the localhost. In the Master Properties section, click Edit.
- Click the Directory Security tab. In the Anonymous access section, click Edit, and then deselect NT to synchronize the password.
- Change the password to match the one that was set in User Manager.
- Stop and restart the IIS Services and test that Anonymous access is still working.
- Open the Netware Administrator found on the sys: volume under Public\WIN32 folder of the Netware 5 server. In the root of the container at which the server exists, create a IUSR_Machine Name account identical to the one that is on the Windows NT Server. On the properties of that user, click Password Restrictions and choose to have Require password checked. Click the Set Password button, and set the password to that of the NT account.
Important Do not require passwords to be changed on the Netware system. This is the most crucial step to the entire process. - In Netware Administrator, under the newly created IUSR properties, choose the Rights to files and directories tab, and then add the appropriate rights to the database files that need to accessed. At the least, READ permissions need to be given, unless changes are made through the Internet that require all permissions except supervisor and access control.
Note This process of configuring proper authentication could also be accomplished by granting rights to a NDS group object (that is, Web Access Group), and then making the IUSR_MachineName a member of this group.
WORKAROUND
If the preceding resolution is not satisfactory, a workaround can be produced that is typically used in older Netware versions. By using GSNW, a connection to the Netware 5 server could be established using the IPX/SPX protocol. However, please note that this requires that IPX be added to the Netware 5 Server as well as the Windows NT Server.
For installation instructions for the GSNW, please refer to the Windows NT 4.0 End-User Manual.
MORE INFORMATION
For more information about these procedures using IIS 5.0, click the following article number to view the article in the Microsoft Knowledge Base:
271228 Unable to obtain data from Access database residing on Netware 5 Server using ASP
In many cases, it is not a good idea to use Access databases as part of a Web-based application. For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
299973 Using Microsoft Jet with IIS
299974 Using Microsoft Jet with IIS
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.
Additional query words: foxpro iis 80004005
Keywords: kbprb kbpending KB271459
