Upload Error for few computers

I am running the task “Initiate Software scan”, scan for 7 computer always stuck…does not progress for hours and days. While rest of the 47 computers it completed it. I checked logs on one of the computers and I get to see following lines repeatedly.


At 09:38:10 +0000 -
[ThreadTime:09:38:10] Starting upload of file ‘0c0b904ca9c3ad71c34c9a7e721a5e5d3e7912d8’ of size 3124
[ThreadTime:09:38:10] Error uploading file ‘0c0b904ca9c3ad71c34c9a7e721a5e5d3e7912d8’, moving to next file in 30 second(s)
At 09:38:41 +0000 -
[ThreadTime:09:38:40] Starting upload of file ‘4f38dc17705f0a7db1774bd2c1219cfe68af23a6’ of size 3116
[ThreadTime:09:38:41] Error uploading file ‘4f38dc17705f0a7db1774bd2c1219cfe68af23a6’, moving to next file in 30 second(s)
At 09:39:12 +0000 -
[ThreadTime:09:39:11] Starting upload of file ‘6fa92d2c3023908d900312e6fe73295f53ee8948’ of size 3113
[ThreadTime:09:39:11] Error uploading file ‘6fa92d2c3023908d900312e6fe73295f53ee8948’, moving to next file in 30 second(s)
At 09:39:42 +0000 -
[ThreadTime:09:39:41] Starting upload of file ‘2b4bf818766e8ccfd2f9d668ed80e0c77d3b852b’ of size 3111
[ThreadTime:09:39:41] Error uploading file ‘2b4bf818766e8ccfd2f9d668ed80e0c77d3b852b’, moving to next file in 30 second(s)
At 09:40:13 +0000 -
[ThreadTime:09:40:12] Starting upload of file ‘0d02e1b84e81b78bcd3e2f02e0fe86f2fa616691’ of size 3114
[ThreadTime:09:40:12] Error uploading file ‘0d02e1b84e81b78bcd3e2f02e0fe86f2fa616691’, moving to next file in 30 second(s)
At 09:40:42 +0000 -
[ThreadTime:09:40:42] Starting upload of file ‘a0e7f8ec05b6c73a2b6e283cab2839030694e598’ of size 3115
At 09:40:43 +0000 -

Not sure what is happening. Pls suggest.

Thank You,
Sangita

In addition to previous post pls refer current dashboard status.
Those 7 computers are not reflecting any changes. I can see “Missing software scan and Software scan never uploaded” status for these 7 computers.

Look into the following KB - Troubleshooting Outdated VM Manager Data status - Customer Support

These setting are not set on the server and as per the document if they have not set already in the computer properties that means they are at their maximum value.

Maybe have a look to these pages on the wiki can help:
https://bigfix-wiki.hcltechsw.com/wikis/home?lang=en-us#!/wiki/BigFix%20Wiki/page/Upload%20and%20Archive%20Manager
https://bigfix-wiki.hcltechsw.com/wikis/home?lang=en-us#!/wiki/BigFix%20Wiki/page/Troubleshooting%20Upload%20Manager

In Your case it is as the relay the agent is connected to is rejecting the request to upload … configuring the deployment to work with the upload manager, if something goes wrong, it appears a good habit start taking care of the following set of configuration settings ( the first on the agent, the second and the third on the relays … on the server they have default value ‘infinite’ and so in general not need to be touched … and the last one on the server ):

_BESClient_ArchiveManager_MaxArchiveSize
_BESRelay_UploadManager_BufferDirectoryMaxSize
_BESRelay_UploadManager_BufferDirectoryMaxCount
_BESRelay_UploadManager_CompressedFileMaxSize

In addition would have a check the AV exclusion on the agent is correctly in place ( procmon can help for this check ):

I figured the scanner version of these problematic 7 hosts is 9.2.32.0000 while other computers having scanner version as 9.2.35.0000. I am trying to upgrade using fixlet action namely “Install or upgrade scanner” so my original problem of initiate software scan and upload scan results will fix (Hopefully) . Now I can see the action is showing these computers as “Not Relevant” . Pls advice how can I upgrade scanner version on these computers.

Thanks,
Sangita Chaudhari

I suggest to check the fixlet relevance and the computer you want to upgrade scanner. Maybe the new is already installed?
If not it might be tricky to figure out what is blocking the relevance to become true. QNA on the computer will be helpful. Are the computer running unix or windows?

Regarding the error from first post, I agree to suggestion by @gpoliafico , the archive manager settings might be to low to fulfill the upload request.

There is a troubleshooting Fixlet (ID:15) in the BigFix Inventory v10 site called Analyze the Relevance of a Fixlet or Task. Select the Install or Upgrade Scanner (9.2.35.0) fixlet from the drop down list in the Description panel, and click the Create Analysis button. It will show which applicability relevance is evaluating to False on the machines having issues.