修复：“ Windows进程激活服务（WAS）由于遇到错误而正在停止。”

I m not yet clear what I did, but I m blogging it so it can be found if someone else has this issue.

我还不清楚我做了什么，但是我正在写博客，以便在其他人遇到此问题时可以到它。

For whatever reason, last week both of my Vista 64-bit machines suddenly stopped being able to start IIS (Internet Information Server). The service just wouldn t start. I started getting this error instead Cannot start service WSVC on Computer .  which wasn t too helpful.

无论出于何种原因，上周我的两台Vista 64位计算机突然都无法启动IIS(Internet信息服务器)。 该服务将无法启动。 我开始收到此错误，而不是“无法在计算机 。 上启动服务WSVC”，它并不太有用。

A visit to the System Event Log via the Event Viewer in Computer Management told me these four errors:

通过“计算机管理”中的“事件查看器”访问系统事件日志告诉我这四个错误：

The World Wide Web Publishing Service service depends on the Windows Process Activation Service service which failed to start because of the following error: The system cannot find the file specified.

“ World Wide Web Publishing服务服务取决于Windows Process Activation Service服务，该服务由于以下错误而无法启动：系统不到指定的文件。”

and

和

The Windows Process Activation Service service terminated with the following error:
The system cannot find the file specified.

“ Windows Process Activation Service服务终止，出现以下错误： 该系统不到指定的文件。”

and

和

Windows Process Activation Service (WAS) is stopping because it encountered an error. The data field contains the error number.

“ Windows进程激活服务(WAS)由于遇到错误而正在停止。数据字段包含错误号。”

and

和

The directory specified for the temporary application pool config files is either missing or is not accessible by the Windows Process Activation Service. Please specify an existing directory and/or ensure that it has proper access flags. The data field contains the error number.

“为临时应用程序池配置文件指定的目录已丢失，或者Windows Process Activation Service无法访问该目录。请指定现有目录和/或确保它具有正确的访问标志。数据字段包含错误号。”

Unfortunately there s little information to go on in any of these error messages. However, it s clear (as mud) from the last error that there s a directory missing or not accessible. I ll add anymore to that because it worked before. That means that something changed.

不幸的是，在这些错误消息中，几乎没有任何信息可以进行。 但是，从上一个错误中可以清楚地看到(目录显示为泥泞)目录丢失或无法访问。 我将在其中添加“ more”，因为它以前可以工作。 那意味着有些改变。

If IIS won t start because Windows Process Activation Service won t start, then I need to get WAS started up first. However, I don t know what directory it doesn t have access to.

如果由于Windows Process Activation Service无法启动而导致IIS无法启动，则需要首先启动WAS。 但是，我不知道它没有访问哪个目录。

I can see from the Services application that WAS isn t its own executable, but rather lives inside of an instance of , where a lot of services live.

从服务应用程序中可以看到，WAS不是其自己的可执行文件，而是存在于实例的内部，该实例中存在许多服务。

So I ll fire up Process Monitor and set the filters (filters are VERY important if you want to avoid being overwhelmed quickly in procmon) to show only processes.

因此，我将启动进程监视器并设置过滤器(如果您希望避免在procmon中Swift被淹没，则过滤器非常重要)仅显示进程。

Even still, there s a lot of processes out there and they will quickly fill the monitor up. I ll need to setup some strategic (read: guessed) highlighting as well.

即使如此，那里仍然有很多进程，它们会Swift填满监视器。 我还需要设置一些策略性的(突出显示：猜测)突出显示。

The hotkey to stop capturing in is Ctrl-E. Basically I ll clear the screen, hit Ctrl-E to capture, try to start WAS (pronounced WAAZ), watch it fail, the stop capture with Ctrl-E.

停止在中捕获的热键是Ctrl-E。 基本上，我将清除屏幕，按Ctrl-E进行捕获，尝试启动WAS(发音为WAAZ)，观察其失败，然后按Ctrl-E停止捕获。

Based on the vague message about application pools temporary files and a directory I ll make a guess and configure highlighting to find paths that contain temp, log, config or app in Process Monitor as seen in the screenshot below.

基于有关应用程序池临时文件和目录的模糊消息，我将进行猜测并配置突出显示以在过程监视器中查包含“ temp”，“ log”，“ config”或“ app”的路径，如屏幕快照所示。下面。

After I run the capture, I scroll around looking for suspicious stuff. One of the nice things about Process Monitor is that you can EXCLUDE things in a given capture after that fact. For example, I saw a pile of Audio and Media related stuff that was visually confusing and cluttering the point, so I excluded it.

运行捕获后，我会滚动寻可疑的东西。 Process Monitor的优点之一是，您可以在该事实之后排除给定捕获中的内容。 例如，我看到了一堆与音频和媒体相关的东西，这些东西在视觉上造成混乱和混乱，因此我将其排除在外。

The result is here:

结果在这里：

It looks like there SHOULD be a folder call c:\inetpub\temp\apppools and on my Vista 64 machines, in the last two weeks to a month, it just disappeared. o idea why. I just noticed recently when I tried to move from a local web development service to IIS itself.

看起来应该有一个名为c：\ inetpub \ temp \ apppools的文件夹，并且在我的Vista 64计算机上，在过去两周到一个月里，它只是消失了。 不知道为什么。 我刚刚注意到，当我尝试从本地Web开发服务迁移到IIS本身时。

I created the folder, started WAS, then IIS and I was back up and running.

我创建了文件夹，启动了WAS，然后启动了IIS，然后又开始运行。

I ll pass the feedback on to the WAS team about the obscure error messages, but I thought I d share this little ten minute debugging session to point out a few things that I think are important and possibly helpful, Dear Reader:

我会将有关晦涩的错误消息的反馈意见传达给WAS团队，但我想我将分享这个十分钟的调试会议，指出一些我认为重要且可能有用的事情，亲爱的读者：

• Know What Your Processes Are Doing (or at least, know how to find out)

  知道您的流程在做什么(或至少知道如何出答案)

• • Knowing how to look ISIDE the Windows Black Box using tools like ProcMon makes you realize that no OS is a Black Box at all. It s very empowering to know that you CA see inside.
    知道了如何使用ProcMon之类的工具在Windows“黑匣子”中查看外观，使您意识到根本没有操作系统是黑匣子。 很高兴知道您可以看到内部。

  • TASK: Learn Process Monitor and Process Explorer.

    任务：了解流程监视器和流程资源管理器。

• Enable Your Intuition

  启用直觉

• • Debugging is 95% tools and 5% intuition. Know what tools can get you that next bit of information you need to take the next step in your analysis.
    调试是95％的工具和5％的直觉。 知道哪些工具可以为您提供下一步进行下一步分析所需的信息。
  • If you feel you ve hit a wall in your analysis, knock that wall down. Your process is doing IO to a file/registry/device/network/etc. Watch it. Look for failures.
    如果您在分析中碰壁，请将壁撞倒。 您的进程正在对文件/注册表/设备/网络/等进行IO。 看它。 寻失败。

My next mission is to find out WHY and HOW this directory disappeared on both my machines. What did I install or run recently? Enjoy!c

我的下一个任务是出为什么该目录在我的两台计算机上都消失了。 我最近安装或运行了什么？ 享受！c

翻译自: https://www.hanselman/blog/fixed-windows-process-activation-service-was-is-stopping-because-it-encountered-an-error