cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

AWS - Test connection failure - Error unmarshalling back from AWS

Hi,

we have installed on our Beacon Server (FNMS 2022R1) the required AWS Modules for our connection:

PS C:\Program Files\WindowsPowerShell\Modules> get-module -listavailable

    Directory: C:\Program Files\WindowsPowerShell\Modules

ModuleType Version    Name                                ExportedCommands

---------- -------    ----                                ----------------

Binary     4.1.384    AWS.Tools.Common                    {Clear-AWSHistory, Set-AWSHistoryConfiguration, Initialize...

Binary     4.1.384    AWS.Tools.EC2                       {Add-EC2CapacityReservation, Add-EC2ClassicLinkVpc, Add-EC...

Binary     4.1.384    AWS.Tools.IdentityManagement        {Add-IAMClientIDToOpenIDConnectProvider, Add-IAMInstancePr...

Binary     4.1.384    AWS.Tools.S3                        {Add-S3PublicAccessBlock, Copy-S3Object, Get-S3ACL, Get-S3...

Binary     4.1.384    AWS.Tools.SecurityToken             {Convert-STSAuthorizationMessage, Get-STSAccessKeyInfo, Ge...

Binary     4.1.419    AWSPowerShell                       {Clear-AWSHistory, Set-AWSHistoryConfiguration, Initialize...

Binary     4.1.420    AWSPowerShell.NetCore               {Clear-AWSHistory, Set-AWSHistoryConfiguration, Initialize...

Script     2.9.0      Az.Accounts                         {Disable-AzDataCollection, Disable-AzContextAutosave, E

1) "Test connection" brings the error message:

Test connection failure - Error unmarshalling response back from AWS. (see screenshot please)

2) The Inventory import shows Failed - error message: "Inventory gathering failed. Error: The 'Set-AWSProxy' command was found in the module 'AWS.Tools.Common', but the module could not be loaded. For more information, run 'Import-Module AWS.Tools.Common'."

This can be found in the log file:

2023-10-09 10:11:43,737 [INFO ] Failed to execute Reader 'Get AWS EC2 dedicated hosts information' from file C:\ProgramData\Flexera Software\Compliance\ImportProcedures\Inventory\Reader\amazon web services\Instance.xml, at step line 1
Error: The 'Set-AWSProxy' command was found in the module 'AWS.Tools.Common', but the module could not be loaded. For more information, run 'Import-Module AWS.Tools.Common'.

I would be very grateful for ideas, support. 

 

 

 

 

(2) Solutions

Hi @ilknur , 

Seems like a Proxy issue, Please check the proxy connections on the beacon server.

View solution in original post

Hi @ilknur , 

Please check if these both AWS.Tools.Common and AWSPowerShell modules installed on the server.

Given that the AWS.Tools.Common module is installed under the C:\Users\*****\Documents\WindowsPowerShell\Modules directory that is private to the "Particular" user (so wouldn't be available to processes running under other user accounts running on this server), I would suggest deleting that one to see if that resolves the error (or changes the error in some way).

Hopefully the AWSPowerShell  module that is installed under C:\Program Files (x86)\AWS Tools\PowerShell will be enough for the FlexNet Manager Suite AWS connector to run, but the import process will give you an error message if it is not enough.

https://community.flexera.com/t5/FlexNet-Manager-Forum/AWS-EC2-connector-import-failing/m-p/153202

View solution in original post

(3) Replies

Hi @ilknur , 

Seems like a Proxy issue, Please check the proxy connections on the beacon server.

Thank you lajakiram,
The proxy settings are the same as on all our servers. What exactly should I check there?

Hi @ilknur , 

Please check if these both AWS.Tools.Common and AWSPowerShell modules installed on the server.

Given that the AWS.Tools.Common module is installed under the C:\Users\*****\Documents\WindowsPowerShell\Modules directory that is private to the "Particular" user (so wouldn't be available to processes running under other user accounts running on this server), I would suggest deleting that one to see if that resolves the error (or changes the error in some way).

Hopefully the AWSPowerShell  module that is installed under C:\Program Files (x86)\AWS Tools\PowerShell will be enough for the FlexNet Manager Suite AWS connector to run, but the import process will give you an error message if it is not enough.

https://community.flexera.com/t5/FlexNet-Manager-Forum/AWS-EC2-connector-import-failing/m-p/153202