Microsoft KB Archive/193997

{|
 * width="100%"|

-

The information in this article applies to:


 * Microsoft Internet Information Server versions 1.0, 2.0, 3.0, 4.0
 * Microsoft SQL Server versions 4.2x, 6.0, 6.5, 7.0

on the following platforms: NT 4.0

-

SUMMARY
When you use an Active Server Pages (ASP) application to access a SQL Server database that has not been set up to use an authenticated network protocol such as named pipes, an error that denies access to the data occurs.

MORE INFORMATION
To enable data access using named pipes, follow the instructions in the following article in the Microsoft Knowledge Base:

"Q159976 HOWTO: Connect to the Microsoft SQL Server via Named Pipes"

After Windows NT Server is updated, restart the ASP application. One way to restart an ASP application is to go back to the ASP application and modify the global.asa file in some trivial way. For example, add a space somewhere that will not change how the global.asa file is processed.

When the Global.asa file is modified and saved the ASP application restarts. This enables any session variables used (such as variables to store connection strings) to be refreshed, and because SQL Server is now able to authenticate the Windows NT Guest account, access to data is possible.

This technique is particularly important when you use the Data Form Wizard in Visual InterDev 1.0 because the wizard uses session variables extensively. For example, if Windows NT Server is not set up properly, you might receive an error when the connection is opened. Other times, the error might be encountered when a property, such as AbsolutePage, is applied to a recordset that is no longer accessible.

In all cases, the following steps enable ASP applications to access SQL Server data through named pipes:


 * 1) Ensure that the Windows NT Server that hosts SQL Server has been properly configured to use named pipes.
 * 2) Restart the ASP application.