This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

when creating a schedule for AWS in the beacon ui the AWS schedule is not applied or created

Symptoms:

when creating a schedule for AWS in the beacon UI the AWS schedule is not applied or created whereas this should happen

Diagnosis:

1.png

2.png

3.png

(no “AWS Import” Schedule listed)

Solution:

Workaround:

  • close beacon UI

4.png

  • stop beacon service

5.png

  • navigate to beacon programdata folder C:\ProgramData\Flexera Software\Beacon

6.png

  • rename "schedule.xml" to "schedule.bak" (or just erase or store in an archive)

7.png

  • start the beacon engine service & launch the beacon ui

8.png

this will create a new schedule.xml which should solve this issue

9.png

10.png

 

Fix:

This was a bug that was fixed in FNMS 2019r1 version of the beacon, the bug subject was:

Default schedule "AWS imports" is not created if schedule.xml already exists during upgrade

‎Jun 30, 2020 09:57 AM

Was this article helpful? Yes No
No ratings
0 Kudos
Version history
Last update:
‎Jun 30, 2020 09:57 AM
Updated by: