Error Accessing Processor Performance Counter Data
Exchange TeamApril 6, 200623 0 0 0 This release of ExPTA includes the following: 1. Perfmon data collection: Collect exctrlst performance data to log file or analyze previously collected logs. ExPTA can lodctr /r collect for durations between 5 minutes to 8 hours. Collection works remotely. Data is analyzed in 20 minute time ranges, and results are grouped by the time in which the problem occurred. You can analyze logs previously collected by ExPTA or via perfmon. ExPTA will expect that the performance counters listed below are included in any log that is analyzed. 2. Queue thresholds: SMTP Server\Categorizer Queue Length, Epoxy(IMAP)\Queue length, EPOXY(POP3)\Queue length, LDAP times, MSExchangeIS Public\Replication Receive Queue Size, SMTP Server\Remote Queue Length, SMTP Server\Remote Retry Queue Length, SMTP Server\Local Queue Length, Virus scan queue length 3. Network thresholds: Network Interface\Packet Outbound errors, Network Interface\Output Queue Length, Network Interface\Bytes Total/sec 4. LDAP latency checks: MSExchangeDSAccess Domain Controllers\LDAP Search Time and MSExchangeDSAccess Domain Controllers\LDAP Read Time thresholds were added to detect problems due to bottlenecks on the AD server. 5. RPC requests: Max RPC requests, average RPC request thresholds are now dependent on the number of users per server 6. Memory changes: Validate that the Database Cache Size Peak < 1.2 GB. In addition, most of the memory rules have been changed to work off the maximum rather than the average values. 7. Improved reporting: Reporting of results between steps and the summary are now displayed in a consistent fashion, using tabbed pages for the different reports. Pick up the latest version from here. Performance counters analyzed by this version of ExPTA: \Database(Information Store)\Database Cache Size \Database(Information Store)\Database Page Fault Stalls/sec \Database(Information Store)\Log Record Stalls/sec \Database(Information Store)\Log Threads Waiting \LogicalDisk(*)\Avg. Disk Queue Length \LogicalDisk(*)\Avg. Disk sec/Read \LogicalDisk(*)\Avg. Disk sec/Write \LogicalDisk(*)\Disk Reads/sec \LogicalDisk(*)\Disk Writes/sec \Memory()\Available Mbytes \Memory()\Free System Page Table Entries \Memory()\Pages/sec \Memory()\Pool Nonpaged Bytes \Memory()\Pool Paged Bytes \MSExchangeIS Mailbox(_Total)\Active Client Logons \MSExchangeIS Public(_Total
account only takes a few minutes. Join Now Read More Reply Subscribe RELATED TOPICS: Online - Cannot get performance counter data Exchange Server2007 - Error Accessing performance counter data on Server Event ID 106, source MSExchange Common, Performance counter updating error   This discussion has been inactive for over a year. You may get a better answer to your question by starting a new discussion. Text Quote Post |Replace Attachment Add link Text to display: Where should this link go? Add Cancel × https://blogs.technet.microsoft.com/exchange/2006/04/06/exchange-performance-troubleshooting-analyzer-expta-1-1-has-shipped/ Insert code Language Apache AppleScript Awk BASH Batchfile C C++ C# CSS ERB HTML Java JavaScript Lua ObjectiveC PHP Perl Text Powershell Python R Ruby Sass Scala SQL VB.net Vimscript XML YAML Insert Cancel Follow this vendor page Reply × Users who spiced this post Read these next... How the cloud works: The advantages of Infrastructure-as-a-Service Here's what you need to know about https://community.spiceworks.com/topic/296881-windows-cpu-beta-performance-counter-error-0x102 IaaS (which totally isn't a buzzword). How to setup networking for a home lab HOW-TO: Virtualization Here's a way to separate your VM lab network from your regular network. When end users know IT Best Practices & General IT How do you deal with end users that think they know how to do your job? © Copyright 2006-2016 Spiceworks Inc. About Advertising Privacy Terms Help Sitemap × Join millions of IT pros like you Log in to Spiceworks Reset community password Agree to Terms of Service Connect with Or Sign up with your email address First Name Last Name Email Join Now or Log In Email Password Log In Forgot your password? Email Reset Password Cancel Need to recover your Spiceworks IT Desktop password? By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks. By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks. Not a member? Join the community Back I agree Powerful tools you need, all for free. Help Desk » Inventory » Monitor » Community »
itfrom a WinXP SP2 workstation and a Windows Server 2003 machine. Either waythe result is that it can't read the peformance counter data http://microsoft.public.exchange.tools.narkive.com/yezjFfqV/extra-error-performance-counters-not-present (see exacterror pasted below). The Exchange server is Exchange 2003 SP2 (Version 6.5Build 7638.2), but running on a Windows 2000 SP4 machine. Network is ActiveDirectory - Global https://helpdesk.kaseya.com/entries/33899158-Windows-performance-monitoring Catelogs all work etc.Just using perfmon on the Exchange machine locally seems to show all theperformance counters.ExTRA error details:Error accessing RPC performance data Time Range:: 02/02/200709:18:14 - 02/02/2007 error accessing 09:23:09Error accessing RPC performance data. The 'MSExchangeIS' RPCperformance counters are not present in the fileC:\ExPTA.bermuda.20070202091842.PerfMon.blg. The following counters aremissing: \\bermuda\MSExchangeIS\RPCOperations/sec,\\bermuda\MSExchangeIS\RPC AveragedLatency,\\bermuda\MSExchangeIS\RPC AveragedLatency,\\bermuda\MSExchangeIS\Active User Count,\\bermuda\MSExchangeIS\RPCRequests,\\bermuda\MSExchangeIS\RPC Requests,\\bermuda\MSExchangeISMailbox(_Total)\Active Client Logons,\\bermuda\MSExchangeISPublic(_Total)\Active Client Logons Nicole Allen [MSFT] 2007-02-02 17:44:28 UTC PermalinkRaw Message Hi Ted,Have you looked at the blg data file (using perfmon) and verified that theperf counters were collected?Could you error accessing processor send the ExTRA result xml file to me? This file is located in the%appdata%\microsoft\extra directory (%appdata% is generally something like\documents and settings\
Windows performance registry (Winperf) Windows Management Instrumentation (WMI) Windows performance registry The Windows performance register is a virtual registry hive that contains performance metrics from a number of installed providers. All the communication with the performance registry is done via the remote registry service. The following monitors may use the Windows performance registry ●Windows performance monitor ●CPU monitor ●Memory monitor ●Swap size monitor ●Bandwidth monitor ●Disk monitor All monitors except the Windows performance monitor can be forced to use WMI instead if the flag “Use WMI” is enabled in the Object property page. How to verify that KNM have access to remote registry service 1.Logon to the KNM host machine using the Windows account used to monitoring 2.Start the 32 bit version of the perfmon.exe application (located in SysWOW64\perfmon.exe on a 64 bit host machine) 3.Connect to the monitored machine and add a counter. If this test fails, KNM will not succeed in enumerating and sampling counters on the monitored machine. 1.Check that firewall is opened for Remote Administration in the correct profile. 2.Make sure the Remote registry service is running on the monitored machine 3.Verify that the account is allowed to access the performance counter hive.http://support.microsoft.com/kb/300702/en-us 4.If its a standalone Vista/7 machine (not in a domain) you have to disable UAC to prevent it from filtering out the credentials.http://support.microsoft.com/kb/951016 5.If counters are missing, and you have verify that the same counters are missing in the performon.exe tool, the performance counter library might need to be rebuilt.http://support.microsoft.com/kb/300956 6.If counters still are missing the counters may be published by a 64 bit dll, KNM is a 32 bit application and cannot yet read 64 bit counter values. User have either to install a 32 bit version of the dll or use WMI to query the counter. Memory leaks in remote registry service on monitored machine Since the performance registry hive is loading external executable code to publish performance data to consume