Troubleshooting

Troubleshooting AWS Connector for SAP #

This section describes a list of known issues related with AWS Connector for SAP.

Topics


Management Console #

  • Cannot be loaded: Service cannot be reached #

    • Problem: Management Console is started but service is not reachable.

      Service cannot be reached
      
      What has happened?
      URL call was terminated because the corresponding service is not available.
      
      Note
      The termination occured in system with error code 403 and for the reason Forbidden.
      
      
    • Cause

      SICF service wd_rocketsteam_s3 is not active.

    • Solution

      1. Go to SICF transaction
      2. Open the tree to sap -> bc -> webdynpro -> lnkaws
      3. Ensure that service wd_rocketsteam_s3 is active.

  • Cannot be loaded: Server URL cannot be reached #

    • Problem: When you open Management Console, a new browser page is started but server cannot be reached.

      This site can’t be reached
      <hostname.fqdn>’s server IP address could not be found.
      
    • Cause

      Your computer cannot resolve the SAP server fqdn name.

    • Solution

      Ensure that hostname can be resolved from your computer. Try executing the following command to ensure that the server is reachable.

      ping <hostname.fqdn>
      

      Ensure that the ports to the https service are opened from your computer. Try executing the following command to ensure that the listening port is reachable.

      telnet <hostname.fdqn> <sap_https_port>
      

Cannot be loaded: Can’t reach this page #

  • Problem: When you open Management Console, a new browser page is started but server cannot be reached.

    Make sure the web address http:// is correct
    
  • Cause

    Ports HTTP or HTTPS are not active.

  • Solution

    Ask your Basis team to check that both HTTP and HTTPS ports are configured and active in the SMICM transaction


GOS / DMS #

  • System error when accessing Knowledge Provider. #

    • Problem: When you try to upload an attachment or business document you get “System error when accessing Knowledge Provider”.

      If you look for errors in transaction /LNKAWS/AWS_LOG_VIEWER, you find an error with the following text:

      You have no authorization to display destination <RFC DEST>
      
    • Cause

      Sometimes, for unknown reasons, the AWS Connector profile fails to be created during configuration. If that happens, the profile must be created manually.

    • Solution

      1. Open transaction SU02.
      2. Set /LNKAWS/SICF as Profile name in the Manually edit authorization profiles section.
      3. Execute Create work are for profiles.
      4. Create New Profile
      5. Indicate AWS Connector. Authorization profile for S4 in and Text field and mark the Single profile option.
      6. Add the Object S_RFC_ADM with authorization /LNKAWS/AUTH
      7. As /LNKAWS/AUTH does not exist yet, double click on it to create
      8. Press Maintain values…
      9. Add the following values:
        • ACTVT: 03
        • ICF_VALUE: ''
        • RFCDEST: LNKAWS*
        • RFCTYPE: G
      10. Save and Activate.
  • Documents of this type are not allowed in your system #

    • Problem. You try to attach a document to a SAP object but the process fails with the following error message:

      Documents of this type are not allowed in your system.
      
    • Cause

      Logon Data in SICF Service wd_rocketsteam_s3 is incorrect. Client or User/Passord are not correctly set.

    • Solution

      1. Go to SICF transaction
      2. Navigate to ICF node /default_host/sap/bc/webdynpro/lnkaws
      3. Edit service wd_rocketsteam_s3.
      4. Access Logon Data tab
      5. Make sure Client field is set to 000
      6. Make sure User created during AddOn SICF Configuration is set properly.
      7. Make sure Password Status field has the Set status (if set to invalid or initial, re-enter the password)

SAP Data Archiving #

  • Archived sessions can not be retrieved #

    • Problem: When you try to retrieve a file using SARA transaction, the file is not recovered.

    • Cause

      Phisical Path in FILE transaction is not correctly set.

    • Solution

      1. Run FILE transaction
      2. Double-click on Logical File Path Definition to open the properties.
      3. Select ARCHIVE_GLOBAL_PATH from the list and select Assignment of Physical Paths to logical path from the Dialog Structure menu.
      4. Select your SAP Server Operating System and delete the Pyshical path suffix.
      5. If Unix, delete .ARCHIVE from the file path
      6. If Windows NT, delete .ARCHIVING from the file path
  • Retrieval job is cancelled #

    • Problem: You try to retrieve a file using SARA transaction while migration program /LNKAWS/CONTENT_REP_MIGRATION is running. Job is cancelled with message:

      No name can be created for the file for retrieval <file_name>
      
    • Cause

      Retrieval needs to write on table ADMI_FILES that is currently blocked by program /LNKAWS/CONTENT_REP_MIGRATION.

    • Solution

      Wait for the migration process to finish before executing the retrieval again.