Hi,
occasionally, we're receiving a failure in System Tasks for our AWS data gathering.
Gathering inventory data: Failed: Could not find a part of the path 'C:\ProgramData\Flexera Software\Compliance\ImportProcedures\Inventory\Reader\Amazon Web Services\Logic.ps1'.
Full Message from Log:
Failed to execute Reader 'Get AWS EC2 account information' from file C:\ProgramData\Flexera Software\Compliance\ImportProcedures\Inventory\Reader\amazon web services\Instance.xml, at step line 1
Error: Could not find a part of the path 'C:\ProgramData\Flexera Software\Compliance\ImportProcedures\Inventory\Reader\Amazon Web Services\Logic.ps1'.
Beacon is within AWS.
But with next run of the Task the error vanishes.
Any idea?
regards,
Matthias
Oct 12, 2020 05:20 AM
Hi Matthias,
Sounds like the file might be locked by another process. How frequent does the import run?
Best regards,
Markward
Oct 13, 2020 04:00 AM
Hi mfranz,
we're running "out of the box" - standard - schedules and tasks/jobs on AWS beacon.
Except, the initial discovery-Job for AWS is taking more time within it's Job, than the upgrade of Beacon-Policy. So there might be a Timing issue here.
I mean:
AWS-Job for gathering Data from AWS got started and in background policyupdates are done on Beacon-side. Due to this, the scripts on Beacon-side are getting downloaded/deleted and recreated, during collecting the Data from of AWS even if it is not finished yet.
Oct 13, 2020 08:06 AM