运行 ASP 站点 SQL Server 6.5 on Windows Server 2008 R2
Running ASP site with SQL Server 6.5 on Windows Server 2008 R2
我有一个经典的 ASP 网站。当我 运行 在 Windows 2008 R2 服务器上本地站点时，它运行良好。当我从另一台机器连接到该站点并尝试通过 iis 7.5 提供该页面时，它失败并出现此错误：
Microsoft OLE DB Provider for SQL Server error '80004005'
asp 中失败的行是：
Set conSQL6 = Server.CreateObject("ADODB.Connection")
conSQL6.Open strConSQL6
当我 运行 在 Win 2003 服务器上使用相同的应用程序时，在服务器本地和远程都没有问题。
关于如何使这项工作有任何想法，完全重写不是一种选择:)
来自PRB: Troubleshooting Error 80004005 "Login Failed" in ASP
Cause
There are two reasons why this error may occur:
- Integrated security is turned on in the SQL Enterprise Manager, and the Microsoft Windows NT account that is being used has not been mapped to a SQL account.
- The User ID in the connection string is invalid or blank.
RESOLUTION
To resolve this problem, ensure that the following conditions are met:
- The Windows NT account is mapped to a SQL account.
- The User ID in the connection string is valid and is not blank.
Set standard security in SQL Server Enterprise Manager. To implement SQL Server standard security, follow these steps:
- From SQL Enterprise Manager, right-click the SQL Server name that appears in the Server Manager window, and then click Properties. (For SQL Server version 6.5 click Configure).
- Click Security Options, and then click Standard and Windows. (For SQL Server version 6.5 click Standard).
- The Password Synchronization option is turned off for that project if you are running under Microsoft Internet Information Server (IIS) 4.0.
我有一个经典的 ASP 网站。当我 运行 在 Windows 2008 R2 服务器上本地站点时，它运行良好。当我从另一台机器连接到该站点并尝试通过 iis 7.5 提供该页面时，它失败并出现此错误：
Microsoft OLE DB Provider for SQL Server error '80004005'
asp 中失败的行是：
Set conSQL6 = Server.CreateObject("ADODB.Connection")
conSQL6.Open strConSQL6
当我 运行 在 Win 2003 服务器上使用相同的应用程序时，在服务器本地和远程都没有问题。
关于如何使这项工作有任何想法，完全重写不是一种选择:)
来自PRB: Troubleshooting Error 80004005 "Login Failed" in ASP
Cause
There are two reasons why this error may occur:
- Integrated security is turned on in the SQL Enterprise Manager, and the Microsoft Windows NT account that is being used has not been mapped to a SQL account.
- The User ID in the connection string is invalid or blank.
RESOLUTION
To resolve this problem, ensure that the following conditions are met:
- The Windows NT account is mapped to a SQL account.
- The User ID in the connection string is valid and is not blank.
Set standard security in SQL Server Enterprise Manager. To implement SQL Server standard security, follow these steps:
- From SQL Enterprise Manager, right-click the SQL Server name that appears in the Server Manager window, and then click Properties. (For SQL Server version 6.5 click Configure).
- Click Security Options, and then click Standard and Windows. (For SQL Server version 6.5 click Standard).
- The Password Synchronization option is turned off for that project if you are running under Microsoft Internet Information Server (IIS) 4.0.