动易企业高级版MSSQL的网站出现的问题
动易企业高级版MSSQL的网站出现的问题
今天发现一动易企业高级版的客户无法完全显示页面.报错500.问题很棘手.
环境:WIN2000+IIS5+动易2005 SP1,MSSQL在另外一台MSSQL专用服务器上
错误解决:打开此客户网站,连接MSSQL的程序出现500错误,打开调试模式,出现如下错误:
---------------------------------------------------------------------------------------------------------------------
ADODB.Connection 错误 '800a0e78'
对象关闭时，操作不被允许。
PATH:\ADMIN\../conn.asp，行64
---------------------------------------------------------------------------------------------------------------------
不可能是动易企业版的问题吧,先检查权限,动易组件和IIS权限一切都正常.再打开此站点的论坛程序(本地ACCESS数据库的),一切正常,速度很快,初步排除了web server的问题.因为排除了我的WEB SERVER的问题,而SQL SERVER不是我司的服务器,我没有继续解决下去.后来客户自己咨询了动易客服,动易客服建议:
---------------------------------------------------------------------------------------------------------------------
原因：
两个原因：当一个数据库中包含有分别在不用机器上的许可关系时，
这也可能发生在同一台机器上，当你给一个关系设置了UNC路径，而另一个关系却是本地路径。
错误原因是：
当用户使用IIS匿名帐号登录后，对本地这台机器而言他是有权的，但是对于一个UNC路径的机器，
另外这台机器是不会认为你当前匿名登录的帐号在它那上面也是合法的。
这样它就不允许你访问它上面的资源，导致错误。
两个解决办法：
1。在IIS工具中，改变IIS匿名帐号成另外一个基于域的帐号。（也就是不使用匿名登录）
2。或则在那台你要访问资源的机器上也创建一个和当前匿名帐号同样的帐号，使用同样的密码。
---------------------------------------------------------------------------------------------------------------------
我收到此建议后,还是无从下手,1.建立一个基于域的账号.2.SQLSERVER不是我的.我试试把这个站点的匿名访问权限设置为ADMIN,出现了和动易客户说的一样的错误
---------------------------------------------------------------------------------------------------------------------
Microsoft OLE DB Provider for SQL Server 错误 '80004005'
[DBNMPNTW]ConnectionOpen (CreateFile()).
/conn.asp，行37
----------------------------------------------------------------------------------------------------------------------
感激查TECHNET,根据提示作好设置后,故障解决.
具体解决方法:在CMD下输入cliconfg.exe,出现MSSQL客户端网络实用工具,在通用选项卡下的默认网络库下选择TCP/IP,点击确定,就可以了.
附:微软原版资料:
SYMPTOMS
When you try to open a connection to a Microsoft SQL Server database from an Active Server Pages (ASP) page, you get the following error:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver][dbnmpntw]ConnectionOpen
(CreateFile()).
NOTE: This article assumes SQL Server is using standard security.
Back to the top
CAUSE
Microsoft Windows NT Server is denying access to the SQL Server. This error can be caused by the way Users, Groups, Rights, and Permissions are configured. Specifically, Microsoft Internet Information Server (IIS) does not have permissions to open a Named Pipe connection to the SQL Server.
Back to the top
RESOLUTION
If the ASP page was accessed anonymously, then the Windows NT/SQL Server computer needs to be able to authenticate the anonymous logon account. To do this use one of the following methods:
• Duplicate the anonymous account as a local account on the Windows NT/SQL Server computer with an identical name and password. To determine which account is used by IIS, open the WWW Properties dialog in the Internet Service Manager. The default account used is IUSR_<machinename>
• Change the anonymous user on the IIS computer to be a domain account so that the Windows NT/SQL computer can verify this account against the domain controller. To change which account is used, open the WWW Properties dialog box in the Internet Service Manager. Change the Anonymous Logon Username and password. Make sure the Username refers to a domain account (for example, Northamerica\JohnSmith).
If the ASP page requires authentication and any of the following is true, the error involves a Windows NT delegation issue where the security credentials are lost:
• The ASP page was accessed using Windows NT Challenge/Response, and SQL is on a different computer.
• The SQL Server is on the same computer as IIS and the server name is specified as opposed to selecting Local.
• The DSN has the "Trusted Connection" check box selected, and the SQL computer is set up to use Named Pipes.
To resolve this, use one of the following methods: • If IIS and SQL are on the same computer, select (local) instead of the server name, when you create the DSN. Also, ensure that "trusted connection" is not selected.
• If IIS and SQL are on separate computers, ensure that TCP/IP sockets are used to access the Windows NT/SQL computer. When Named Pipes are used to access the SQL Server, IIS tries to impersonate the authenticated user, but it does not have the ability to prove its identity. By using TCP/IP sockets, the connection between SQL and IIS is not authenticated. To enable TCP/IP sockets, run the SQL Server Setup program and select TCP/IP sockets under the Change Network Support option. You may also need to run the SQL Client Configuration Utility on the IIS computer and change the Net Library from Named Pipes to TCP/IP sockets. To start the SQL Client Configuration Utility, follow these steps:1. Click Start, and then click Run.
2. In the Open box, type cliconfg.exe, then click OK.
• You can also avoid this delegation issue by choosing to authenticate via Basic (Clear Text). This will give IIS the information needed to impersonate the authenticated user to the SQL Server. Be aware that with this authentication method, passwords are transmitted across the network, and could be stolen. To change to Basic authentication, open the WWW Properties dialog box from the Internet Service Manager, and select Basic (Clear Text), and clear the Windows NT Challenge Response check box.很不幸,我女朋友差点成为双性恋,有人却很羡慕.但是你真正爱的人分了爱给别人.那种感觉就覆盖了刺激和性幻想.觉醒吧!!!那种痛苦不亚于变心于其他男人.B4下天下所有同性恋,有病要早治
