SCCM Pull Distribution Point MSI Installation Error 1602

I have a MSI installation problem with a Pull Distribution Point. When I read pulldp_install.log on "LOCAL_LETTER:\SMS_DP$\sms\logs" I can find an error 1602.

Product: ConfigMgr Distribution Point -- Installation operation failed.
Windows Installer installed the product. Product Name: ConfigMgr Distribution Point. Product Version: 5.00.8634.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1602.

I have also some Error 1168 too during "closing MSIHANDLE"
I/O on thread XXX could not be cancelled. Error: 1168

      











 I already have this kind of problem. So I stop "SMS Agent Host" process (net stop ccmexec in cmd or in remote this powershell command: Get-WmiObject -ComputerName COMPUTERNAME -Class Win32_Process -Filter " name='CcmExec.exe' "  | Stop-Process )

I wait some minutes and Pull Distribution Point installation is now successfully


Product: ConfigMgr Distribution Point -- Installation operation completed successfully.
Windows Installer installed the product. Product Name: ConfigMgr Distribution Point. Product Version: 5.00.8634.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0.

SCCM Bug: Push Client - ERROR: Unable to access target machine for request - Error 1003 - ccm.log

If you have error "Unable to access target machine for request" with error code "1003" in your "Microsoft Configuration Manager\Logs\ccm.log" on your secondary or your primary

...
======>Begin Processing request: "2097199533", machine name: "MYMACHINE"  $$ <03-01-2018 18:27:05.821-480="">
Execute query exec [sp_IsMPAvailable] N'SEC'~  $$ <03-01-2018 18:27:05.822-480="">
---> ERROR: Unable to access target machine for request: "2097199533", machine name: "MYMACHINE",  access denied or invalid network path.  $$ <03-01-2018 18:27:05.823-480="">
Execute query exec [sp_CP_SetLastErrorCode] 2097199533, 1003~  $$ <03-01-2018 18:27:05.824-480="">
Stored request "2097199533", machine name ""MYMACHINE", in queue "Retry".  $$ <03-01-2018 18:27:05.827-480="">
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097199533, 2~  $$ <03-01-2018 18:27:05.831-480="">
Execute query exec [sp_CP_SetLatest] 2097199533, N'03/01/2018 10:27:05', 194~  $$ <03-01-2018 18:27:05.842-480="">
<======End request: "2097199533", machine name: ""MYMACHINE".  $$ <03-01-2018 18:27:05.851-480="">
....
<03-01-2018 18:27:05.824-480=""> <03-01-2018 18:27:05.827-480=""> <03-01-2018 18:27:05.831-480=""> <03-01-2018 18:27:05.842-480=""> <03-01-2018 18:27:05.851-480="">  
Instead of:

...
======>Begin Processing request: "2097199533", machine name: "MYMACHINE"  $$ <03-01-2018 18:51:25.981-480="">
Execute query exec [sp_IsMPAvailable] N'SEC'~  $$ <03-01-2018 18:51:25.987-480="">
---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)~  $$ <03-01-2018 18:51:25.988-480="">
---> Attempting to connect to administrative share '\\MYMACHINE.mydomain.net\admin$' using account 'MYDOMAIN\AdminAll'~  $$ <03-01-2018 18:51:25.988-480="">
...
Error 1003 normally is: "Cannot complete this function." but here it is a SCCM Bug (CB 1706 and 1710. Perhaps before and after)



Resolution: (Do it on your Primary SQL server, Secondary will do synchronization)

1st: get all client with 1003 error:
SELECT * FROM ClientPushMachine_G
WHERE 1=1
AND LastErrorCode = '1003'

(and save these informations to create a collection to re-push client)

2nd:delete all line with 1003 error : (WARNING: modify database directly is NOT permit by Microsoft - backup your database before any modifications)
DELETE FROM ClientPushMachine_G
WHERE 1=1
AND LastErrorCode = '1003'


3rd:re-push you clients
All should be OK now

IIS HTTP Error 503 due to Limits in our SCCM Distribution Point

One of our IIS server have HTTP Error 503 (a SCCM Distribution Point)

Multiple check....All Seems OK.....
After some research, we found a colleague modified "Limits" in "Default Web Site" like these screenshots:

He checked "Limit bandwidth usage" (this is NOT the problem) but he checked "Limit number of connections" and set low value (50 is too low for this application, there is more connections all day long)

Normally, there is NO limitation in "Default Web Site" as below screenshot:

Reinitializing parameter (uncheck "limit number of connections"), and now IIS is OK



Conclusion:
Does not modify IIS "Limit number of connections" if you don't have a real good reason (license reason for example) and only if you must know how many users use your application in same time.
You can use "Limit bandwidth usage" to limit bandwidth usage if you need to restrict Distribution Point bandwidth (reason:VPN, low bandwidth cable use by multiple application...)