Downloads fails on client

Usage and Config Platform
1

I have a fixlet that has worked fine in the past and now when I try to push it to a client, the client reports back that the downloads fail, even though I can see the sha1 folder of the prefectch on the client’s current relay in /wwwrootbes/bfmirror/downloads/sha1

For testing I removed all the lines from the fixlet expect for the 2 prefetch lines.

The action description tab also shows that the downloads have been successfully cached on the root server.
Any other suggestions?

   Report posted successfully
At 14:47:15 -0500 - 
   Successful Synchronization with site 'BES Support' (version 1416) - 'http://sync.bigfix.com/cgi-bin/bfgather/bessupport'
At 14:48:10 -0500 - 
   DownloadPing command received (ID=7241342)
At 14:48:25 -0500 - 
   DownloadPing command received (ID=7241308)
At 14:48:38 -0500 - 
   DownloadPing command received (ID=7241361)
At 14:48:55 -0500 - 
   DownloadPing command received (ID=7241611)
At 14:53:00 -0500 - 
   DownloadsAvailable: checking for 'http://relay1:52311/bfmirror/downloads/7241733/0'
   DownloadsAvailable: true (action id 7241733)
   ActionLogMessage: (action:7241733) Non-Distributed - DownloadsAvailable
   ActionLogMessage: (action:7241733) Submitting download request
   ActionLogMessage: (action:7241733) Download url: 'http://localhost:52311/Uploads/3d706678ec44d71f1bd3df848d30a67741439c54/PortQry.exe.tmp'
   ActionLogMessage: (action:7241733) Download url: 'http://localhost:52311/Uploads/a466e0060e7121454c9d907a6ac697c3baa000fa/QueryUpdateDNS.ps1.tmp'
At 14:58:32 -0500 - 
   DownloadPing command received (ID=7241351)
At 14:58:46 -0500 - 
   DownloadPing command received (ID=7241311)
At 14:58:50 -0500 - 
   DownloadPing command received (ID=7241371)
At 14:59:03 -0500 - 
   DownloadPing command received (ID=7241613)
At 15:01:33 -0500 - 
   Report posted successfully
At 15:03:00 -0500 - 
   DownloadsAvailable: checking for 'http://relay1:52311/bfmirror/downloads/7241733/0'
   DownloadsAvailable: true (action id 7241733)
   ActionLogMessage: (action:7241733) Non-Distributed - DownloadsAvailable
   ActionLogMessage: (action:7241733) Submitting download request
   ActionLogMessage: (action:7241733) Download url: 'http://localhost:52311/Uploads/3d706678ec44d71f1bd3df848d30a67741439c54/PortQry.exe.tmp'
   ActionLogMessage: (action:7241733) Download url: 'http://localhost:52311/Uploads/a466e0060e7121454c9d907a6ac697c3baa000fa/QueryUpdateDNS.ps1.tmp'
At 15:10:12 -0500 - 
   DownloadPing command received (ID=7241617)
At 15:10:23 -0500 - 
   DownloadPing command received (ID=7241314)
At 15:10:25 -0500 - 
   DownloadPing command received (ID=7241363)
At 15:10:46 -0500 - 
   DownloadPing command received (ID=7241381)
At 15:13:00 -0500 - 
   DownloadsAvailable: checking for 'http://relay1:52311/bfmirror/downloads/7241733/0'
   DownloadsAvailable: true (action id 7241733)
   ActionLogMessage: (action:7241733) Non-Distributed - DownloadsAvailable
   ActionLogMessage: (action:7241733) Submitting download request
   ActionLogMessage: (action:7241733) Download url: 'http://localhost:52311/Uploads/3d706678ec44d71f1bd3df848d30a67741439c54/PortQry.exe.tmp'
   ActionLogMessage: (action:7241733) Download url: 'http://localhost:52311/Uploads/a466e0060e7121454c9d907a6ac697c3baa000fa/QueryUpdateDNS.ps1.tmp'
At 15:13:01 -0500 - 
   ActionLogMessage: (action:7241733) JobFailed - cancel and fail action
   ActionLogMessage: (action:7241733) DownloadJobFailed
At 15:13:02 -0500 - 
   ActionLogMessage: (action:7241733) ending action
2

There are two failures possible with that error. The first failure is a pretty severe one that is done when the client tries to set up its download operation. The second would have put out an additional message so it isn’t that one.

There’s nothing set up on the drive the client is running on that might prohibit long file names is there?

3

Not that i’m aware of. It’s happening on Win2012 and Win2008R2

4

and it is occurring across 3 different BF deployments, yet other fixlets with prefetch work just fine. It even fails when I issue the fixlet to run on the Root server.

5

Can you post a copy of the prefetch lines?

6

i noticed that of the 2 prefetches, only 1 was causing the issue. I modified the payload of that prefetch, recaptured it with the Software Distribution wizard and then updated the fixlet with the new prefetch and it worked fine. So i’m not sure what was wrong with that old payload to just stop downloading all of the sudden across multiple environments.