Welcome to MicrosoftTechEd

Last week i was upgrading one my ConfigMgr site to SP2, in between i got an error.

“SMS Site Component Manager cannot stop component SMS_CLIENT_CONFIG_MANAGER on Component server  <server name>.The component is probably performing clean up tasks which could take a while, clicking ignore will terminate the component and anything that it’s doing.”

I did “retry” once and observed for a some more min. but again i have got the same error. I don’t want abort or ignore in the middle of the upgrade. I just stop the SMS_COMPONENT_MANAGER service for a while restarted again and then clicked on “retry”. Guess !!! upgraded started. If you faced the same problem then you may try this.However this is not documented in any Microsoft site.

Thanks and Regards |Abhishek Joshi |www.AbhishekJoshi.com

Incoming search terms:

• sccm component status summarizer replication troubleshooting (1)
• statmsg id 5202 5203 mean (1)
• stop the SMS_CLIENT_CONFIG_MANAGER component (1)

Last month one of our stake holder facing problem while running SCCM report . He was facing error 500 in internet explorer. when checked the IIS logs find below error is appearing

After searching on the web, found SMS 2003 Faq’s http://technet.microsoft.com/en-us/library/cc875797.aspx . However, our servers are installed with SCCM 2007 and IE7. After going through the SMS 2003 FAQ and http://learn.iis.net/page.aspx/373/editing-configuration-files/ we were able to solve the problem. Below are the steps.

Resolution Steps:

1) Open the latest IIS log file using SMS trace utility and filter it by “buffer” (filter by “contains”). You will see error logs as below. You can find the report ID number.

2) Run the report in Internet Explorer and observe whether same error entry is appearing in the IIS logs or not.

3) If yes, go to that report in SMS console, and take the SQL query for that report. Then run the query on the SMS database and check for how many rows it returned?

4) You need to adjust a registry value on the SMS Reporting Point to allow the return of a larger row set. To do that, go to HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Reporting Add a DWORD value Rowcount and assign it a value for the desired maximum limit, the maximum row count is 32767 (decimal) But if you need to return more, then set it to 0xffffffff (Hex). This will return all rows but will significantly increase the workload on your site server database. It is not recommend doing this until it is critical to do these settings.

5) Open console of IIS manager 7.0

6) Select server Name.

7) On the right pane, right click on ASP and click on Open feature

8 ) Change the value of “response buffering time-out”. To decide upon “response buffering time-out “ please check how many maximum rows we expect from the report and based on that do math 1 MB per 1000 records. However, it’s ideal. After changing the value if error is still appearing in IIS logs. Please calculate the “response buffering time-out” value by doing math of 2MB per 500 Records.

9) Change “Script Timeout” value to 180 sec.  The default is 90.

10 ) Run the report

Thank and Regards |Abhishek Joshi| www.AbhishekJoshi.com

Incoming search terms:

• sccm launch reports console (1)

what if you are getting following warning message in SMS_Status_Manager Component with Message ID 1215?

SMS Status Manager received a status message reported by component "Advanced Client" running on computer "<server name >", and the time stamp on the message is more recent than the current system time on the site server.

Possible cause: The system clock on computer "<server name>" is 32192 or more seconds ahead of the site server’s system clock.

Solution: Synchronize the system clock of computer "<server name>" with the site server’s system clock. Please refer to your Windows NT Server documentation or the Microsoft Knowledge Base for further information.

SMS Status Manager will process status messages with improper time stamps when the site server’s system clock surpasses the improper time stamps. For example, this status message will not be processed for 32192 seconds. SMS Status Manager will continue to report this problem every 24 hours until you fix it. SMS Status Manager will not report this problem if the system clock of computer "<server name >" is less than 300 seconds ahead of the site server’s system clock. This interval is configurable in the SMS site control file. Please refer to the Microsoft Knowledge Base for further information.

Please follow the steps below

1) Go to status filter rule.

2) Create the rule as given below in the figures below

Note:- This behavior only occurs when the computer is using this particular runtime library when the transition date (the day we change to Daylight Saving Time) falls on the first day of the month. For more details please go through  http://support.microsoft.com/kb/295450

Thanks and Regards |Abhishek Joshi |www.AbhishekJoshi.com

Incoming search terms:

• sccm status message interval (1)

Some of the systems were not scan for ITMU, when I have checked the subnets for these systems, I have clicked that It has been assosciated with the new distribution point. I went through DataTransferService.log, for 2 to 3 systems and I got a way towards accomplishment. The log was totally full of errors(As shown below).

I went to distribution point server, navigate to SMS_DP_SMS PKGD$ in the IIS and browse it. Though browsing was enable, but still it wasn’t. When I have gone through security events on DP server, there were lot of failed logons from the systems which were not able to scan for ITMU. That’s it! I have done following steps and it solved my problem.

1) Navigate to SMS_DP_SMSPKGD$ in IIS.

2) Right click, go to properties

3) Open a directory security tab and Edit the " Authentication and access control" 

4) It will open below window. I have just check " Integrated Windows authentication" and click ok.

Thanks and Regards |Abhishek Joshi |www.AbhishekJoshi.com

Incoming search terms:

• error sending dav request http code 401 status \unauthorized\ (1)

If MPControl.log file throwing error “http verification .sms_aut (<Port number>) failed with status code 503, service unavailable” then check for your IIS application pool. SMS management point pool and CCM server framework pool might have stopped.

For resolution please check site server’s for Netlogon service is stopped or not.

Note: – After installing June 08 patches Netlogon service was stopped on some of the SMS secondary site which causes proxy management point stops working. Starting of Netlogon service solved our problem.

Thanks and Regards |Abhishek Joshi |www.AbhishekJoshi.com

Incoming search terms:

• SCCM 503 Service Unavailable (1)