sherbang's questions

I've written the following playbook. I expect an error from the second play, but the first and third to run. What I get is the first running, the second failing, and the third is completely ignored.

If I make the second play succeed then the third play works.

How can I get the third play to execute even when the second play fails?

- name: First local task
  hosts: localhost
  tasks:
  - add_host:
      name: dummy.example.com
      groups: test

- name: Failing remote host
  hosts: test
  tasks:
    - debug:
        msg: 'test'

- name: "This one should run too?"
  hosts: localhost
  tasks:
    - debug:
        msg: 'success!'

I'm on a x64 Server 2008 system. I'm seeing these 2 error messages in my event log periodically:

WARNING: The LastCounter and LastHelp values of the performance registry are corrupted and need to be updated. The first and second DWORDs in the Data Section contain the original LastCounter and LastHelp values, respectively, while the third and fourth DWORDs in the Data Section contain the updated new values.

ERROR: The performance counter name string value in the registry is not formatted correctly. The malformed string is 17894. The first DWORD in the Data section contains the index value to the malformed string while the second and third DWORDs in the Data section contain the last valid index values.

Both of these have source as LoadPerf, and are followed by an information message from LoadPerf: Performance counters for the Backup Exec (Backup Exec) service were loaded successfully. The Record Data in the data section contains the new index values assigned to this service.

As I said before, these 3 messages repeat periodically.

KB 300956 leads me to believe that the performance counter library needs to be rebuilt. The instructions supposedly include 2008, but I don't have an i386 directory on my install CD, and can't find the perfc009.da_ or perfh009.da_ files anywhere on the cd.

So i guess I'm looking for 2 things. 1) simply where I can find those files for 2008 x64, and even better 2) if someone has dealt with these errors on server 2008 and can give me any advise.

Thanks.