Issue: Slow Performance & Crashes Associated with Antivirus & Firewall

Issue: Slow Performance & Crashes Associated with Antivirus & Firewall

Microvellum and AutoCAD

To minimize performance issues and crashes associated with antivirus software, we advise the following steps.

  1. Exclude these Microvellum folders: 
    C:\Program Files\Microvellum
    C:\Users\<username>\AppData\Roaming\Microvellum
    C:\Users\<username>\AppData\Local\Microvellum
    C:\file\path\to\microvellum\data
    (e.g., C:\Microvellum\Common Microvellum Data\Imperial\049_0) 
  2. If running a standard version AutoCad, exclude these files in addition to the previous files excluded. 
    C:\Program Files\Autodesk
    C:\Users\<username>\AppData\Roaming\Autodesk
    C:\Users\<username>\AppData\Local\Autodesk 
  3. Exclude these application files (location will vary depending on where it's installed): 
    Toolbox OEM: Toolbox.exe

    (e.g., C:\Program Files\Microvellum\Toolbox OEM 2017\Toolbox.exe)

    ERP: Micromanager.exe

    (e.g., C:\Program Files\Microvellum\Micromanager\Micromanager.exe)

    Toolbox with Standard AutoCad: acad.exe

    (e.g., C:\Program Files\Autodesk\AutoCAD 2016\acad.exe)

  4. Here are file type exclusions that will help as well: 

    *.Fas, *.lsp, *.3ds, *.wmf, *.sdf, *.ac$, *.apj, *.bak, *.ctb, *.cui, *.cuix, *.dcl, *.dst, *.dwf, *.dwg, *.dwl, *.dwl2, *.dwt, *.fbx, *.ipt, *.lin, *.ma, *.mat, *.max, *.mb, *.mns, *.mnu, *.pat, *.pgp, *.rfa, *.rft, *.rte, *.rvt, *.shp, *.shx, *.stb, *.sv$ 

If you have centralized antivirus management, you should be able to push these to other machines. If not, most antivirus programs will allow you to export and import exception lists.

SQL Server

To minimize the performance issues and crashes often associated with antivirus it would be advisable to do the following for your SQL server:

These Microvellum recommendations mirror those from Microsoft.
  1. Configure the Windows Firewall to Allow SQL Server Access
  2. Configure a Windows Firewall for Database Engine Access
  3. How to choose antivirus software to run on computers that are running SQL Server

Windows Firewall

What traffic should you allow through the firewall?

The default ports and protocols used by SQL Server services are:

Port

Protocol

Description

80

TCP

Default TCP Port used by Reporting Services

1433

TCP

Default TCP Port used by Database Engine

1434

UDP

Default UDP Port used by SQL Server Browser Service

1434

TCP

Default TCP Port used by Dedicated Admin Connection (DAC)

2382

TCP

When running Analysis Services named instance or running AS in SharePoint mode.

2383

TCP

Analysis Services default TCP port for clustered or standalone instances.


If you're running multiple instances of SQL Server and using different TCP ports for each, you also need to add them to the list above. When using the Windows Firewall, it's also highly recommended not to use Dynamic Port allocations but to define a static port for each instance.

Antivirus Exclusions

Target System

Exclude

Description

Windows Failover Cluster

Witness Drive

The witness disk is used for achieving quorum in your cluster.

Windows Failover Cluster

C:\Windows\Cluster

The directory for your clustering binaries.

SQL Server Data files

MDF, NDF, LDF

The common file extensions used by SQL Server.

SQL Server Backup files

BAK, TRN

The common file extensions used by SQL server

SQL Server Trace files

TRC

The common file extensions used by SQL server

SQL Server Backup files

BAK, TRN

The common file extensions used by SQL server

SQL Server Log files

MSSQL\LOG directory

The directory for SQL Server log files.

SQL Server Executable

SQLServr.exe

SQL Server executable.

SQL Server Agent Executable

SQLAgent.exe

SQL Server executable.

SQL Server Reporting Services Executable

ReportingServicesService.exe

SQL Server executable.

SQL Server Analysis Service Executable

MSMDSrv.exe

SQL Server executable.


    • Related Articles

    • Issue: Errors & Slow Performance of Microvellum OEM or AutoCAD

      When using AutoCAD, you may notice errors, slow performance, or sometimes, the application may crash. The Windows "Page File" size may cause this. This article presents the optimal setting for this file when using Microvellum OEM, or Microvellum with ...

    • Improving Product Library Performance

      The purpose of this article and video is to provide guidance on how to enhance the speed and performance of your Library. When it comes to Library Performance, it refers to the speed at which products are rendered in 2D and 3D, as well as the speed ...

    • Issue: Could not Load File or Assembly SQLServerCE

      Issue: The installation of Toolbox version 7 failed, and generates the error,  "Could not load file or assembly 'System.Data.SqlServerCe, Version=4.0.0.0" Possible Solution: It is possible that the installation may be failing while trying to install ...

    • Issue: Error Message "Toolbox VBA is not Currently Installed"

      Issue: While using Toolbox v7, you'll come across the following error: "Toolbox VBA is not currently installed.  Please run the Toolbox R7 installer to install the Toolbox VBA component."  Solution: Toolbox v7 no longer uses any VBA components, but a ...

    • Issue: Error Message "Could not Load File or Assembly System.data.SqlServerCe"

      Issue: An error occurs after installing a Microvellum update: "Could not load file or assembly 'System.data.SqlServerCe, Version 4.0.0.0....or one of its dependencies. The system cannot find the file specified." Solution: This error occurs when ...

    • Recent Articles

    • Toolbox Release Notes | Build 24.1.1105.641

      The following release notes apply to Toolbox build 24.1.1105.641 Nesting Fix Fig. 1: The fatal error that would occur during processing. There was reportedly an issue that occurred when clients attempted to process a work order using the nesting ...

    • Microvellum Foundation Library Release Notes | Build 24.1025

      The following release notes apply to Microvellum Foundation Library build 24.1025. Additions Added new global variable “Remove Stop Dado On Bottom Edge” for wood drawer boxes. Check this option to run the dado through at the bottom of the sub front ...

    • Toolbox Release Notes | Build 24.1.1030.641

      The following release notes apply to Toolbox build 24.1.1030.641 Routing and Profile Fixes Several issues were found with routing and polyline paths: Fig. 1: Horizontal routes off of a part disappearing (left) and appearing correctly (right). When ...

    • Toolbox Release Notes | Build 24.1.1010.641

      The following release notes apply to Toolbox build 24.1.1010.641 Biesse Winstore Fix Several issues with the Biesse Winstore plugin have been resolved: There was an issue that would sometimes occur wherein materials that were intended to stack wound ...

    • Toolbox Release Notes | Build 24.1.1001.641

      The following release notes apply to Toolbox build 24.1.1001.641 HBore Toolfile Fix Fig. 1: The location in the Toolfile UI where the error would occur. There was an issue reported with the functionality of the Horizontal Boring Machine setting in ...