CCR 2629988: Doc Assistant cannot connect to the online server
Description: Doc Assistant does not connect to the online documentation server when launched in the Online mode because of network issues.
Workaround: Set the Proxy Server before launching Doc Assistant.
CCR 2642435: Downloading and installing updates for a single product not working
Description: Updates for multiple products are installed even when you try to download and install updates for a single product from the My Downloads page.
Workaround: This issue is being investigated. In case, you want to install updates for all the available products, select all the products in the list and download them.
CCR 2642427: Download status is not updated even after the download is complete
Description: When you download updated documents for a product on the My Downloads page, the status of the download is not updated automatically.
Solution: Click the Refresh button to update the download status.
CCR 2549352: Low space in the home directory results in multiple issues with Doc Assistant
Description: Some of the following issues might be observed if there is not enough free space in the home directory:
- Doc Assistant exits unexpectedly
- Doc Assistant hangs after launch
- Displayed content is distorted
- A blank page is displayed
Solution: To resolve these issues, set the CDA_DISABLE_CACHE environment variable to True.
CCR 2549356: Dashboard takes time to load on RHEL7.7 on the first launch.
Description: When you launch Doc Assistant for the first time on a RHEL7.7 system, it takes approximately 10 seconds for My Dashboard to display.
Solution: The issue is being investigated.
CCR 2562202: Doc Assistant launches in Offline mode
CCR 2757746: On switching from TA to Doc Assistant, Doc Assistant goes offline
Description: Doc Assistant is launched in the Offline mode even if the CDA_OFFLINE environment variable is not set.
Solution: Try to relaunch Doc Assistant after deleting all the files and directories from the $HOME/.config/cadence directory.
CCR 2759092: Help button does not work when it is called from libManager application without a Virtuoso session
Description: The Help buttons in certain Cadence Library Manager forms do not open relevant Help topics.
Solution: The release you are using is not available on the Cadence documentation production server. Contact your system administrator or your Cadence customer support representative for more information.
CCR 2756750: Online mode not available in the Doc Assistant standalone launch
Description: In Doc Assistant, when you switch from Offline Documentation mode to Online Documentation mode, an error message is displayed that states that the release is not available on the Doc Assistant servers. Doc Assistant fails to launch in Online Documentation mode.
Solution: The release you are using is not available on the Cadence documentation production server. Contact your system administrator or your Cadence customer support representative for more information.
CCR 2780674: Opening Task Assistant makes the Doc Assistant go Offline
Description: When a user guide is opened by clicking a link in a Task Assistant, the Doc Assistant interface automatically switches to Offline documentation mode.
Solution: Task Assistant works only in Offline documentation mode. Therefore, Doc Assistant is launched in Offline documentation mode when accessed from the Task Assistant. On closing Task Assistant, the Doc Assistant automatically returns to its previous documentation mode.
At any point, you can switch on the View Documentation Online option in the Hamburger menu to switch to Online documentation mode.
FUSION-1818: An ambiguous warning flags in the CIW on opening a help form.
Description: When Doc Assistant is launched from Virtuoso, at certain times, the Doc Assistant opens and the relevant topic is displayed. However, the following error is displayed in the CIW.
WARNING obShowTag for tool "Command_Interpreter", tag "ciw" (version "") failed, status 1 = obcViewerNotResponding
ERROR (HELPAPI-002): Help viewer is not responding.
Warning No help found for help symbol ciw
Solution: This issue is noticed predominantly in slow machines with low specifications. The recommended configuration is a 4 Core CPU and 16GB RAM. Also ensure that there are no additional users sharing the ephemeral port.
FUSION-1892: The | (pipe) special character is not working in search in Offline documentation mode
Description: Adding a pipe symbol in the search string does not give the intended results.
Solution: Currently, there is no solution or workaround for this issue.
FUSION-1911: The Hamburger menu is hidden when Doc Assistant is zoomed in while the topic viewer is opened
Description: The Hamburger menu does not appear when the Doc Assistant window is zoomed in to higher values, for example, 160%.
Workaround: Currently, there is no solution or workaround for this issue.
CCR 2791272: * with less than 3 characters is not giving proper results
Description: Search keywords that include the * wildcard character and are less than three characters in length, for example, co*, do not retrieve the required search results.
Workaround: Ensure that search keywords with the * wildcard include at least three characters, for example, conf* instead of co*.
CCR 2791282: Windows Scaling issue in Doc Assistant
Description: In Windows, when the scaling is increased, for example, to 150%, the Dashboard, Bookmarks, and a few other options in the Doc Assistant are not visible.
Workaround: Reduce the scaling to 100% and re-open the Doc Assistant. Alternatively, you can update the Doc Assistant application properties.
- Right-click the Doc Assistant application (
cda.exe). - Choose Properties.
- Open the Compatibility tab.
- Click High DPI Settings.
- Select Override high DPI scaling behavior.
- Select Application from the Scaling performed by drop-down list.
- Click OK.
- Relaunch Doc Assistant.
CCR 2629988: Manually configuring the proxy server for Doc Assistant not working
Description: Manually configuring the proxy server using the Doc Assistant Settings options does not work for the Windows operating system.
Workaround: Proxy settings in the Doc Assistant Settings are specific to your corporate network and are applicable only to LINUX machines. To set up a proxy server connection manually for a Windows machine:
- Select the Start button
- Choose Settings.
- Select Network & Internet.
- Select Proxy.
- Specify the required proxy settings.
CCR 2642427: Download status is not updated even after download is complete
Description: In certain situations, the download and installation statuses of documents are not updated dynamically during the operation.
Workaround: Click the Refresh button in the My Downloads page to view the updated status.
CCR 2642435: Downloading and installing updates for a single product not working
Description: In the My Downloads page, downloading the document for a single product results in all linked product documents also being downloaded. This is because of the dependency between the HTML pages.
Workaround: Download all dependent documents together.
CCR 2784079: Doc Assistant popups "Render process exited with code 133" message and generate the core file in DPC
CCR 2779651: Doc Assistant in offline mode gives rendering error with exit code:5
CCR 2779661: Doc Assistant : render process crashed when opening cda with product help button
CCR 2781876: Cadence doc assistant; Render process crash 'Render process exited with code; 5 Do you want to reload the page?'
Description: In Virtuoso, accessing the Doc Assistant from the tool Help buttons displays the following error message:
Render process exited with code:5
Do you want to reload the page?
Workaround: Set the following SHELL environment variable before launching Doc Assistant:
setenv QTWEBENGINE_CHROMIUM_FLAGS "--single-process"
Open a Virtuoso session and run Doc Assistant from the Help menu, for example, in the CIW, select Help—User Guide. Doc Assistant appears.
CCR 2805697: Open Weblinks in Browsers setting cannot be updated in Offline mode
Description: The Open Weblinks in Browsers setting is not saved when changed in Offline mode.
Solution: This issue is noticed only in Offline mode. Currently, there is no solution or workaround for this issue.
CCR 2815598: Websocket (505) error continues to come up (on certain machines) even after cleaning up cache
Description: Doc Assistant will give Error (505): No data received. Could not establish Websocket connection.
Workaround: This issue is noticed only in Offline mode. As a workaround user can use Doc Assistant in Online mode or try the following steps.
User can click the Refresh button in the Websocket error (505) page to reload the page. When the error does not go away even after clicking the Refresh button, then perform the steps to remove the following folders
1. Remove the C:\Users\<login>\.config\cadence folder
2. Remove the C:\Users\<login>\AppData\Local\cadence folder