You may receive below error msg when upgrading System Center Current Branch 1602 to 1606. (in fact in any SCCM version upgrade)
distmgr.log on the Primary site;
Failed to copy f:\Program Files\Microsoft Configuration Manager\bin\x64\smspxeperf.dll to \\SCCB-DP-W2012.LAB\SMS_DP$\sms\bin\smspxeperf.dll. GLE = 32
or
The distribution point ["Display=\\SCCB-DP-W2012.LAB \"]MSWNET:["SMS_SITE=SCB"]\\SCCB-DP-W2012.LAB \ is not installed or upgraded yet.
or
DP thread with ID 6096 failed to process DP action
Event Log on problem DP;
On the DP, Application event log will show "An error occurred while trying to load the module from \SMS_DP$\sms\bin\smspxe.dll for provider SMSPXE. If the provider is marked as critical, the Windows Deployment Services server will be shut down".
Error Information: 0x7F
This will break all the content distribution to the problem distribution point in SCCM.
Fix:
First check and compare the smspxeperf.dll on the primary site server with file on the problem DP.
If the versions won’t match, then rename the existing version on the DP.
If you get access denied error stop WDS service, then rename the smspxeperf.dll. Now copy the new file from primary server or CAS to the problem DP under \SMS_DP$\sms\bin\
You can wait for an hour to site server to re-run the DP upgrade or simply re-start the SMS_SITE_COMPONENT_MANAGER service on the primary site server. This will start the upgrade process straight away. Review the distmgr.log to see the progress of the upgrade.
Once the DP is upgraded try to distribute a simple package and that should get distributed without any issues.
Also review the \SMS_DP$\sms\bin\vcredist.log on the DP for any errors, as in many instances Visual Runtime install also caused the problem.
distmgr.log on the Primary site;
Failed to copy f:\Program Files\Microsoft Configuration Manager\bin\x64\smspxeperf.dll to \\SCCB-DP-W2012.LAB\SMS_DP$\sms\bin\smspxeperf.dll. GLE = 32
or
The distribution point ["Display=\\SCCB-DP-W2012.LAB \"]MSWNET:["SMS_SITE=SCB"]\\SCCB-DP-W2012.LAB \ is not installed or upgraded yet.
or
DP thread with ID 6096 failed to process DP action
Event Log on problem DP;
On the DP, Application event log will show "An error occurred while trying to load the module from \SMS_DP$\sms\bin\smspxe.dll for provider SMSPXE. If the provider is marked as critical, the Windows Deployment Services server will be shut down".
Error Information: 0x7F
This will break all the content distribution to the problem distribution point in SCCM.
Fix:
First check and compare the smspxeperf.dll on the primary site server with file on the problem DP.
If the versions won’t match, then rename the existing version on the DP.
If you get access denied error stop WDS service, then rename the smspxeperf.dll. Now copy the new file from primary server or CAS to the problem DP under \SMS_DP$\sms\bin\
You can wait for an hour to site server to re-run the DP upgrade or simply re-start the SMS_SITE_COMPONENT_MANAGER service on the primary site server. This will start the upgrade process straight away. Review the distmgr.log to see the progress of the upgrade.
Once the DP is upgraded try to distribute a simple package and that should get distributed without any issues.
Also review the \SMS_DP$\sms\bin\vcredist.log on the DP for any errors, as in many instances Visual Runtime install also caused the problem.
Good afternoon Venu.
ReplyDeleteI'm getting the same error "["Display=\\my_remote_DP\"]MSWNET:["SMS_SITE=001"]\\my_remote_DP\ is not installed or upgraded yet." on a remote DP after upgrading to 1710.
Can't distribute any content to it.
In my case I can't find the same error message as you do in event viewer and can't find the file smspxeperf.dll on the remote DP. I only have it on the MP.
Any other ideas?
Cheers,
pedro
Just to add that the problem was solved automatically during the night. Probably SCCM needs some hours to fix the issue.
ReplyDeletecheers,
pedro