ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
ImportExportCLI fails when using one ARA installation over multiple AE instances
Article ID: 87521
Updated On:
Products
CA Automic Workload Automation - Automation Engine
Issue/Introduction
Affects Release version(s): 6;7
Error Message :
Unhandled Exception: System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> Ventum.Bond2.Services.InvalidUserNameException: Invalid user name, or user system and client mismatch
This occurs in implementations of ARA over multiple AE clients/instances.
ImportExportCLI.exe invoked using anything but the first entry in the customer.config file causes the above error message when used as follows:
References
Error Message :
Unhandled Exception: System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> Ventum.Bond2.Services.InvalidUserNameException: Invalid user name, or user system and client mismatch
This occurs in implementations of ARA over multiple AE clients/instances.
ImportExportCLI.exe invoked using anything but the first entry in the customer.config file causes the above error message when used as follows:
PS C:\Automic\Tools\ARA\Utilities\ImportExportCLI> .\ImportExportCLI.exe deepexport -con http://localhost/ara -usr "200ARA/USERNAME" -pwd PASSWORD -format xml -mt Application -fi myapp.zip
Automic Release Automation Documentation:
Cause
Cause type:
Configuration
Root Cause: Configuration issue resulting from ambiguity in instance names.
Configuration
Root Cause: Configuration issue resulting from ambiguity in instance names.
Environment
Release:
Component: ARLSMG
Component: ARLSMG
Resolution
This field was added on 30/03/2017. This article has not been updated yet. Refer to the "Description" or "Workaround" sections for solution information.
Fix Status: No Fix
Fix Status: No Fix
Additional Information
Workaround :
N/ASOLUTIONUse the full user name: - For RM internal user: // - For AE user: ///This removes any ambiguity in the case of multiple connected AE systems.Example using two tenants: /100 /200 System name: -usr "/200/ARA/USERNAME"
N/ASOLUTIONUse the full user name: - For RM internal user: // - For AE user: ///This removes any ambiguity in the case of multiple connected AE systems.Example using two tenants: /100 /200 System name: -usr "/200/ARA/USERNAME"
Feedback
Yes
No
Powered by
