I upgraded the beacons and I have an error coming from the AWS integration complaining that the accesskey can't be converted to a securestring and it's failing at the test-connection procedure.
I can still run cmdlets in the ps shell without issue on the same machine and pull the data using the same cmdlets in the documentation. Not even sure what the issue is. I looked at the readers and it looks fine.
I have heard a report that this problem only happens when testing the connection in the beacon UI, but doesn't affect the actual import process. If you save the connection details before pressing the Test button then it should be OK and the connection will still work during the import process (assuming the correct details have been entered).
If anybody gets a chance to verify this observation, please post your experiences here!
(Did my reply solve the question? Click "ACCEPT AS SOLUTION" to help others find answers faster. Liked something? Click "KUDO". Anything expressed here is my own view and not necessarily that of my employer, Flexera.)
I also facing same issue while integrating with AWS. Right now we are using version FNMS 2021R1.
The value for 'Access Key' is not valid.
--Details---
PowerShell method 'Test-Connection' failed Cannot process argument transformation on parameter 'accessKey'. Cannot convert the "XXXXXXXX" value of type "System.String" to type "System.Security.SecureString".
This is a bit of a wild guess, but I wonder whether this problem is related to the PowerShell version that is installed on the beacon.
What output do you get if you open a PowerShell window and enter the following:
$PSVersionTable
(Did my reply solve the question? Click "ACCEPT AS SOLUTION" to help others find answers faster. Liked something? Click "KUDO". Anything expressed here is my own view and not necessarily that of my employer, Flexera.)
I'm running 5.1. It works fine on version 16, but upgrade to 17 and it breaks. The current workaround is to use version 16 for AWS and anything else that happens to break after upgrade. I also rebuilt a beacon and same issue. I upgraded one manually and added the aws integration in per specification and it also breaks. All logs and errors produced by the beacon and see on the CLI shows there is an issue at the beacon for version 17 at least in my experience.
I have confirmed what you and I are seeing is a bug with support. I have also identified other bugs on top that will essentially stop the integration from working on the CLI as well on the upgraded beacons. I have a call this morning with support to collect more data before it heads over to an engineer.
Even I am using the same beacon version 17 and I getting the same error while integrating the AWS with Beacon; especially when clicking on test connection.
For testing purpose, i saved the creds and executed the adapter. It worked fine. But in the logs its says the adapter can read the data from AWS. And its not able to write\ create the file for importing.
I have heard a report that this problem only happens when testing the connection in the beacon UI, but doesn't affect the actual import process. If you save the connection details before pressing the Test button then it should be OK and the connection will still work during the import process (assuming the correct details have been entered).
If anybody gets a chance to verify this observation, please post your experiences here!
(Did my reply solve the question? Click "ACCEPT AS SOLUTION" to help others find answers faster. Liked something? Click "KUDO". Anything expressed here is my own view and not necessarily that of my employer, Flexera.)
That's great to have the confirmation - that will help others who are encountering the same thing! Thanks for sharing.
I have not seen anything that indicates a specific timeframe for when the "test connection" behavior may be fixed sorry.
(Did my reply solve the question? Click "ACCEPT AS SOLUTION" to help others find answers faster. Liked something? Click "KUDO". Anything expressed here is my own view and not necessarily that of my employer, Flexera.)
AWS reconciliation taking time more than 60Min, But Flexera suggested to schedule AWS import every 30 min. How we need to workout this issue. If we put every 30 min max times it's failing.
@sreeramyenuga - it doesn't sound like that issue is related to the problem testing the connection that is being discussed in this topic. I would suggest posting a new topic to see if anybody has insight on the time taken by AWS imports.
(Did my reply solve the question? Click "ACCEPT AS SOLUTION" to help others find answers faster. Liked something? Click "KUDO". Anything expressed here is my own view and not necessarily that of my employer, Flexera.)
The issue with testing the AWS connection has been marked to be fixed in the next FlexNet Manager Suite On-premises release. In the meantime, simply avoid using the Test Connection button: as described in this thread, the inability to test the connection when configuring the connection details in the UI will not negatively affect the actual import process.
(Did my reply solve the question? Click "ACCEPT AS SOLUTION" to help others find answers faster. Liked something? Click "KUDO". Anything expressed here is my own view and not necessarily that of my employer, Flexera.)
(Did my reply solve the question? Click "ACCEPT AS SOLUTION" to help others find answers faster. Liked something? Click "KUDO". Anything expressed here is my own view and not necessarily that of my employer, Flexera.)
