BigFix OS Deployment Error: Waiting for the os deployment server to unblock this target

[bfadmin]

I’ve created a Windows 7 32-bit bare metal profile and deployed on a VM while executing the tasks, it shows “Waiting for the os deployment server to unblock this target”. [Screenshot attached]

When I checked the logs from OS Deployment Web Interface below logs were captured.

[2019/01/02 11:10:34:806] W Action Menu chose TASKMENU3
[2019/01/02 11:10:35:09] W About to launch a linked task.
**[2019/01/02 11:10:37:526] W Loading activity from net://global/hostactivities/task364515743/activity.ini (radset-wndwsstrTMYY3LRV.ini) **
**[2019/01/02 11:13:18:214] W Loading activity from ini file (net://global/hostactivities/task364515743/bom13.ini) **
**[2019/01/02 11:13:19:261] - - - - ACTIVITY PLAN - - - - **
[2019/01/02 11:13:19:261] [4]TASK 364515743
**[2019/01/02 11:13:19:261] - - - - - - - - - - - - - - - **
[2019/01/02 11:13:19:277] W Exception occurred
[2019/01/02 11:13:19:277] W Index out of range [:0] in file hostactivity.rbc, line 657
[2019/01/02 11:13:19:277] W no such action index(0)
[2019/01/02 11:13:19:277] W called from ActivityPlan_GetActionDescription (activity_plan.rbc:109)
[2019/01/02 11:13:19:277] W called from run (sequencer.rbc:3797)
[2019/01/02 11:13:19:277] W called from RAD_CheckForActivity (load.rbc:23601)
[2019/01/02 11:13:19:277] W called from AgentDispatch (rbagent.rbc:4396)

I’ve searched a lot for this issue but didn’t get any appropriate answer, If anyone comes across with such error, a response will be appreciated.

Thanks

[bfadmin]

@JasonWalker, @sergio_tarchi, guys any idea where should I look for the error?

[bfadmin]

Has anyone come across above error? Please need help to get rid of it.
Thanks

[bfadmin]

@vtripodi, have you ever come across this error? Where should I start looking for troubleshooting?

[vtripodi]

I got this error but it was a long time ago and, as far as I can remember, the log was different so take with a grain of salt what I reporting in the following.
In my case it was related to a target where I tried a deployment, the installation was not successfull (the target booted twice to get the right driver then it stopped becasue osd did not found the right driver). Then I sent another deployment to the vm using the osd fixlet from BigFix console and I got the error. From the OS Deployment Web Interface I had to cancel either the previous task or the target (in the latter case I performed again the pxe boot for this target).
I suggest that you open a support case for your problem attaching the logs.

[bfadmin]

Hi @vtripodi, not sure if this is the exact reason to cause the deployment failed but this seems to be a proxy server issue which was configured on OSD server machine and blocked access to BigFix root server. We allowed access to BigFix root server and now able to deploy the profile successfully.