• 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. Problem with cdsdoc (version2.1) of hotfix IC 5141

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 125
  • Views 14663
  • 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

Problem with cdsdoc (version2.1) of hotfix IC 5141

RAO VINAY
RAO VINAY over 13 years ago

Hi,

I am using IC5141 hotfix and cdsdoc version is 2.1. I don’t have any problem to open cdsdoc in Mozilla but I am not able to view any of the images and also I am not able to go down to any of the link which are usually given in documents. Images in document looks like broken one which is as shown in pic (It is attached to this post). Whenever I am trying to open any link, it throws some warning saying

“The connection was refused when attempting to contact vlsi60:9000.”

And then it never opens. How can I resolve this? Any kind of suggestion would be appreciated.

  • cdsdoc_image_prob.jpg
  • View
  • Hide
  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 13 years ago

    Hi Vinay,

    You should not need that solution if running on RHEL4. Can you try doing:

    cdsdoc -test
    which cdsdoc

    also try these steps:

    If CDSDoc is running, shut it down by clicking Exit in the Library window.
    Make sure old CDSDoc processes are not running:

    • Use the ps -ef command to look for the processes obServer and https. If they are running, use the kill command to terminate them.


    Set the debug environment variable in a shell window (UNIX) or command prompt (Windows).

    •  setenv CDS_DEBUG_CDSDOC "debug"


    Restart CDSDoc . Go through the steps of opening a document, and then post the debug output that appears in the terminal window.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 13 years ago

    Hi Vinay,

    You should not need that solution if running on RHEL4. Can you try doing:

    cdsdoc -test
    which cdsdoc

    also try these steps:

    If CDSDoc is running, shut it down by clicking Exit in the Library window.
    Make sure old CDSDoc processes are not running:

    • Use the ps -ef command to look for the processes obServer and https. If they are running, use the kill command to terminate them.


    Set the debug environment variable in a shell window (UNIX) or command prompt (Windows).

    •  setenv CDS_DEBUG_CDSDOC "debug"


    Restart CDSDoc . Go through the steps of opening a document, and then post the debug output that appears in the terminal window.

    Regards,

    Andrew.

    • 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