/build/static/layout/Breadcrumb_cap_w.png

Troubleshooting Windows Monitoring Log Enablement Package (LEP)

        Even though the Performance Monitor Tool is an exceptional debugging and troubleshooting tool it also has its share of bugs and Caveats. Here are a few fixes and workarounds to common Performance Monitor issues.

 

Issue 1:

Symptoms:

                    The following error is displayed when importing an LEP with Performance Monitor: When attempting to create the Data Collector Set the following system error occurred: The security ID structure is invalid.


Cause: 

            This issue is caused when the Security tag value does not have the security token needed to import the Data Collector Set. 


Solution:

            The solution to this issue is to edit the LEP with a text editor and remove the value between the <Security> tags.



Issue 2:

Symptoms:

                    The following error is displayed when attempting to start an LEP in performance monitor: When attempting to start the Data Collector Set the following system error occurred: No data to return.


Cause: 

            This issue is caused when a performance counter listed in the LEP does not exist in Performance monitor. This usually occurs when not all product features or components are added during installation.


Solution:

            Identify which counter exist in the LEP and which does not exist in Performance Monitor and remove it. Or add the missing performance counter to Performance Monitor and restart the LEP.






Comments

This post is locked

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ