Main Support:       Knowledge Center
Documentation:   ADS Documentation   >  ADS 2023 Update 1.0   >  ADS 2023 Update 1.0 Release Notes

This document contains references to Agilent Technologies. Agilent's former Test and Measurement business has become Keysight Technologies. For more information, go to

Skip to end of metadata
Go to start of metadata

Advanced Design System 2023 Update 1.0 Release Notes

For general information about Advanced Design System (ADS), visit ADS webpage at

Starting ADS 2022 release, support for the following operating systems has been discontinued:

  • Windows 7 Enterprise
  • RedHat Linux RHEL 6.x
  • SuSe Linux SLES 11

For more information, refer to Supported Platforms.


Feature Updates

Circuit Simulation


  • MVSG GaN model version 3.1.0 is available
  • SiMKit models are now aligned with version 5.6
  • The automatic computation of the stability probes (WSP) can now be turned off in the S-Parameter controller.
  • BSIMBULK model version 107.1.0 is available.
  • Added support for BSIM-CMG model version 111.2.1.
  • Major improvements in Envelope and Envelope Convolution when using S-Parameters.
  • Enhancement for statistical flow:

    • Statistical controller is for different statistical analyses: Monte Carlo, Yield, Yield Optimization.

    • Advanced sampling methods, Latin Hypercube Sampling(LHS), Hammersley Sequence Sampling(HSS), and Boundary Sampling, are available for statistical analyses.

    • The rerun mechanism is updated for users to rerun one or more special trials.

    • New measurement equations are added to measure the third moment and the fourth moment of a statistical distribution: skewness and kurtosis.

    • The non-effective statistical variables are now eliminated from the simulation.

Data Display

Data Viewing & Analysis and Manipulation

  • Improved the management and transparency of DDS AEL files being loaded:
    •   the new AEL File Manager enables the following (for more information, see DDS AEL Expression Files):
      • Allows specifying a list of AEL files to be loaded from SITE, INSTALL and workspace locations
      • Added option to reload AEL files without having to restart ADS
    • Added new pre-defined equations for displaying list of DDS AEL files loaded at various locations (for more information, see Equations).
    • The Archive/Unarchive Workspace commands have been enhanced to handle DDS AEL files, located either in the workspace or outside, with intuitive user interface to support all likely use cases.
  • Enhancements in Expression Manager:
    • New context menu to automatically augment the selection by adding all equations that use the selected equation
    • The Equation Hierarchy dialog, invoked from the Show Hierarchy context menu, has been re-structured into a tree format so as to also presents all the references to the selected equation.

EM Simulation


  • The oaTermType in the layout view is now preserved when creating the schematic view.

File & Workspace Management Tools

Workspace & Library Management

  • Archive/Unarchive Workspace enhanced to handle DDS AEL files and dataset files as below:

    • Added support for handling DDS AEL files either located within or outside of the workspace
    • Improved support for dataset files in $DATA_HOME
    • Added Select All button archiving external workspace files.
      See Archive for more details.

  • Improved alphanumeric sorting of cell names shown in Library View and other Dialog boxes
  • Technology Layer Improvements:
    • Filtering capability has been added to all layer selection combo boxes to allow narrowing down the layers of interest.
    • Improved usability for adding new layers and long layer names with tooltips and expanded widgets.

  • Used default browser for opening Help webpages on Windows.
  • Improved version control performance when retrieving the status for many files. Added option to check-in/out dialogs to allow automatically or manually selecting related items.

Design Editing and Physical Design

GDSII translators:

  • GDSII importer improves its handling of design elements that are on unmapped layers

General Editing Improvements

  • The shape and size configuration for solder mask and solder paste has been enhanced to support use cases of key customers
  • In 3D layout view, 3D bounding cuboid, instead of edges, of an instance can be drawn via a preference setting.
  • Filtering capability has been added to all layer selection combo boxes to allow narrowing down the layers of interest.
  • Plane tool has been enhanced to support global net-based clearance constraint hierarchically.
  • When routing traces, unconstrained vias are now selectable in the via selection box when constrained vias are also available. The selection combo box presents the sets in logical grouping
  • (Beta feature) the new Simple Evaluator, set as the default evaluator since ADS 2023, has further enhanced to handle bondwire variables and several other use cases the existing Full Evaluator could handle. This evaluator processes component parameter expressions significantly faster than the existing Full Evaluator.



  • Added a new memory interface, Pathfinding Interface, which unlocks multi-level modulations, PAM3, PAM4, PAM6, PAM8, and PAM16.
  • Memory Interface AMI Model Builder supports additional PAM3 modulation.
  • Support units in Memory Interface AMI Model Builder
  • Support BIRDs 209 Clock Forwarding (Rx_Use_Clock_Input)
  • Support BIRDs 207
  • Unlocked DDR Bus Sim for compliance apps (eye and jitter measurements)
  • Enhanced DDR5 compliance with more test IDs
  • New Compliance Probe component - Memory Probe for ADS measurements and Compliance Probe for Compliance Tests
  • Transparent data cycle and simulator selections for controller and memory components
  • Support s-parameter sweep for PCB, package, and DIMM, via (CA/Data Bus PreLayout Builder) components with Batch Sim
  • Support the custom bit sequence file (xml format), with load/save features
  • Improved CTLE usability to support variable, etc.
  • CA/DataBus PreLayout Builder usability enhancement - Graphical aid and other usability enhancements
  • Improved saving characterization data per pin
  • Supports reference Impedance entry for S-Parameter Toolkit
  • Supports tDIVW1, tDIVW2, vDIVW for LPDDR5

  • Tx_AMI, Rx_AMI components can start with an AMI Modeler
  • New CTLE preset for 802.3ck
  • Support CTLE preset sweep with Batch Sim
  • IBIS model input for C-PHY TX component
  • SerDes AMI Modeler support unit
  • Improved SSC behavior for USB NRZ AMI model
  • Supports reference Impedance entry for S-Parameter Toolkit

EM - SIPro/PIPro

  • In Via Designer, it is now possible to rename the ports in the design. The port name will be visible in the S-parameter and TDR plot. If a cell is exported, the symbol pins will have the corresponding port name.

Power Electronics

SMPS Performance Testbench

  • Added Efficiency test to the SMPS Performance Testbench.

Power Electronics Library

  • Added a 4 pin SiC Model with parasitics to the Power Electronics library.

Netlist Translator

  • Enhanced the netlist import tool to support additional syntaxes for .PARAM statement.


  • Added an example to demonstrate the SMPS Performance Testbench feature.
  • Added an example to show layout modification effects on a boost converter.


Design Rule Check

  • The DRC Create Rules dialog supports a technology layer with the name 'default'.

For more information, see Design Rule Checker (DRC).

Electrical Rule Check

  • Electrical Rule Check (ERC) Current Density shows the current density at each component pin with highlighting in schematic and layout. To get started using ERC, from the ADS Main window select Open an Example > Training Examples > Layout Verification > Layout Verification Tools Tutorial.

For more information, see Electrical Rule Check (ERC).

Layout Versus Schematic

  • The LVS dialog Auto View supports the checked state (Zoom or Center) and the unchecked state (no update to the window view).
  • The LVS dialog can be configured as a generic LVS viewer. Use the command interface to define mapped/unmapped components, mapped/unmapped nets and parameter mismatches. The viewer supports highlighting in schematic and layout.
  • The LVS dialog report provides additional information on mapped and unmapped pins for each net. Under the Net Mappings header, expand each net to see the component pins on the net.
  • Cells with an emview are now recognized as a device.
  • LVS now uses the connectivity setting 'Calculate all flight wires between grounds'. When the setting is checked, missing physical connections to gnd! in layout are reported as errors. When not checked, LVS reports a warning.

For more information, see Layout Versus Schematic (LVS).

PDK Validator

  • The PDK Validator configuration supports specifying default design cell names and a model include path in a different library than the component library.

For more information, see PDK Validator.

Top Fixed Issues

Data Display

Data Viewing & Analysis and Manipulation

  • Fix crash related to modifying specification or mask properties that should be disabled.

EM Simulation

EM Integration

  • A bug was fixed so that the Interpolation flag in the EM data view is now honored.


  • Metal bias values directly specified in LTD are applied pre-scaling rather than post-scaling. This restores the pre-2023 release behavior
  • EM > Tools > Cookie Cutter: non-polygon shapes that overlap with the cookie cut region, but are not completely inside, are excluded from the cookie cut.


  • A bug has been fixed that rendered the dotted bounding box of an encrypted EMPro 3D component in the wrong location after changing its orientation.
  • A bug got fixed that prohibited to view the mesh after rerunning an FEM simulation.
  • The netlister of the 'em_nport' and 'em_pnport' components from the 'empro_basic' library can now deal with a large number of ports.
  • A bug was fixed that could cause a crash when dragging and dropping a pin onto another pin in a port setup.
  • An issue has been fixed to deal with international characters in file paths when using xxPro and the legacy 3D EM Previewer.
  • An EMPro 3D component can now be excluded from a Full EM Extraction analysis by disabling its 'Include in Mesh' setting.
  • FEM Generation 2 now supports a port with multiple plus and/or multiple minus pins, as well as a pins with multiple shapes.


EM - SIPro/PIPro


  • When an ODB++ imported board design contains line segments that completely overlap when they go back and forth to a extreme connect point, disconnect errors can happen in the imported ADS layout. The ADS code that joins ODB line segments during import occasionally removes these overlapping line segments entirely up to the first "TEE" in the structure as this sort of overlap with co-linear points isn't allowed in ADS layout.This fix provides a workaround for this erroneous behavior when EM simulation is your primary goal for importing your ODB++ design by disabling the line join functionality and keeping the individual line (segment) features as they are defined in the ODB++ structure.
    The configuration flag <KeepLinesAsIndividualSegments>0</KeepLinesAsIndividualSegments> in the <workspace_dir>/setup_odb.opt xml option file controls this join behavior.Change the 0 to 1 to have the lines imported as individual segments.
  • Failure in SIPro subdomain fixed in case non-updateable ideal short components are used in the analysis setup.

Known Issues

Design and Technology Management

  • ADS dynamic link is compatible with Virtuoso releases up to IC6.1.8-64b.500.22 / ICADVM20.1-64.500.22;  it is not compatible, and hence not fully functional, with Virtuoso release number IC6.1.8-64b.500.24 / ICADVM20.1-64.500.24.
  • AEL constants are protected and should not be modified in any DDS expressions.  An AEL error will be issued in case an attempt to modify an AEL constant occurs.

Design Guide

  • Unable to unarchive HDMI design guide from the Schematic view (DesignGuide > HDMI).
    • Unarchvie using the old ADS version.
    • HDMI design guide will open in case it is already unarchived.
  • Simulating the "1_Sim_CA" design in the DDR4 CTB design guide prompts the netlist error.
    Workaround: Open the schematic design "PatternGen_CA_Continuous" and arrange the pin numbers in order.
  • Simulating of schematics in the HDMI_Link_Simulation design guide prompt the netlist error.
    Workaround: Open the schematic design “HDMI_Diff_RX” and arrange the pin numbers order in order.

Design Kits

  • A design created using ADS2020 Non-Linear Demo Kit (NLD) and using NLD discontinuities like demo_bendP, demo_stepP, demo_teeP, etc. will not work as expected in ADS 2021.
    Workaround – In ADS 2021, either update the design with the latest NLD i.e. NLD shipped along with ADS 2021; or continue to use the NLD that was shipped with ADS 2020.

Circuit Simulation


  • When using GoldenGate in ADS 2020 Update 2.0, some of the library files of RFIC cockpit options are not getting loaded due to license incompatibility. It is recommended to use ADS 2020 Update 1 when using GoldenGate in ADS.
    For details on license compatibility, see License Codeword Version Compatibility.

  • Simulation Manager may not work on Windows and throw exceptions for some designs.

  • ADS 2019 will not be compatible with Verilog-A files, which have been encrypted before ADS 2019. There is no change for non-encrypted Verilog-A files.

  • TMI models are supported for pure Hspice syntax only. The support of hybrid syntax (mixing Hspice and Spectre) is planned for a future release. 
  • BSIMSOI models using TMI modeling is not supported yet. Classical BSIMSOI models are supported as before.
  • TMI Aging simulations are not supported.
  • SystemVue - ADS Cosimulation in Netlist mode (InvokeADS set to YES) doesn't work with ADS 2023 or later versions.


  • In ADS, electro thermal simulation is assisted to automatically turn off the HBAHB and TAHB options for single tone HB. However, the electro thermal simulation for multi-tone HB needs a manual intervention to turn off the HBAHB and TAHB options for reporting voltage data.

  • You may not be able to start a Transient/Envelope Electro-Thermal (ETH) simulation only when the same testbench is open in the viewer of Transient/Envelope thermal results. You need to close the viewer before launching a Transient/Envelope ETH simulation.

  • Paths or other user specified settings made in the ETH controller may need to be updated when the workspace is moved across operating systems. To avoid potential problems, use the ETH controller's Advanced tab to clean the ETH run directory after such a move.
  • On a fresh Linux machine, electrothermal simulation fails with the following error message:

    Heatwave returned an unknown error code 127.

    Workaround: The error could be due to missing packages, for example, libpng12. Verify your system meets the requirements using the script. For more information,  see Checking Installed RPM Files and the Operating System Version.

  • If you get licensing errors while running thermal simulation, you may need the following workaround.
    Workaround: Rename the file  $HOME/.eesofrc. For example,  $HOME/.eesofrc-orig.

  • Electrothermal does not support remote simulation, batch simulation, Monte Carlo, tuning, Optimization, and Measurement Equations. Also, you cannot sweep directly on the DC controller.

  • All libraries referenced in a layout should use the same layout resolution, namely the OA database units (DBU) per user unit (UU).

  • You cannot run both a transient and envelope simulation on the same design from one testbench.

  • The calculation of power dissipation from passive components other than resistors may not be correct in harmonic balance simulations.

  • Electrothermal does not support the transient or envelope simulation that is controlled by a ParamSweep.  

  • If you get "Maximum timestep reduced to half of shortest transmission line delay " warning, it can lead to transient simulation to not converge   
    Workaround: Unselect "Limit timestep for Transmission Line" option on Time Setup tab of Tran component to get it work.

  • On Linux, if you specify the THERMAL_DIRECTORY variable in eesof_lib.cfg file using backward slash (..\thermal), the thermal simulation does not run properly.
    Workaround: Specify the THERMAL_DIRECTORY variable using forward slash (../thermal) instead of backward slash.

  • The ETH viewer does not support 4K displays. A few instances of text and icons may appear distorted. 

  • You receive an error message in substrate editor that you cannot use the same layer number more than once. You can safely ignore this error during thermal technology export.

  • On a fresh Windows 10 system, Electrothermal simulation terminates with an error. 
    Workaround: Install the following Microsoft Visual C++ runtime components: 

DDR Design 

  • You receive an error message to check port numbering when performing simulation with SnP component for differential configuration.
    Workaround: Select the first option in Pin Configuration for the SnP component.

HSD Design


  • You receive an error message when runtime libraries for some of the ADS example ibs files (for old AMI models) are unable to get installed automatically during the ADS install.  The error appears eventhough the ibs file is supported on specific platform. 
    Workaround: Microsoft Visual C++ 2010 runtime library is required to run the dll files. Download the following library if it is not installed:


SIPro/PIPro, Via Designer 
  • On Windows 10 with Intel HD graphics, Via Designer may show an error message ‘Failed to use the connection between ADS and Via Designer.’  This has been isolated to the latest release of Intel HD Graphics drivers (23.xx.xx.xxxx).
    Workaround: Downgrading the graphics driver to the previously recommended driver resolves this issue (e.g.,, A05).
  • DirectX 9 as a graphics driver is no longer supported. DirectX 11 is thus be used by default. Run "diagdx" to verify which DirectX version is supported on your system.
  • ADS 2020 is not compatible with the latest available Samsung component models released in June 2018. The support for the component models is planned to be added in an upcoming update release.
  • Simulation failure when using components with S-parameter models or for which the model is defined using a lib/cel/view in case the Updating model does not require new simulation is not set. As a workaround, turn on the option. For PI-AC simulations, the options are turned on by default, for SIPro, this needs to be turned on explicitly.
  • If you run SIPro/PIPro on a fresh machine with Suse 11 or Redhat 6 installed, you may encounter the critical error "EMPro exited unexpectedly during execution." This is related to the graphics driver software.
    Workaround: Upgrade to the latest vendor-specific drivers and OpenGL libraries for the graphics card.
    Alternative workaround: 
    Run the following commands:

    cd $HPEESOF_DIR/fem/2020.20/linux_x86_64/bin
    ./startempro --personality=sipi--driver=x11

    Ignore any license-related error messages that may show up on executing these commands. The driver setting is saved per personality for future sessions.

  • With split domains on, there are no results available until simulation results are available from the last simulation, or even after the simulation.

  • Cadence® Allegro®(SPB 17.2 and SPB 17.4) is not supported on RHEL 8. As a result, the BRD Import and ADFI Export does not work on RHEL 8.


  • The power graph is not correct when VRM's or Sinks are defined, starting from pin definitions. All the other result data is correct. This issue does not occur when VRMs and sinks are defined from component instances.

EM Simulation


  • In a vncserver session running on an RHEL8.4 platform, you may encounter the critical error "EMPro exited unexpectedly during execution." This is related to the graphics driver software contained in the mesa-*.x86_64.20.3.3-2.el8 packages.
    Workaround: downgrade the packages to the previous version using the following command:

     sudo yum downgrade mesa-*

    The packages mesa-*-20.1.4-1.el8.x86_64, and the dependent llvm package work.


  • The FEM and Momentum Generation 2 flows are state-of-the-art solvers but still evolving. In case it does not handle your design, switch back to Generation 1.

  • Multi-technology designs cannot be analyzed with Momentum.
    Workaround: Use the FEM simulator
  • Project load fails with the error 'OccDesign::getNet: key not found' when a layout shape has a multi-bit net name (e.g. 'd<7:0>' or 'a,c,net1').
    There is no workaround.
  • With McAfee Endpoint Security (ENS) enabled, the Momentum surface current visualization hangs.
    Workaround: Disable the "Enable Adaptive Threat Protection" flag in McAfee ENS.

RFPro and 3D Viewer

  • If the Geometry view is empty when opening the design, this may point to an issue with the graphics card driver.
    Recommended workaround: Upgrade to the latest vendor-specific drivers and OpenGL libraries for the graphics card.
    Alternative workaround 1: On Linux, launch the tool and force it to use the X11 driver. On Windows, set the driver to 'msw'. This preference is saved for the current user and per personality. You can do that by executing the following commands, e.g. in a shell on Linux:

    cd $HPEESOF_DIR/fem/2022.20/linux_x86_64/bin
    ./startempro --personality=rfpro --driver=x11
    ./startempro --personality=3dview --driver=x11

    Ignore any license-related error messages that may show up on executing these commands. The driver setting is saved per personality for future sessions.

    cd $HPEESOF_DIR/fem/2022.20/linux_x86_64/bin
    ./startempro --personality=rfpro --clear-preferences
    ./startempro --personality=3dview --clear-preferences

    For further troubleshooting with 3D libraries, refer to the following topics:

    Alternative workaround 2: Set the following environment variable EMPRO_SET_SOFTWARE_DRIVER_AS_DEFAULT=1. This variable controls the default driver when no preference was set. On Linux, X11 is used. On Windows, MSW is used.
    You can clear all preferences as follows:

EM Setup

  • On a Virtual Windows 10 system with Microsoft Hyper-V Video display driver, the 3D EM Preview with EM Setup Preprocessing may bring up a dialog with a Hoops error, and, after suppressing the dialog, it opens up blank.
    There is no workaround.
  • EM Setup faces issues submitting jobs to a cluster when the "sitecluster behavior" is not implemented in sitecluster implementation.

    Workaround: Add a behavior function to sitecluster that returns {} as output on stdout.

  • FEM based parallel jobs on sitecluster with behavior configuration (qbehave) may show incomplete simulation logs.
    Workaround: You can view the complete log available in the following location: <wrk_space>/simulation/<lib>/<cell>/layout/emSetup_FEM/proj.ep/Simulation/<simulation_num>/emds_dsn/design/emprfem*.log

Distributed simulations

  • The example implementation of the sitecluster command for LSF clusters may lead to failing simulations if the path or number of threads is too large.
    Workaround: See the workaround details in the sitecluster documentation.


    • Exporting with MentorDA link does not work with the latest Mentor Graphics software Version VX2.6. 

Power Electronics

  • SMPS Performance test bench shows an error with femgen2 solver.
    Workaround: Re-run the test bench.
  • PowerMOS_SiC power devices operate under a very wide range of voltage and current slew rates and it is a challenge to create a model that converges under all conditions – especially conditions that depend upon what components are connected externally to the power device in the circuit schematic. Please contact technical support if you encounter such an issue when attempting to use this model.
  • If you run PEPro on a new machine with Suse 11 or Redhat 6 installed, you may encounter the critical error "EMPro exited unexpectedly during execution." This is related to the graphics driver software.
    Workaround: Upgrade to the latest vendor specific drivers and opengl libraries for the graphics card.
    Run the following commands:

    cd $HPEESOF_DIR/fem/2020.20/linux_x86_64/bin
    ./startempro --personality=sipi--driver=x11

    You can ignore any license related error messages. The driver setting is saved per personality for future sessions.


  • While installing a new version of ADS, if you see “Previous version detected” error even after you have already run the uninstaller for that version of ADS, you may need to manually uninstall ADS before installation of the new ADS. To manually uninstall ADS, perform the following steps.
    1. Exit the current ADS installation session if it is running
    2. Remove or rename the file .com.zerog.registry.xml  under the folder  C:\Program Files\Zero G Registry . Both the folder and the file are by default hidden, so you may need to change the folder viewing setting to show hidden files and folders, do so via the Advanced settings of the View tab in the Windows Folder Options dialog box.
    3. Remove the ADS installation directory through the Windows Explorer.
  • After performing the above steps, you can re-start the ADS installer.


  • You may observe additional License Usage when Client Machine reconnects to network after intermittent disruption.
    Workaround: In case of network interruption on the client machine, to reclaim the inactive licenses, a TIMEOUT can be set using the TIMEOUTALL feature in options file (minimum time period of 15 minutes). The inactive license may stay checked out for this period of time

  • Unable to install Licensing Hardware Key Drivers on Windows.

  • Workarounds:

    • Turn off UEFI Secure Boot (BIOS) and use the default 6.3 version of the Wibu key driver delivered with the EEsof Licensing tools.

    • Turn on UEFI Secure Boot (BIOS), upgrade to ADS 2020 Update 2.0 and use the 6.51 WibuKey driver version available in the 2020.02 License tools installation directory.

    You will not be able to run older ADS releases with the 6.51 WibuKey dongle drivers

  • Setting FLEXLM_DIAGNOSTICS to the highest level (FLEXLM_DIAGNOSTICS=3) on Windows client may cause a crash during license checkout. Flexera is investigating this issue.
    Workaround: It is recommended not to use the FLEXLM_DIAGNOSTICS on Windows clients or use it at lower level (FLEXLM_DIAGNOSTICS=1 or FLEXLM_DIAGNOSTICS=2).
  • Licensing may not support a license file path that is too long. This will likely occur when you have too many license files.
    Workaround: Remove some license files, move the license files to a shorter directory path or to combine license files into a single file.

  • License Setup wizard may not be able to start license server with many license files. During setup, it may lead to a situation where a command prompt window appears/disappears incessantly. This is due to the fact that License Setup wizard is not able to start lmgrd with a long command line and may get stuck in a loop.

    1. It is recommended to combine all license code words tied to same MAC ID into single license file to avoid setting large number of license files.
    2. Try to use a shorter path to place license files.
    3. If #1 and/or #2 does not help, start the license server (lmgrd.exe) from the command line (e.g. lmgrd.exe -c <lic-file-path> -l <license_server_log.txt>) and then set <PRODUCT>_LICENSE_FILE=<PORT-NUMBER>@localhost for product you want to use on same PC.
  • Dongle drivers for Flex-10 dongles on Linux are release specific. Installing the latest dongle drivers on Linux will function properly only for the most recent EEsof releases.
    : Install and use dongle drivers as needed.  If you need to run the most recent EEsof releases, use the latest  Flex-10 dongle driver. If you need to use older releases, uninstall the latest dongle driver and re-install the older dongle driver

  • FLO and EEsof License setup are writing server logs at different locations. However, the EEsof server log file location is updated in the License Manager > Environment tab.
  • When multiple same-named INCREMENT lines of different version exist on the license server, few advanced FlexNet options to reserve/limit licenses may not work properly. 
  • Product Selector “Check Availability“ generates incorrect results (which leads to license failure) for older releases when multiple date base versions of like-named bundles exist in the license pool.
  • In Linux, Product Selector OK and Cancel Buttons locations are reserved.
  • Starting from FlexNet Publisher 2015 (also known as version 11.13.1), the adoption of the best practice of the least-privilege security therein results in the License Server related Windows Service to run with the LocalService Account privilege (instead of the LocalSystem privilege as before.)  Running with the LocalService Account privilege, an executable can no longer access any files located in the per-user specific type of folders.  As a result, any license file placed in those folders can no longer be accessed by the License Server when the License Server is automatically started via the Windows Service upon each PC reboot. For the local node-locked license, this would not result in any disruption to the usage of EEsof applications; however, for the license installed on a network PC that is accessed by multiple client PCs, this may cause EEsof applications not to start after the network PC reboots
    Workaround: Store your license files in the Windows folders that are accessible by the LocalService Account privilege.  For example, C:\ProgramData or C:\users\public are both qualified choices.  In general, any folder that has the "Users" group listed in its Properties > Security page and this "Users" group has the read permission enabled should work. 
  • Using the default port to connect to a license server may cause a delay when checking out licenses. If no port is given in the license file, Flexera scans ports 27000 to 27009 to find the port. Starting from FlexNet Publisher 2015 (aka version 11.13.1), the default timeout for the response from each port increased from .1 seconds to 3 seconds.

    To avoid the delay, KSM now issues licenses with port 27009 instead of leaving this blank. The EEsof License Setup Wizard (from Licensing 2017.01 onwards) handles some common situations such as: where it detects license file(s) without port, when users get a new license file with port 27009, or when all license files for a vendor daemon does not have same port.

    You will not be able to start the license server if all license files for a vendor daemon on a server does not have same port.
    Users who manually setup a license server or using EEsof License Setup Wizard with older licensing bits may need to manually edit license files to comply with the following rules:

    1. All license files for a vendor daemon on a server must use the same port (or all be blank). 

    2. Using the default port (blank) is allowed but may result in longer checkout times. 

    3. If setting up a network server, select an unused port that is not blocked by a firewall.

    Workaround: If the user cannot change the port, or wants to use the default Flexera ports, the environment variable FLEXLM_TIMEOUT can be set to .2 seconds (200000), to minimize the performance degradation. However, if the network latency is an issue in your environment, you may need to fine-tune this setting to minimize the general performance degradation while still accommodating the network latency.

  • Installation of EESof EDA tools (such as, SystemVue 2016.08, Genesys 2017.XX, or ADS 2017.XX) may hang at 4% (percentage vary based on the products) for few hours or even more on some specific machines.
    • Disable Firewall setting in Anti-Virus Software installed on the PC.
    • Download and unzip process explorer from the below link and then invoke procexp.exe.
      Right click on the wusa.exe process under <Product installer exe> and select KillProcess. Now it will continue the product installation.
  • After installing EESof EDA tools (such as, SystemVue 2016.08, Genesys 2017.XX, or ADS 2017.XX) successfully and try to invoke the software or License wizard, you may encounter “api-ms-win-crt-runtime-l1-1-0.dll” missing error.
    Workaround: Install the Update for Universal C Runtime in Windows .  On Windows 64-bit system systems, the file to install is x64 version of the Microsoft hotfix KB2999226. A copy of the Windows6.1-KB2999226-x64.msu Microsoft 64-bit hotfix installer can be found under the C:\Program Files\Keysight\EEsof_License_Tools\bin directory.  The Microsoft hotfix KB2999226 can be found under the Update for Universal C Runtime in Windows  page at as well.
  • On a newly formatted RHEL system, the EEsof Licensing tools may fail to boot. This is because the FlexNet Publisher 2015 requires a certain rpm
    Workaround: Under the EEsof product installation directory, there exists a utility script named "" under the bin directory. Run this script to find out whether any rpm is missing; run this script with a "-y" command-line option to also have all the missing rpms automatically installed if you have the sudo or root privilege.
  • License server may stop recognizing Flex-10 dongle on some systems within a few hours after starting
    Workaround: If v6.10 or v6.11 is found and experience this problem then upgrade the WibuKey drivers to v6.30/6.30b from Wibu Systems.
  • Unable to install Flex-10 driver if Flex-9 dongle is already plugged into a machine
    Workaround: Before installing a Flex-10 driver for the first time, unplug the Flex-9 dongle.
  • There is a known FlexNet Publisher issue, whereby mixing node-locked codewords and floating codewords in one license file can result in: a) Remote simulations not working or b) A second local simulation not working in case the license is node-locked and also has incorrect version.
    Workaround: It is strongly recommended that you do not mix node-locked codewords and floating codewords in one license file nor in any configuration that ends up with node-locked codewords and floating codewords both available on the same server. In other words, put the node-locked license and the floating license on different servers, and point to the respective one based on what you need to run.
  • If a user simultaneously runs two instances of a product and has mixed different versions of the same codeword on one license server, extra licenses may be pulled and result in unexpected “Licensed number of users already reached for this feature” errors.
    Workaround: We recommend you remove expired codewords, to separate out the new and the old versions of codewords into different files and different servers, and to point to the respective one based on what you need to run.
  • Not specifying the TCP/IP port for the license server during license setup may lead to unexpected behavior and/or license checkout failure on the Windows platform. We strongly recommend you to always explicitly specify the TCP/IP port associated with each license server.
  • A node-locked and floating bundle operating on Linux cannot be shared between products using EDA License Tools version older than 2014.01 when run at the same time.
  • License Setup Wizard does not remove any previous user-configured FLEX Windows License Service manually set up by a user using FlexNet's lmtools.
    Workaround: You must remove the previous user-configured Windows License Service via lmtools.
    • Run the lmtools.exe from C:\Program Files\Agilent\EEsof_License_Tools\bin to invoke the lmtools utility. The lmtools utility window is displayed.

      If you have installed an EEsof product released before 1st August, 2014 on your system prior to installing an EEsof product released after 1st August, 2014 then the default EEsof Licensing tools path will remain C:\Program Files\Agilent\EEsof_License_Tools. On the systems that only have EEsof products released after 1st August, 2014 installed then the default EEsof Licensing tools path will be C:\Program Files\Keysight\EEsof_License_Tools.
    • In the Service/License File tab, check the Configuration using Services option. All user-configured FLEX Windows License Services will be listed.
    • Select the service you wish to remove.
    • Select the Config Services tab and click the Remove Service button to remove the service.
      To ensure that the license service or lmgrd is running, click View Log. A log window appears that confirms whether agileesofd and lmgrd are up and running.
  • While running multiple versions of prior SHORT_PRODUCT_NAME releases together, set PRODUCT_NAME_MAXIMUM_BUNDLE_USAGE=ON in your environment so that all of them will use the same method to check out licenses. Otherwise, you might receive an error message, "Licensed number of users already reached".
  • For LSF style distributed simulations, ensure that the PATH on the client computer points to the $HPEESOF_DIR/EEsof_License_Tools/${architecture} directory that corresponds to the EEsof release being used. This needs to be done in order to ensure that the proper version of the Flexera utilities (like lmutil ) gets picked up in the path before any older in-compatible versions (that may also be installed on a users’ system.)
  • License Setup Wizard ( aglmwizard.exe ), which is used to set up and record the license path would not work if you already have an environment variable set for PRODUCT_NAME_LICENSE_FILE.
    Workaround: You can use PRODUCT_NAME_LICENSE_FILE variable to point to license file or refer to Licensing (For Administrators).
  • The License Setup Wizard will exit or not properly configure a license server, if the server has all of its licenses currently in use.
    Workaround: Wait for a license on the server to become available as you normally would before launching the product.
  • Unable to set license in case unicode characters are used either in path or license file name because the Flex License Service does not support these characters.
  • The Product Selector tool will be unable to display the license server status properly when connected to older license server.
    Workaround: Upgrade your license server to the latest version.

  • EEsof Licensing Tools installer can hang on systems with McAfee LiveSafe installed and running the default firewall settings.
    Workaround:  Prior to installing EEsof Licensing Tools, temporarily turn off the McAfee LiveSafe firewall.

  • Licensing setup steps on systems with McAfee LiveSafe installed can fail.
    Workaround:  Under the McAfee LiveSafe firewall settings, under Port and Settings, allow the use of port 27001 for lmgrd.exe under the EEsof Licensing Tools installation bin directory.  Under Internet Connections for Programs , enable lmgrd.exe, aglmmgr.exe and aglmwizard.exe for all devices and turn off monitoring.

  • On Windows, EEsof product releases prior to 2014 can have boot time issues with licensing if an newer EEsof product is installed prior to installing the older product. For example, if a users installs Advanced Design System 2017 and then installs Advanced Design systems 2014.01, the user can have boot time errors with ADS 2014.01.
    Workaround:  For Advanced Design System users,  set a system environmental variable named ADS_LICENSE_FILE under the Control Panel/ System, and Security / System / Advanced system settings and under the "environmental variables".  Add an System variable named ADS_LICENESE_FILE and the value will be the path to your local license file or the port@host setting for your site.

Third-Party Applications

  • Spyder application menu bar becomes inactive when the window is maximized using View > Full Screen or by pressing F11 (shortcut key to maximize the screen).
    Workaround: Press F11 again to make it the default screen. The menu bar is now active and works fine.


  • Cadence applications (Assura) is not supported in RHEL 8 Linux Distribution. 

Virtual Test Bench

  • From VTB 2022, SystemVue VTB's QT help file is integrated into SystemVue VTB installer. However, help does not open, when you press F1 for a VTB component.
    Workaround: Perform the following steps:
    1. Open a command window.

    2. Set the path to ADS help directory. Execute the following command:

      On Windows

      set path="<ADS_Install_DIR>\bin\Help";%PATH%

      On Linux

      export PATH=<ADS_Install_DIR>/bin/Help:$PATH

      On RHEL 7 (due to library related issue)

      export HPEESOF_DIR=<ADS_Install_DIR>
      export LD_LIBRARY_PATH=$HPEESOF_DIR/lib/linux_x86_64:$HPEESOF_DIR/lib/linux_x86:$LD_LIBRARY_PATH
      export PATH=$HPEESOF_DIR/bin:$PATH
      export PATH=$HPEESOF_DIR/bin/HELP:$PATH


      <ADS_Install_DIR> is the ADS installation directory.

      On Windows: The default ADS location is "C:\Program Files\Keysight\ADS<version>"

      On Linux: The default ADS location is "/usr/local/ADS<version>".

      For example, <version> is 2022

    3. Invoke VTB help. Execute the following command:

      On Windows

      assistant -collectionfile "<VTB_Install_DIR>\Help\vtb.qhc"

      On Linux

      export SYSTEMVUE_INSTALLATION_DIRS=xxx/SystemVueVTB/2022
      assistant -collectionfile $SYSTEMVUE_INSTALLATION_DIRS/Help/vtb.qhc


      <VTB_Install_DIR> is the SystemVueVTB installation directory on Windows.
      xxx is the directory where unzip or untar of VTB package is done on Linux
      On Windows: The default VTB location is "C:\Program Files\Keysight\SystemVueVTB2022"

      You can also refer to the online version of the SystemVueVTB documentation.

  • When using VTB on Virtual Machine (VM), if SystemVue crashes then ensure to restart your system.

  • To use VTB, ensure ADS is installed in a path that has only ASCII characters.

  • Backward compatibility
    In ADS, the customized VTB can have a backward compatibility issue.
    Workaround: To fix this issue, use one of the following methods:
    1. Open and Save the custom VTB in SystemVue2022Update0.1. Now, you can use the custom VTB in ADS.
    2. A built-in workspace conversion tool is provided in the installer. You can convert the custom workspace (.wsv) to the newer SystemVue version. Use the following steps to convert the workspaces:
      • Open Command Prompt in the Administrator mode.
      • Browse the location of the old workspace. For example, C:\ADS_VTB.
      • Run the following command parameter.

        C:\ADS_VTB><SystemVueVTB_Installation_Dir>\bin\WorkspaceConversionToolManaged.exe" VTB_Examples.wsv VTB_examples_new.wsv


        1. <SystemVueVTB_Installation_Dir> is the location where SystemVue VTB package is installed. For example, C:\Program Files\Keysight\SystemVueVTB2022.

         2. VTB_Examples.wsv is old SystemVue file and VTB_examples_new.wsv is converted file.

    3. The following successful message is displayed.
      Created: VTB_example_new.wsv

    4. You can now use the VTB_examples_new.wsv workspace in ADS.

  • When multiple VTB versions are installed, the VTB package in the Library Configuration Editor remain fixed to a particular VTB version. However, symbol view uses the correct VTB version.

Examples - Known Issues

  • Examples under <ADS Install Directory>\examples \Instrument_links folder are not getting opened on Linux where as they are opening fine on Windows.
    Workaround: Rename the ‘Instrument_links’ folder to ‘Instrument_Links’, if you have write permission to the <ADS Install Location>\examples folder. In case you do not have the write permission then proceed with manual unarchive process (File > Unarchive from the ADS Main window) pointing to the Example workspace. 

  • Example search might not work and prompt you the "Database is locked" error when ADS installation is on NAS.
    Workaround: Restart the nfslock service on client. In case the problem still persists, reboot the client to unlock the database.

  • Unable to compile Pin Diode Model using Visual Studio 2012 on Windows 7 64-bit platform.
    Workaround: Delete the contents of the directory examples\RF_Microwave\UserCompiledModel_wrk\ UserCompiledModel\lib.win32_64 before using UCMs.
  • An error occurs while running a custom VTB.
    Workaround: Download and run a custom VTB from the following location: <ADS Install Location>\SystemVue\2016.08\win32_64\VTB. 


  • PDF generation triggered from the PDF button in the installed documentation does not work when the default browser in Mozilla Firefox.
    Workaround: Use Google Chrome or Microsoft Edge or switch to online documentation and generate PDF.
  • On Windows, printing directly from installed documentation generates non-readable output.
    Workaround: Use the PDF version of the document for printing purposes.

  • From 2017 onwards, in the installed documentation when you open a page using the "Open a link in new tab" option the documentation does not open a page in a different tab by default. You need to set the preferences to open any link in a new tab.
    To set the preferences:

    1. From the 201x version of the installed documentation, Click Edit > Preferences.
      The Preferences Dialog box is displayed.

    2. Select the Options tab.

    3. Under Appearance, select the Show tabs for each individual page option.

    This is a one-time setting for a particular release of a product.
  • Unable to open online documentation, any external link, or Embedded Survey link in Linux on Mozilla Firefox browser.
    Workaround: Use Mozilla Firefox version 39 or above or keep the Mozilla Firefox window open and then try to open online documentation.
  • While using the installed documentation, you may encounter issues like documentation not showing any content, it throws an error, it displays unexpected hierarchy in the Content tab, or it does not display any search results.
    Workaround: Close the documentation, delete the contents of the following directory, and open the documentation again.
    • On Windows:  C:\Users\<Windows_Login_ID>\AppData\Local\Keysight\Help
    • On Linux: 
      • $HOME/.local/share/Keysight/Help
      • $HOME/.cache/Keysight
      • $HOME/.cache/rfdeqthelp
  • The installed help search does not support [] or {} or any other text using these combinations.
  • On Linux, Konqueror web-browser does not display the online documentation properly. It may not display documentation pages at all or may display them broken and with errors.
    Workaround: Use Mozilla Firefox to view the online documentation.

Please help us improve
Please help us improve
Was this topic helpful? Yes No