FlexNet Manager Suite 2018 R2 - VMware Data Gathering Failed Using ESXQuery Agent
We are using ESXQuery Agent to gather VMware Inventories as detailed in the following URL: community.flexera[dot]com/t5/FlexNet-Manager-Knowledge-Base/VMware-Stand-alone-Inventory-Agent-for-FlexNet-Manager-Suite/ta-p/114055
We have deployed, configured the agent and manually pasted the inventories in "C:\ProgramData\Flexera Software\Incoming\Inventories" previously as well and FNMS actually absorbed the files and uploaded the data in the console. And, the pasted files automatically gets disappeared from the above-mentioned path (i.e. under ProgramData).
However, recently yesterday while we repeated the same activities, we found that after pasting the inventory files in "C:\ProgramData\Flexera Software\Incoming\Inventories", FNMS is not absorbing or uploading the same to the console and the files are still there in the folder under the ProgramData path.
If anyone can please let me know why this is happening. What can be the actual reason and how this can be resolved.
Thanks & regards,
This thread has been automatically locked due to inactivity.
To continue the discussion, please start a new thread.
Hi @dennis_reinhardt ,
Yes right, the task is in "Ready" state and not going into "Running" status even through tried to run the task. Under the "History" tab found errors. Please find the attached (PFA) image files for a better understanding/reference.
1. If you can please tell me the path to the error log of these tasks.
2. Also, if you can assist me to resolve this issue please.
Kindly let me know if I need to provide any further details/information.
Thanks & regards,
Hi @sourav_sengupta ,
For me it's look like a failed tasks in task scheduler, under which context do you run the task?
You use service account or SYSTEM account?
Also it is checked that task should run with high privilege and also to run if the user is not logged in?
You can lookup the "Action" from the task and try to run it manually to see what error is produced. As mentioned by Adrian, the user context is important.