IIS6 到 IIS7 - 根元素必须与引用文件“appSettings”的部分的名称匹配。
我正在将所有本地主机应用程序从 WinXP/IIS6 计算机移至 Win7/IIS7.5 计算机。我从WinXP的wwwroot目录复制了几个文件夹到Win7的wwwroot。然后创建一个虚拟目录并转换为应用程序。当我浏览此应用程序时，出现错误：
Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
Parser Error Message: The root element must match the name of the section referencing the file, 'appSettings'
Source Error:
Line 1: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
Line 2: <html xmlns="http://www.w3.org/1999/xhtml">
Line 3: <head>
Line 4: <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
Source File: C:\inetpub\wwwroot\iisstart.htm Line: 2
我缺少什么？
I am moving all my localhost applications from a WinXP/IIS6 machine to a Win7/IIS7.5 one. I copied a few folders from the wwwroot directory of WinXP to wwwroot of Win7. Then created a virtual directory and converted to an application. When I browse this application, I get the error:
Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
Parser Error Message: The root element must match the name of the section referencing the file, 'appSettings'
Source Error:
Line 1: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
Line 2: <html xmlns="http://www.w3.org/1999/xhtml">
Line 3: <head>
Line 4: <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
Source File: C:\inetpub\wwwroot\iisstart.htm Line: 2
What am I missing?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
该应用程序的默认应用程序池是.Net 4.0。将其更改为 v2.0 的另一个应用程序池，错误消失了。
The default app pool for this application was .Net 4.0. Changed it to another apppool of v2.0 and the error went away.