Ok, I fixed the first issue with P&P installation, then I had to deal with this next one.....
- Failed to create instances of performance counter '# of Connections Opened/Sec' - Couldn't get process information from remote machine..
-
Failed to create instances of performance counter 'Total Command Executions' - Couldn't get process information from remote machine..
-
Failed to create instances of performance counter 'Average Command Execution Time' - Couldn't get process information from remote machine..
Well it seems this is a permissions related error and it will cause the DAAB (Data Access Block) to fail when attempting to log instrumentation information. I found this helpful FAQ via MSDN on adding your process user to the correct security groups.
http://msdn.microsoft.com/netframework/programming/bcl/faq/SystemDiagnosticsProcessFAQ.aspx#Question8
How do I use the Process class under a non-admin account?
From Windows Server 2003, you will get an exception if you try to get process performance information under a non-admin account. The workaround is to add that account into the Performance Counter Users Group.