Foglight Agent Move / Migration from one Foglight Agent Manager to another Fails due to Missing lockbox ID that does not exist actually. (4258965)

Foglight Agent Move / Migration from one Foglight Agent Manager to another Fails due to Missing lockbox ID that does not exist actually.

Running KB Move Agent To another Fglam failing due to Missing Lockbox ID nnnnnnn on source FglAM.  Actually this ID does not match any lockbox in diagnostic snapshot. Lockbox does not exist.

Missing Lockbox could be caused by a Deleted lockbox in the past but credential cache did't refresh on source FglAM

Please follow the steps below to refresh the Credential Cache in Source FglAM:

1. Shutdown source FglAM
2. Check timestamp on state/default/credentials/query.cache.xml and state/default/credentials/credential.cache.xml it should match the shutdown time of the process
3. Start FglAM with credential caching disabled flag, open a command prompt and run:    <Fglam_home>/bin/fglam -Dcom.quest.glue.disable.credential.cache
4.  Stop FglAM, another command prompt can be used for this purpose:     <Fglam_home>/bin/fglam -q   or do Ctrl+C in running command prompt. Do not close the command prompt.  Wait for message "Core shutdown complete"
5. Verify the state/default/credentials/query.cache.xml and state/default/credentials/credential.cache.xml files should not exist.​
6.  Start fglam service in normal fashion.
7. Then try again the migration process Move Agent To another Fglam

To verify existing lockbox and its ID, you can use this script in Script Console: // Begin - Foglight - List Lockbox / ID groovy script def topSvc= server.get("CredentialManagementService"); def ts=topSvc.listLockboxes(); def lockboxInfo =new ArrayList(); for(obj in ts) { lockboxInfo.add("lockboxId="+obj.getId()+", lockboxName="+obj.getName()); } return lockboxInfo //End