PENDINGComponent Not Installed by Site Component Manager

P

prytkov

Member
9
0
1
Hello everyone!

I have three servers (1.sccm , 2.sql , 3wsus)

On sccm have critical error, but dont uderstand what's wrong

Thank you for your help and support

Снимок-01.PNG
  • Thread Starter
  • #2
Some of the errors disappeared overnight, but why they disappeared remains a mystery.
I'm sorry, but there are still questions about other componentsСнимок-03.PNG
  • Thread Starter
  • #8
Hello Garth!

Ofcourse i review the component status messages, but dont understand whats wrong. The description of the problems does not give an understanding of the essence of the problem.

Now i'll try to turn firewall off on all servers, and all icons of Site Status turn to "OK"
However in tab "Component Status" i have received several warnings and several critical errors

Could you tell me where to start to find the error

Best regards
  • Thread Starter
  • #10
Can you tell us what errors you see for each component?.

Снимок-07.PNG
Снимок-08.PNG

Ill try to open messages from SMS_EXECUTIVE
--
Site Component Manager did not copy file "C:\Program Files\Microsoft Configuration Manager\bin\x64\system32\smsperf.dll" to "\\SRV-WSUS-01.SCCM.CORP.AERO\ADMIN$\system32\smsperf.dll", because the source file is not a newer version than the destination file.

--
Site Component Manager did not copy file "C:\Program Files\Microsoft Configuration Manager\bin\x64\system32\perf_msg.dll" to "\\SRV-WSUS-01.SCCM.CORP.AERO\ADMIN$\system32\perf_msg.dll", because the source file is not a newer version than the destination file.
--
Site Component Manager did not copy file "C:\Program Files\Microsoft Configuration Manager\bin\x64\syswow64\smsperf.dll" to "\\SRV-WSUS-01.SCCM.CORP.AERO\ADMIN$\syswow64\smsperf.dll", because the source file is not a newer version than the destination file.
--
Site Component Manager did not copy file "C:\Program Files\Microsoft Configuration Manager\bin\x64\syswow64\perf_msg.dll" to "\\SRV-WSUS-01.SCCM.CORP.AERO\ADMIN$\syswow64\perf_msg.dll", because the source file is not a newer version than the destination file.
--
Site Component Manager did not copy file "C:\Program Files\Microsoft Configuration Manager\bin\x64\system32\smsmsgs\srvmsgs.dll" to "\\SRV-WSUS-01.SCCM.CORP.AERO\ADMIN$\system32\smsmsgs\srvmsgs.dll", because the source file is not a newer version than the destination file.
--
Site Component Manager did not copy file "C:\Program Files\Microsoft Configuration Manager\bin\x64\system32\smsmsgs\climsgs.dll" to "\\SRV-WSUS-01.SCCM.CORP.AERO\ADMIN$\system32\smsmsgs\climsgs.dll", because the source file is not a newer version than the destination file.
--
Site Component Manager did not copy file "C:\Program Files\Microsoft Configuration Manager\bin\x64\system32\smsmsgs\provmsgs.dll" to "\\SRV-WSUS-01.SCCM.CORP.AERO\ADMIN$\system32\smsmsgs\provmsgs.dll", because the source file is not a newer version than the destination file.
--
Site Component Manager could not start the SMS_SERVER_BOOTSTRAP_SRV-INST-01 service on site system "\\SRV-WSUS-01.SCCM.CORP.AERO" to install component SMS_EXECUTIVE with the service logging on as account "". The operating system reported error 997: Overlapped I/O operation is in progress.
--
Possible cause: Site Component Manager does not have sufficient access rights to administer the site system.
Solution: Verify that the Site System Installation accounts are properly configured to allow the site to administer the site system.
--
Site Component Manager failed to install this component on this site system.

Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager will automatically retry the installation in 60 minutes. To force Site Component Manager to immediately retry the installation, stop and restart Site Component Manager using the Configuration Manager Service Manager.
--
  • Thread Starter
  • #11
Thanks all for the help, it seems that the firewall did not work properly, I will look for which ports and on which server to open

Best regards
  • Thread Starter
  • #12
I dont understand how it's works.
My first action turn off firewall on all servers (1.sccm 2. sql 3.wsus)
then, two days later, I sequentially turned on the firewall on one server of the queue, starting from the first and ending with the last. I expected to see service crashes , but I didn 't see any errors in the site status or in the component status.
as a result, the errors that were previously gone
Last edited: