...
======>Begin Processing request: "2097199533", machine name: "MYMACHINE" $$
Execute query exec [sp_IsMPAvailable] N'SEC'~ $$
---> ERROR: Unable to access target machine for request: "2097199533", machine name: "MYMACHINE", access denied or invalid network path. $$
Execute query exec [sp_CP_SetLastErrorCode] 2097199533, 1003~ $$
Stored request "2097199533", machine name ""MYMACHINE", in queue "Retry". $$
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097199533, 2~ $$
Execute query exec [sp_CP_SetLatest] 2097199533, N'03/01/2018 10:27:05', 194~ $$
<======End request: "2097199533", machine name: ""MYMACHINE". $$
....
Instead of:
...
======>Begin Processing request: "2097199533", machine name: "MYMACHINE" $$
Execute query exec [sp_IsMPAvailable] N'SEC'~ $$
---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)~ $$
---> Attempting to connect to administrative share '\\MYMACHINE.mydomain.net\admin$' using account 'MYDOMAIN\AdminAll'~ $$
...
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
