• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. ADE Explorer Message 2110

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 8760
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ADE Explorer Message 2110

AndyChen5168
AndyChen5168 over 2 years ago

Hi,

I run ADE Assembler simulation long hours will get error message "ADE Explorer Message 2110".

Could you know how to resolve this issue and setting ?

Error message:

ERROT(EXPLORER-2110). Cannot run simulation because the Cadence Message  Passing Subsystem (MPS) used by ADE Explorer or ADE Assembler to communicate with background processes is unavailable in the vrituosoxxxx session.

A possible reason could be that cdsNameServer has stopped running. Restart Virtuoso and the rerun simblation in this maestro cellview.

Thank

Andy

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 2 years ago

    Andy,

    That is indeed the reason - somebody has killed the cdsNameServer process. What used to happen in the past was that if the cdsNameServer process got killed, then things would generally stop working as the mechanism for ADE to communicate with the child processes would fail - so you'd end up with simulations that appeared not to finish, results wouldn't appear, and so on. Now we introduced a check to tell you as you start the simulation - and the only solution is to quit Virtuoso and restart.

    Now, the main issue is preventing cdsNameServer from being killed. The main issue is usually caused by using a job submission system such as LSF to start Virtuoso, and then that being set up to kill all related processes when the job ends. Because cdsNameServer is started by the first person who needs it on a machine, if that virtuoso ends and LSF/SGE etc is set up this way, then it might kill the cdsNameServer and that would impact any other users on the same machine that happened to be utilising the cdsNameServer started by the first user.

    The way around this is to use the "daemon starter" setup - go to the Help menu in any Virtuoso window and in the search box at the top of the help menu, type "daemon starter".

    There's a little bit about it in these articles:

    How to resolve Virtuoso job shown running on LSF farm even after exiting

    Troubleshooting ADE Explorer, ADE Assembler, and ADE XL

    If you get stuck, you should contact customer support.

    Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • AndyChen5168
    AndyChen5168 over 2 years ago in reply to Andrew Beckett

    Thanks @Andrew Beckett for your good information.

    We'll try to reopen Virtuoso and try to use the "daemon starter"

    Regards,

    Andy

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • AndyChen5168
    AndyChen5168 over 2 years ago in reply to Andrew Beckett

    Thanks @Andrew Beckett for your good information.

    We'll try to reopen Virtuoso and try to use the "daemon starter"

    Regards,

    Andy

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information