Skip to content
logo Knowledgebase

Process Monitor Filters for Troubleshooting and Performance Analysis

Created on  | Last modified on 

Summary

Use Process Monitor from Microsoft to capture and analyze system activity. This article explains how to add filters and troubleshoot Sage 100 installation, migration, conversion, and printing performance issues.

Description

Resolution

CAUTION: Use caution when working with the below product functionality. Always create a backup of your data before proceeding with advanced solutions. If necessary, seek the assistance of a qualified Sage business partner, network administrator, or Sage customer support analyst.


CAUTION: Sage support can't assist with third-party products, hardware, report customizations, or state and federal tax questions. Refer to our Scope of Support for more info. Contact your Sage business partner, network administrator, or accountant for assistance.
Add Process Monitor filters

  1. Download Process Monitor from Microsoft.
  2. Extract the Process Monitor files.
  3. Launch Procmon.exe.
  4. Select Filter, Organize Filters....
  5. Select Import.
  6. Browse to the required *.PMF file.
  7. Select Open.
Note: Repeat steps four through seven to load multiple filters and switch between them.

Troubleshoot printing performance issues

Note: Use these steps after you rule out network and antivirus causes.
  1. Save the Crystal_Performance.PMF file to the workstation.
  2. Open Process Monitor.
  3. Import the filter using the steps in Add Process Monitor filters.
  4. Select Filter, Load Filters, Crystal_Performance.
  5. Select File, and verify Capture Event is enabled.
  6. Enable Capture Events if it isn't selected.
  7. Preview the report.
  8. Look for DLL files in another application's program folder, such as:
    • C:\Program Files (x86)\ProgramName...\filename.dll
    • C:\Program Files (x86)\Common Files\ProgramName...\filename.dll
Note: The filter highlights DLL paths that contain "CR". Known DLLs that cause printing performance issues include:
  • CRU*
  • SVCRFUNC*
  1. Rename one DLL file at a time.
  2. Test printing performance after each rename.

Troubleshoot Sage 100 installation, migration, and data conversion errors

  1. Save the appropriate PMF file from the attachments section:
    • Sage100_Install.PMF for installation errors.
    • Sage100_Migration.PMF for migration errors.
  2. Open Process Monitor.
  3. Import the filter using the steps in Add Process Monitor filters.
  4. Select Filter, Load Filters, Sage100_Install or Sage100Migration.
  5. Select File, and verify Capture Events are enabled.
  6. Enable Capture Events if it isn't selected.
  7. Reproduce the error by installing the update or performing the migration.
  8. Stop the capture when the error occurs.
  9. Review the events that occurred immediately before the error.
  10. Search for these terms:
    • Error
    • SY_Error
    • SWPROM
    • SYERRM
    • ExclamXP.bmp
    • Network Error
    • Access Denied
    • Bad Network Path
Note: Files that trigger the error often appear in the events immediately before the failure.

 

DocLink: Printing screen hangs when printing, another version of Crystal Reports Designer or a Crystal Reports runtime engine is also installed on the same machine
DocLink: Error: "Errors were written to the SQL Translation Log"
DocLink: Product Performance Troubleshooting Template
Attachment: 253_20230425123245_Sage100_Install.PMF
Attachment: 253_20230425123245_Sage100_Migration.PMF
Attachment: 253_20230425123245_Sage100_Startup.PMF
Attachment: 253_20230425123245_Crystal_Performance.PMF
Attachment: 253_20230425123246_Sage100_Data.PMF
Attachment: 253_20230425123246_CrystalVersion_Conflict.PMF
Attachment: 253_20230425123246_Sage100_AccessDenied.PMF

Need more help?

Chat now