IIS7 / Win2008 上的 Nuget 服务器出现 w3wp.exe 故障
我意识到这是边缘非开发，但我是一名尝试创建 NuGet 服务器的开发人员，而不是 IIS 人员，所以希望这里有人经历过这一点。
我有一些跨多个应用程序使用的库，所以我想用它们制作 NuGet 包。我还想设置一个合适的 NuGet 服务器，以便与我合作的人员可以轻松访问，并简化与 CI 端的集成（从 TeamCity 构建推送新包）。我按照此处的说明进行操作，从“创建远程源”开始：
http://docs.nuget.org/docs/creating-packages/hosting-your-own-nuget-feeds
我严格遵循它，当然使用可用的最新版本的 NuGet.Server 包截至撰写时。它在我的使用 VS2010 的开发机上运行良好，因此我将其部署到实时服务器（Win2008、IIS7）。应用程序池以集成模式运行 .Net，应用程序使用 NetworkService 身份运行，并且我将指定包目录的完全权限授予了 Network Service 帐户。
然后，当我尝试访问该站点时，我立即在应用程序事件查看器中收到此错误：
错误应用程序 w3wp.exe，版本 7.0.6001.18000，时间戳 0x47919ed8，错误模块 ntdll.dll，版本 6.0.6001.18538，时间戳 0x4cb73957，异常代码0xc0000374，故障偏移0x00000000000a7857，进程ID 0xa8c，应用程序启动时间0x01cc9f77f1f23af0。
Web 服务器正在运行许多其他 Web 应用程序，其中大多数是 ASP.NET MVC，因此一般来说应该没问题。
对 IIS 不太了解的人如何找出导致此错误的原因？我没有可以依靠的 IIS 管理员，因此开发人员必须扮演 IT 人员的角色。 :|
I realize this is borderline non-development, but I'm a developer trying to create a NuGet Server, not an IIS guy, so hopefully someone here has experienced this.
I have some libraries used across several applications, so I wanted to make NuGet packages out of them. I also wanted to set up a proper NuGet server so that people collaborating with me would have easy access, and to ease the integration with the CI side (pushing new packages from TeamCity builds). I followed the instructions here, starting at "Creating Remote Feeds":
http://docs.nuget.org/docs/creating-packages/hosting-your-own-nuget-feeds
I followed it to the letter, of course using the latest version of the NuGet.Server package available as of writing. It worked fine on my dev box using VS2010, so I deployed it to the live server (Win2008, IIS7). The app pool is running .Net in Integrated mode, the app is running using the NetworkService identity, and I gave full rights on the designated packages directory to the Network Service account.
Then when I try to access the site, I immediately get this error in the Application event viewer:
Faulting application w3wp.exe, version 7.0.6001.18000, time stamp 0x47919ed8, faulting module ntdll.dll, version 6.0.6001.18538, time stamp 0x4cb73957, exception code 0xc0000374, fault offset 0x00000000000a7857, process id 0xa8c, application start time 0x01cc9f77f1f23af0.
The web server is running many other web applications, most of them ASP.NET MVC, so in general it should be fine.
How would someone not very knowledgeable on IIS go about finding out what causes this fault? I don't have an IIS admin to lean on, so the developer has to play IT guy. :|
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
如果
ntdll.dll出现故障，则说明出现了严重错误。我会再次尝试使用最新版本的 NuGet Gallery - 最近发生了很多变化。nuget.org 上的在线文档有点过时了。我们遵循这里的详细信息，这几乎是第一次工作：
http://www.codecapers.com/post/How-to-Set-Up-a-Local-NuGet-Gallery.aspx
If
ntdll.dllis faulting, something is badly wrong. I would try again with the latest version of NuGet Gallery - there have been many changes recently.The docs online at nuget.org are a bit out of date. We followed the details here, which worked pretty much first time:
http://www.codecapers.com/post/How-to-Set-Up-a-Local-NuGet-Gallery.aspx