Issue
You are getting Server busy, unable to complete request Code 433 on all patch jobs ran on the clients. This can be seen in the status of a patching task in the Scheduled Tasks of the console or seen in a vulscan.log file located on the client.
Cause
Likely patching is still taking place but returning information to the core is unable to complete which is giving this error. You can verify this by looking in a vulscan log located in the C:\Programdata\LANDesk\Log folder on the client. In the vulscan.log file at the very end, you should see a postcgi.exe entry like the ones shown below but ending with an error near the end of the vulscan log when it tries to upload data to the core.
A good entry is show here:
Thu, 03 Aug 2017 11:08:39 HTTP POST: http://LDMS20163.ak.local:443/incomingdata/postcgi.exe?prefix=vulscanresults\&name=ScanResults_{E0098567-4CC5-1F41-B922-2D5DDB6B8FDB}_034.vrz
Thu, 03 Aug 2017 11:08:39 Setting a proxy...
Thu, 03 Aug 2017 11:08:39 Setting socket timeout to 1000 * 60 * 4
Thu, 03 Aug 2017 11:08:39 Success
A failing log entry is shown here, the HTTP error code on the end of the failed entry might be different in your environment, note the 433 return code at the bottom of the vulscan log:
Thu, 03 Aug 2017 09:52:18 HTTP POST: http://LDMS20163.ak.local:443/incomingdata/postcgi.exe?prefix=vulscanresults\&name=ScanResults_{E0098567-4CC5-1F41-B922-2D5DDB6B8FDB}_034.vrz
Thu, 03 Aug 2017 09:52:18 Setting a proxy...
Thu, 03 Aug 2017 09:52:18 Setting socket timeout to 1000 * 60 * 4
Thu, 03 Aug 2017 09:52:19 Failed http://LDMS20163.ak.local:443/incomingdata/postcgi.exe?prefix=vulscanresults\&name=ScanResults_{E0098567-4CC5-1F41-B922-2D5DDB6B8FDB}_034.vrz on server (0), server status: 404.
Thu, 03 Aug 2017 09:52:19 HTTP Error 404. Giving up.
Thu, 03 Aug 2017 09:52:19 Last status: Failed: No response from core
Thu, 03 Aug 2017 09:52:19 Failed to put vulnerability results to core as file: 8DB301B1
Thu, 03 Aug 2017 09:52:19 Skipping repair step because scan errors occurred.
Thu, 03 Aug 2017 09:52:19 ReleaseMutex 'Global\vulscan_scan' succeeded. Code: 0
Thu, 03 Aug 2017 09:52:19 Failed
Thu, 03 Aug 2017 09:52:25 Read from pipe (0x230) failed: 109
Thu, 03 Aug 2017 09:52:25 ClosePipes
Thu, 03 Aug 2017 09:52:25 Exiting with return code 0x8db301b1 (433).
Resolution
Please ensure that the file postcgi.exe is still well present in the folder C:\Program Files\LANDesk\ManagementSuite\incomingdata and that it was not deleted by your antivirus. If the file is still there, please proceed to the following steps:
On the core itself, open IIS Manager. Select you core name on the left pane then open ISAPI and CGI Restrictions. An entry for postcgi.exe should be present in ISAP and CGI Restrictions section as shown in the photo. If one is not present add an entry for it by clicking Add on the right Make sure it is set to Allow and Allow Extension Path to Execute is checked.
The next section to look at is the incomingdata settings under Default Web Site by expanding the tree. You should see two entries under Handler Mappings One for CGI-exe and ISAPI-dll both should be enabled here in incomingdata but they disabled in the other parts of the website this is normal. If they are not enabled or missing, select Edit Feature Permissions on the right menu and check all boxes in the dialog to Enable or Add Script Map to create an entry.
After you make the changes close IIS Manager and run a patching task on the client again.