Troubleshooting taking screen captures for legacy application documents

Consider these troubleshooting tips to resolve errors that can occur when you use the Document Application tool to include screen captures in legacy application documents.

This content applies to legacy application documents only. For applications that use features and stories, create product overview and gap analysis documents.

Before you can take screen captures with the Document Application tool, your system administrator must enable server-side screen captures. For more information, see “Enabling server-side screen captures for application documents” in the installation information.

  • Connection to the server was refused because the resource URL is not specified in the Data-Admin-System-Setting.

    The Data-Admin-System-Setting instance Pega-AppDefinition – CaptureScreenshotsResourcePath was not updated from its default setting.

    1. Update the Data-Admin-System-Setting instance Pega-AppDefinition – CaptureScreenshotsResourcePath to contain the URL of the service, for example, http://10.224.232.91:8080/prScreenshot/rest/capture.
    2. If updating this setting does not resolve the issue, verify that the server for capturing and storing screenshots was set up during installation of the Pega Platform.
  • Connection to <resourceURL> was refused because the resource URL host name and port number are incorrect in the Data-Admin-System-Setting.

    The Data-Admin-System-Setting instance Pega-AppDefinition – CaptureScreenshotsResourcePath was updated from its default setting but the value is not valid.

    1. Verify that the Data-Admin-System-Setting instance Pega-AppDefinition – CaptureScreenshotsResourcePath contains the correct host name and port number.
    2. If updating this setting does not resolve the issue, verify that the server is available and was set up during installation of the Pega Platform.
  • The resource URL path is incorrect in the Data-Admin-System-Setting.

    The Data-Admin-System-Setting instance Pega-AppDefinition – CaptureScreenshotsResourcePath was updated from its default setting, and a response was received when trying to connect to the server. However, a connection cannot be established with the PhantomJS REST server.

    1. Verify that the Data-Admin-System-Setting instance Pega-AppDefinition – CaptureScreenshotsResourcePath contains the correct URL of the service.
    2. If updating this setting does not resolve the issue, verify that the server was installed and set up correctly during installation of the Pega Platform.
  • The authentication parameters are incorrect in the Data-Admin-Security-AuthenticationProfile.

    Login failed because of an incorrect user name or password.

    1. Update the Data-Admin-Security-AuthenticationProfile instance CaptureScreenshotsAuthProfile with the correct user name and password.
    2. If updating this information does not resolve the issue, verify that the server was installed and set up correctly during installation of the Pega Platform.
  • The server is not responding. Try again and contact your system administrator if the problem persists.

    When the Document Application tool tried to take screen captures, an issue occurred with the server that must be resolved by your system administrator.

  • Screen could not be captured. Try again or choose to override.

    The Document Application tool seemed to take screen captures successfully, but instead of images, this message displays. Your system administrator must verify that the following components are installed on the Linux server that is enabled for taking screen captures:

    • fontconfig
    • freetype
    • libfreetype.so.6
    • libfontconfig.so.1
    • libstdc++.so.6