eScan Corporate for Microsoft SBS Standard: Features, Licensing & Benefits

Troubleshooting eScan Corporate on Microsoft SBS Standard: Common Issues Fixed

Overview

This guide covers common problems with eScan Corporate running on Microsoft Small Business Server (SBS) Standard and step‑by‑step fixes to restore protection and performance.

1. Installation or update fails

• Cause: Corrupt installer, insufficient permissions, or conflicting antivirus components.
• Fix:
  1. Run as administrator: Right‑click the installer and choose “Run as administrator.”
  2. Disable conflicting AV: Temporarily uninstall or disable other security software (Windows Defender can be left but real‑time components may need adjustment).
  3. Check disk space and .NET: Ensure at least 1–2 GB free and that required .NET Framework versions are installed (SBS Standard commonly needs .NET 4.6+).
  4. Use fresh installer: Download the latest eScan Corporate package from the vendor portal and verify checksum if available.
  5. Install in Clean Boot: Boot with minimal services (msconfig → selective startup) to avoid service conflicts.

2. Services not starting (eScan services stop or fail)

• Cause: Service dependency issues, corrupt service files, or permission problems.
• Fix:
  1. Open Services.msc and locate eScan services (e.g., eScan Anti‑Virus Service).
  2. Attempt manual start; note error codes.
  3. If dependency errors appear, ensure Windows services like Remote Procedure Call (RPC) and Windows Installer are running.
  4. Reapply correct permissions to program files and registry keys (grant Administrators full control).
  5. Repair installation from Control Panel → Programs and Features or re‑run installer with repair option.
  6. Check Event Viewer (Application/System) for specific error messages and search vendor KB with that code.

3. Client Management Console cannot connect to server

• Cause: Network issues, firewall blocking, wrong port/configuration, or certificate problems.
• Fix:
  1. Verify network connectivity: Ping the eScan server from the console machine.
  2. Confirm ports: Ensure the eScan management ports (default per product docs) are open in Windows Firewall and any network firewall.
  3. Check service status: Ensure eScan Management Server and related services are running.
  4. Validate credentials: Re‑enter admin credentials and ensure the account isn’t locked or expired.
  5. Certificates: If using HTTPS, ensure the server certificate is valid and trusted on client machines.
  6. Use IP instead of hostname: Test connection by IP to rule out DNS issues.

4. Real‑time protection not scanning files or high CPU usage

• Cause: Exclusions misconfigured, database corruption, or scanning engine stuck in loop.
• Fix:
  1. Update signatures: Force an update of virus definitions; verify successful download.
  2. Rebuild databases: Use eScan’s database repair/rebuild tools or reinstall signature files.
  3. Check exclusions: Remove unnecessary exclusions that bypass scanning and ensure critical paths are included.
  4. Scan logs: Review logs to identify files causing repeated scans; quarantine or investigate those files.
  5. Adjust heuristics/scan depth: Temporarily reduce aggressive heuristics if CPU spikes during specific operations.
  6. Restart services or server: A clean restart can clear hung scanning processes.

5. Scheduled scans not running

• Cause: Task scheduler issues, service conflicts, or misconfigured schedule.
• Fix:
  1. Verify the scheduled task exists in the eScan console and Task Scheduler.
  2. Ensure the account set to run the task has the “Log on as a batch job” right.
  3. Check task triggers and conditions (power, network) that might prevent run.
  4. Review eScan logs for schedule errors and correct time zone/clock settings on server.
  5. Recreate the schedule if corrupted.

6. Email scanning/SMTP issues (mail flow interrupted)

• Cause: Incorrect mail relay settings, incompatible SMTP filters, or certificate issues.
• Fix:
  1. Confirm SMTP host/port and authentication details in eScan mail protection settings.
  2. Temporarily disable mail scanning to confirm eScan is the cause.
  3. Check mail server logs for connection attempts and errors from eScan server.
  4. Ensure TLS/SSL settings match mail server requirements and update certificates if expired.
  5. Whitelist internal mail servers if causing loops.

7. Licensing and activation problems

• Cause: Expired keys, connectivity to license server blocked, or corrupted license files.
• Fix:
  1. Verify license validity in the eScan console.
  2. Ensure the server can reach vendor activation endpoints (check proxy settings).
  3. Re‑apply license key or use offline activation per vendor instructions.
  4. Contact vendor support with license ID if re‑activation fails.

8. Windows SBS-specific integration issues (Active Directory, Group Policy)

• Cause: GPO conflicts, AD permissions, or incorrect deployment method.
• Fix:
  1. Deploy eScan using AD‑friendly methods (MSI/GPO or the vendor’s AD integration tool).
  2. Ensure the installer and service accounts have appropriate domain permissions.
  3. Check GPOs that may block installation or service startup and adjust accordingly.
  4. Use Group Policy to push firewall rules and port openings for eScan components.

9. Logging and reporting not populating

• Cause: Log service disabled, disk space, or permission problems.
• Fix:
  1. Check log storage path and free disk space.
  2. Ensure eScan log services and reporting modules are running.
  3. Confirm write permissions for the log folder.
  4. Reconfigure or rebuild the reporting database if corrupt.

10. When to contact eScan support

• Signs to escalate:
  • Persistent service crashes with no clear log errors.
  • Licensing server errors after attempting vendor fixes.
  • Complex AD or Exchange integrations failing after standard troubleshooting.
• Prepare before contacting:
  1. Collect Event Viewer entries, eScan logs, system info (OS build, .NET version), and exact error messages.
  2. Note steps already taken and timestamps of failures.

Quick checklist (run before detailed troubleshooting)

• Reboot server and affected clients.
• Update eScan signatures and product to latest build.
• Ensure Windows updates and .NET are current for SBS Standard.
• Verify disk space and basic network connectivity.
• Backup eScan configuration and relevant logs.

If you want, I can create a printable checklist or step‑by‑step script for specific errors you’re seeing (provide the error code/text).