I am totally stuck with my SCCM 2007 R3 server. Every few days my server is locked and when i try to unlock with my domain user it fails and i found my domain disappeared from the log on to menu and only This Computer xxx option is available "as Local Administrator". To resolve this i have to force restart through VMWare console. Now when i log on after restart i find the following error: szAppName : smsexec.exe szAppVer : 4.0.6487.2000 szModName : mfc80.dll szModVer : 8.0.50727.762 offset : 00022df3 C:\DOCUME~1\SCCMAD~1\LOCALS~1\Temp\1\WER1e09.dir00\smsexec.exe.mdmp C:\DOCUME~1\SCCMAD~1\LOCALS~1\Temp\1\WER1e09.dir00\appcompat.txt and in the event log i found the following: faulting application smsexec.exe, version 4.0.6487.2000, faulting module mfc80.dll, version 8.0.50727.762, fault address 0x00022df3. Windows cannot determine the user or computer name. (The specified component could not be found in the configuration information. ). Group Policy processing aborted. On 8/16/2012 6:46:43 AM, component SMS_MP_CONTROL_MANAGER on computer SCCM reported: MP Control Manager detected DMP is not responding to HTTP requests. The http status code and text is 503, Service Unavailable. Possible cause: DMP encountered an error when connecting to SQL Server. Solution: Verify that the SQL server is properly configured to allow Device Management Point access. If using a standard SQL security account, verify that the SQL Server is configured to allow standard SQL Security; or configure the Device Management Point to use an NT integrated security account, with appropriate access. If using integrated security, verify the account used by the DMP to connect to the SQL server is a member of the SMS_SiteSystemToSQLConnection_<sitecode> group on the SQL server, that the account is not locked out, and that the account password is not expired. (In standard security, the default account is SMS_SQL_RX_<sitecode>.) Possible cause: The SQL server Service Principal Names (SPNs) are not registered correctly in Active Directory Solution: Ensure SQL server SPNs are correctly registered. Review Q829868. Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which SMS is configured to communicate. Solution: Verify that the designated Web Site is configured to use the same ports which SMS is configured to use. Possible cause: The designated Web Site is disabled in IIS. Solution: Verify that the designated Web Site is enabled, and functioning properly. Possible cause: The SMS ISAPI Application Identity does not have the requisite logon privileges. Solution: Verify that the account that the SMS ISAPI is configured to run under has not been denied batch logon rights through group policy. For more information, refer to Microsoft Knowledge Base article 838891. For more information, see Help and Support Center at SMS_COMPONENT_STATUS_SUMMARIZER on computer SCCM reported: SMS Component Status Summarizer set the status of component "SMS_PXE_SERVICE_POINT", running on computer "SCCM", to Critical. Possible cause: The component is experiencing a problem. Solution: Diagnose and fix the problem by: 1. Examining the status messages that the component reports. 2. Correcting the problem. 3. Instructing SMS Component Status Summarizer to reset the counts of Error, Warning, and/or Informational status messages reported by the component. To reset the counts, right-click Reset Counts on the component in the Component Status summary in the SMS Administrator console. When the counts are reset, SMS Component Status Summarizer will change the status of the component to OK. This might take some time if site "GDI" is a child site. 4. Delete any unwanted status messages from the SMS site database, if necessary. 5. Monitor the component occasionally to verify that the problem does not reoccur. Possible cause: The component is OK and you were unnecessarily alerted because the Component Status Thresholds are set too low for the component. Solution: Increase the Component Status Thresholds for the component using the Thresholds tab of the Component Status Summarizer Properties dialog box in the SMS Administrator console. Possible cause: The component is flooding the status system by rapidly reporting the same message repeatedly. Solution: Diagnose and control the flood of status messages by: 1. Verifying that the component is actually flooding the status system. View the status messages reported by the component and verify that the same message is continually reported every several minutes or seconds. 2. Noting the Message ID of the flooded status message. 3. Creating a Status Filter Rule for site "GDI" that instructs Status Manager to discard the flooded status message when component "SMS_PXE_SERVICE_POINT" on computer "SCCM" reports it. 4. Verifying that your sites' databases were not filled up by the flooded status message. Delete any duplicate status messages from the site database, if necessary. 5. Refer to the Microsoft Knowledge Base for further troubleshooting information. For more information, see Help and Support Center at The time service encountered an error and was forced to shut down. The error was: 0xC002001B The time provider NtpClient cannot determine whether the response received from GDIPDC01.gdi.com.qa has a valid signature. The response will be ignored. The error was: Not enough server storage is available to process this command. (0x8007046A) The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {1A9FFCE9-10C1-40BC-9815-B20C1DC2D156} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19). This security permission can be modified using the Component Services administrative tool. Application pool 'CCM Windows Auth Server Framework Pool' is being automatically disabled due to a series of failures in the process(es) serving that application pool. The World Wide Web Publishing Service encountered an internal error in its process management of worker process '0' serving application pool 'CCM Windows Auth Server Framework Pool'. The data field contains the error number. Application pool 'DefaultAppPool' is being automatically disabled due to a series of failures in the process(es) serving that application pool. I review all the possible causes with no success. connected to computer management from another PC and in services i found smsexec.exe is stopped also windows time but i couldn't start the windows time service as the following error appears: not enough server storage is available to process this command. Also tried to remotely restart through task schedule and got the following error: The RPC server is unavailable. I need help urgently. Thanks

All of the errors above are symptoms of some other root cause. Have you checked the performance of your system? A few of the errors above seem to indicate it being overwhelmed. Have you applied any post SP2 hotfixes? There are quite a few and more than a couple are very important to install to resolve memory leak issues: http://social.technet.microsoft.com/wiki/contents/articles/4505.list-of-public-kb-articles-and-hotfixes-for-configuration-manager-2007-sp2-en-us.aspxJason | http://blog.configmgrftw.com

Thanks Jason for you quick response, actually the system performance is ok, also i didn't apply any post SP2 hotfix. The computer lockout is happening before applying SP2. I don't know what causes the computer to forget my domain as when i force restart it remembers again. I think the smsexec.exe error happens before the computer lockout as well as the windows time error. This is the main issue i am facing, i think other issues can be handled.Hussien Sherief