Troubleshooting Common G-Lock Email Processor Errors and Fixes
G-Lock Email Processor (GLEP) automates processing of incoming messages, but occasional errors can interrupt workflows. Below are common problems, their root causes, and step-by-step fixes to get GLEP running smoothly again.
1. GLEP won’t start or crashes on launch
Possible causes:
- Corrupted installation files
- Conflicting software (antivirus, other mail clients)
- Missing or outdated .NET Framework
Fixes:
- Repair or reinstall: Uninstall GLEP, download the latest installer from the official source, and reinstall.
- Run as Administrator: Right-click the GLEP shortcut → Run as administrator.
- Check .NET: Install or update Microsoft .NET Framework required by your GLEP version.
- Temporarily disable antivirus: Turn off real-time scan and retry. If it helps, add GLEP to antivirus exclusions.
2. Cannot connect to the mail server (POP3/IMAP)
Possible causes:
- Wrong server settings (host, port, SSL)
- Credentials changed or expired
- ISP or firewall blocking ports
- Two-factor authentication (2FA) enabled without app password
Fixes:
- Verify settings: Confirm incoming server, port, and SSL/TLS settings with your email provider.
- Test credentials: Log into the account via webmail to ensure username/password are valid.
- Use app password: If provider requires 2FA (Gmail, Yahoo, etc.), create an app-specific password and use it.
- Check firewall/router: Ensure ports (e.g., 995 for POP3S, 993 for IMAPS, ⁄143 for non-SSL) aren’t blocked. Temporarily disable firewall to test.
- Enable less secure apps (if applicable): For older accounts that require it, enable access per provider instructions.
3. Messages not processed or missing after rules run
Possible causes:
- Incorrect or overlapping filters/rules
- Actions moving or deleting messages prematurely
- Parsing conditions not matching message format
Fixes:
- Review rule order: Ensure rules run in the intended sequence; move critical rules higher.
- Inspect actions: Temporarily disable destructive actions (move/delete) and run in test mode to identify the rule causing removal.
- Test with sample messages: Save raw message files and run them through rules to diagnose parsing mismatches.
- Refine match conditions: Use broader patterns or regular expressions if emails vary in format.
4. Parsing failures (fields empty or wrong data)
Possible causes:
- HTML email structures or multipart messages not handled by current parsing rules
- Unexpected line breaks, encodings, or nested MIME parts
- Incorrect regular expressions
Fixes:
- Switch parsing method: Try switching between HTML, plain-text, or MIME parts in rule settings to find the correct source.
- Normalize encoding: Ensure GLEP is set to detect common encodings (UTF-8, ISO-8859-1) or convert as needed.
- Update regex: Test and refine regular expressions with sample message content; use online regex testers.
- Use XPath/DOM: If available, parse HTML using DOM/XPath targeting elements rather than raw text.
5. Slow performance or high CPU usage
Possible causes:
- Large inbox with many messages
- Complex rules with heavy parsing or external lookups (databases, HTTP)
- Insufficient system resources
Fixes:
- Archive old messages: Move processed or old emails to archive folders to reduce inbox size.
- Simplify rules: Break complex workflows into smaller steps or use fewer heavy operations.
- Increase system resources: Close unnecessary apps, add RAM, or run GLEP on a dedicated machine.
- Limit concurrent threads: Reduce parallel processing threads in settings to lower CPU spikes.
6. Export or action failures (database, file, email send)
Possible causes:
- File permission issues
- Database connection or query errors
- SMTP misconfiguration for outgoing messages
Fixes:
- Check file paths and permissions: Ensure GLEP has write access to target folders and files.
- Validate DB credentials and queries: Test database connections independently; fix SQL errors and timeout settings.
- Confirm SMTP settings: Verify SMTP host, port, SSL/TLS, credentials, and test sending from another client.
7. Licensing or activation problems
Possible causes:
- Expired or invalid license key
- Network issues preventing activation
- License stored locally corrupted
Fixes:
- Check license status: Open Help → Registration and confirm license validity.
- Re-enter key: Copy-paste the license key again; avoid hidden characters or trailing spaces.
- Offline activation: If online activation fails, use manual/offline activation procedure provided by the vendor.
- Contact support: If the license still fails, contact vendor support with purchase details.
8. Logs show vague or unhelpful errors
Possible causes:
- Logging level too low
- Errors originate from external systems
Fixes:
- Increase log verbosity: Enable debug or detailed logging in GLEP and reproduce the issue.
- Collect and inspect logs: Save logs, note timestamps, and correlate with actions attempted.
- Check external systems: Review mail server logs, database logs, or antivirus logs for related entries.
- Share logs with vendor support: When contacting support, include logs and exact steps to reproduce.
Quick troubleshooting checklist
- Restart GLEP and the host machine.
- Verify account login via webmail.
- Confirm server host/port/SSL and app-passwords.
- Run rules in test mode with sample messages.
- Increase logging and collect logs for support.
When to contact G-Lock support
Contact support if:
- Reinstall and configuration fixes fail.
- License activation errors persist after offline activation attempts.
- You can reproduce a bug with debug logs attached.
Include: GLEP version, Windows version, exact error messages, screenshots, and log files.
If you want, I can produce a checklist tailored to your GLEP version and the specific error messages you’re seeing.