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

The Flexera Community is currently in maintenance mode to prepare for the upcoming launch of the new community. Click here for more information.

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: 

Flexera Agent issue

Shubhangishelar
By
Level 4

we installed windows agent on our system and there is no error in the log, we are encountering a couple of issue:

1. The uploader log is not being generated,

2. The ndi.gz file is not reporting to the beacon.

could you please assist us with these issues?

‎Jul 19, 2024 01:55 AM

0 Kudos
(4) Replies

lajanakiram
By Level 6 Flexeran
Level 6 Flexeran

Hi @Shubhangishelar , 

Please check the tracker.log if upload is successful to the beacon. For uploader log, Check under windows/temp or Users/temp folder based on the account used for installing the agent. 

‎Jul 19, 2024 04:51 AM

Shubhangishelar
By
Level 4

we installed windows agent on our system and  we are facing below error.

could you please assist us with these issues?

[7/16/2024 5:49:13 PM (G, 0)] {6920} Uploading file 'system on desktop-4ppmrla at 20240716T161256 (Full).ndi.gz' to 'https://beaconname/ManageSoftRL/Inventories'
[7/16/2024 5:50:18 PM (N, 0)] {6920} Error 0x8007274C: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
[7/16/2024 5:50:18 PM (N, 0)] {6920} Error 0xE050044D: Failed to create remote directory /ManageSoftRL
[7/16/2024 5:50:18 PM (N, 0)] {6920} Error 0xE0690099: Specified remote directory is invalid, or could not be created
[7/16/2024 5:50:18 PM (G, 0)] {6920} ERROR: Remote directory is invalid
[7/16/2024 5:50:18 PM (G, 0)] {6920} Upload failed due to a server side issue. This server may be retried during this upload session.
[7/16/2024 5:50:18 PM (G, 0)] {6920} Upload rule is 'Inventory'
[7/16/2024 5:50:19 PM (G, 0)] {6920} Connecting to upload location 'https://beaconname/ManageSoftRL/Inventories'
[7/16/2024 5:50:19 PM (G, 0)] {6920} Upload username is ''
[7/16/2024 5:50:19 PM (G, 0)] {6920} Upload proxy is ''
[7/16/2024 5:50:20 PM (G, 0)] {6920} Uploading file 'system on desktop-4ppmrla at 20240716T161256 (Full).ndi.gz' to 'https://beaconname/ManageSoftRL/Inventories'
[7/16/2024 5:50:20 PM (N, 0)] {6920} Error 0xE0500005: Host name lookup failed
[7/16/2024 5:50:20 PM (N, 0)] {6920} Error 0xE050044D: Failed to create remote directory /ManageSoftRL
[7/16/2024 5:50:20 PM (N, 0)] {6920} Error 0xE0690099: Specified remote directory is invalid, or could not be created
[7/16/2024 5:50:20 PM (G, 0)] {6920} ERROR: Remote directory is invalid
[7/16/2024 5:50:20 PM (G, 0)] {6920} Upload failed due to a client connection issue. This server will not be retried during this upload session.
[7/16/2024 5:50:20 PM (G, 0)] {6920} WARNING: FlexNet Manager Platform has failed to upload a file to all configured upload servers; aborting attempt to upload these file(s)
[7/16/2024 5:50:20 PM (G, 0)] {6920} Uploading finished
[7/16/2024 5:50:20 PM (G, 0)] {6920} ************************************************************
[7/16/2024 5:50:20 PM (G, 0)] {6920} Unable to upload inventory file(s)
[7/16/2024 5:50:20 PM (U, 0)] {6920} ERROR: Error (s189m263)
[7/16/2024 5:50:20 PM (U, 0)] {6920} ----------------
[7/16/2024 5:50:20 PM (U, 0)] {6920} FlexNet Manager Platform could not upload the inventory.

 

‎Jul 22, 2024 02:22 AM

0 Kudos

mfeinman
By
Level 9
In response to Shubhangishelar

On that Windows server, open a browser to https://beaconname/ManagesoftRL/Test.  (Substitute "beaconname" with your beacon's name as listed in tracker.log. You should see something like the following:

tempo.png

This means that your Windows server can reach your inventory beacon.  What happens when you try this? If it fails to resolve, I suspect this could be a DNS issue.

--Mark

 

‎Jul 22, 2024 02:27 PM