Corrected anomalies in this release

This list identifies the corrected anomalies in the
FactoryTalk Activation Manager
 version 5.03.00. Use the identification information in parentheses to track the anomaly for reference when receiving assistance from Customer Support with a related issue.
  • FactoryTalk Activation Helper service is not running when Startup Type is set to Automatic. (3695570)
    First identified in
    FactoryTalk Activation Manager
     version 5.01.00.
    Workaround:
     Use the Windows
    Services
     dialog to manually start the FactoryTalk Activation Helper service.
  • When performing a borrow operation with an invalid destination, the error message suggests an incorrect binding. (3827299)
    First identified in
    FactoryTalk Activation Manager
     version 5.02.00.
    There is no workaround for this issue.
  • EasyActivate displays an empty serial number, product key, and product version after getting an activation that requires a named user (4028704)
    When an activation requires a named user, but a user is not provided when using EasyActivate from the command line, the EasyActivate GUI should show a [NamedUserRequired] error. The error dialog does not always appear. Sometimes the GUI displays empty fields instead of the error.
    First identified in
    FactoryTalk Activation Manager
     version 5.02.00.
    Workaround:
     To avoid the issue, supply a named user to EasyActivate.exe when a license requires a named user.
  • WebSocket Service does not start if a configuration using FTACmdUtility was incorrect and then fixed (4925062)
    When the WebSocket Service is given invalid parameters using the FTACmdUtility, the FactoryTalk Activation Helper may not receive updated parameters when applying the correct configuration later.
    First identified in
    FactoryTalk Activation Manager
     version 5.02.00.
    Workaround:
     To resolve the issue manually restart the affected services:
    1. Start the Windows Service Manager console.
    2. Stop the FactoryTalk Activation Helper service.
    3. Start the FactoryTalk Activation Websocket Service. The FactoryTalk Activation Helper service will start automatically.
  • When performing a borrow operation from a remote
    FactoryTalk Activation Manager
     using the FTACmdUtility, the Find Available Activations page may display "n/a" in the Product column. (4983208, 3735889)
    First identified in
    FactoryTalk Activation Manager
     version 5.02.00.
    Workaround:
     Borrow activations using the
    FactoryTalk Activation Manager
     user interface instead of the FTACmdUtility.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal