Product Documentation

Known issues

Oct 08, 2015

Known issues in AppDNA 7.6.5

  • Windows 7 x32 and Windows XP x32 snapshot images are not updated on upgrade from AppDNA 7.6 to AppDNA 7.6.5. Workaround: import the OS snapshot image as a custom image. [#26308]
  • For some Web Apps, URL imports are being incorrectly marked as successfully imported after an error in web capture import. Workaround: reimport the Web App or use the Standalone Web Capture tool. [#26306]
  • Re-editing a Xen solution after upgrade results in an error if the target platform was not opened for edit. Workaround: re-create solution. [#26311]
  • Filtering out frameworks on the application list doesn’t work. Workaround: restart the AppDNA client. [#26319]
  • Custom OS images are not retaining their OS relationship dependencies after upgrade. Workaround: reassign OS relationship dependencies. [#26318]
  • The Standalone Directed Spider fails to launch on Vista and XP. Workaround: use the AppDNA 7.6 Web Spider on XP and Vista to capture web pages in Internet Explorer 6 and 7. [#26314]
  • When server side queuing is enabled, OS images with xml larger than 1 GB fail with this error: 'Too many retries waiting to get a lock to load the file details'. Workaround: turn off server side queuing and set SQL memory allotment. [#26295]
  • Remote database installation occasionally fails. A retry will be successful. [#26267]

Known issues in AppDNA 7.6

  • Snapshotting an OS image may take longer than expected due to the collection of .NET  DNA. The command window remains open while the snapshot is being collected and closes when the snapshotting is complete. [#26269]
  • Loading an OS snapshot captured with the latest snapshotter that is more than 1 GB in size may fail with an out of memory exception when using the queue processor. If this occurs, turn off the queue processor and retry. [#26298]
  • After an upgrade to AppDNA 7.6, custom reports and their algorithms continue to appear in the Custom Reports Manager screen although they were removed during the upgrade. To work around this issue, you can manually remove the reports from the list. [#15847]
  • The upgrade to AppDNA 7.6 does not assign solutions permissions to users who have a custom role. When those users log on, the message “There were errors retrieving solution templates” appears. [#17553]

    To work around this issue, log on as an administrator, go to Administration > Roles, select the custom role, and then select the following permissions:

    • SolutionTemplates: Administer
    • SolutionTemplates: Read
    • Solutions: Administer
    • Solutions: Read
  • Unanalyzed applications do not appear in the Windows 8 and Windows Server 2012 applications list and summaries. [#13611]
  • The Build Assessment reports do not show applications as stale after you import an operating system that is in the same family as the one used for the Build Assessment solution. To work around this issue after the operating system is overwritten, configure the Build Assessment solution for the new operating system. [#17160]
  • Forward Path click through to remediation does not work if a custom report name includes a space. To work around this issue, rename the custom report. [#15869]

Limitations in support for local languages

Note: In this topic, the term letter is used in the broad sense of any writing system, including syllabaries and ideographs.

The following is a summary of the known issues when working with local languages:

  • When installing the AppDNA server (a "Complete" installation), install the server files to a location whose path does not contain any non-Latin letters. Otherwise, activating your license may fail with a "The Citrix license server is not running and could not be started" error.
  • The AppDNA database name must not contain non-Latin letters.
  • When running AppDNA on a local language version of Windows, you may find that the text in some screens, windows, and dialog boxes does not display perfectly. For example, sometimes texts may overlap or be truncated. The exact issues vary depending on the language and the fonts that are available.
  • AppDNA does not accept URLs that contain East Asian (such as Japanese or Simplified Chinese) characters for web application captures. The solution is to specify the URL by using the Punycode URL.
  • When running AppDNA on an East Asian language version of Windows, some characters may appear incorrectly and be unreadable in log files and messages (such as the explanation for why an algorithm failed during analysis).
  • When running AppDNA on an East Asian language version of Windows, some characters in the Effort Calculator Word export are unreadable. This can be corrected by selecting a suitable font, such as SimSun-ExtB in Simplified Chinese.
  • When running AppDNA on an East Asian language version of Windows, some characters may not appear correctly (or at all) in the PDF exports. Most of the issues can be corrected by installing the Arial Unicode MS Regular font on the AppDNA server machine. This font comes with Microsoft Office 2003 and later.
  • When you use the Search and Browse screen to search for files, the results incorrectly ignore applications whose names include East Asian characters.
  • When creating new actions or action details for an algorithm, you must not include non-Latin letters in their names.
  • Auto-clicker has been tested with English language installers only and it is not expected to work with installers in other languages.