Hello,I'm trying to install System Center Configuration Manager 2007 on Windows Server 2003 SP2.It is a testing server with a Pentium 4 3 GHz and 4 GB memory.I'm connecting to the server with RDP an first installed Microsoft SQL server 2005 and Service Pack 2 for SQL 2005.After SQL installation, i start the installation of SCCM. This installation gives a warning that i have to install some updates.After installation of this updates, i started SCCM installation with an RDP connection.The installations fails. Can someone help me please. Here is the last part of the log file. As you can see, it fails with an time-out.<12-03-2008 16:12:03> Installation is done and configuring site components are still going.<12-03-2008 17:07:26> Timed out monitoring.<12-03-2008 17:07:26> End monitoring - SMS_SITE_COMPONENT_MANAGER.<12-03-2008 17:07:26> Begin monitoring - SMS_COMPONENT_MONITOR.<12-03-2008 17:07:26> MonitorComponent: failed to initialize COpsMgmtComponent object.<12-03-2008 17:07:26> Failed to complete monitoring.<12-03-2008 17:07:26> End monitoring - SMS_COMPONENT_MONITOR.<12-03-2008 17:07:26> Begin monitoring - SMS Management Point.<12-03-2008 17:07:26> MonitorServerRole: failed to get availability state, error = 0x80070005.<12-03-2008 17:07:26> Failed to complete monitoring.<12-03-2008 17:07:26> End monitoring - SMS Management Point.<12-03-2008 17:07:26> Completed monitoring installation of Configuration Manager services.<12-03-2008 17:07:26> Some core services may not be available.<12-03-2008 17:07:26> Enabling Next button.

Have you used a domain accounts that's also a local admin for installating ConfigMgr? Can you start the ConfigMgr admin console? If so: have a look at system status -> site status to see what's going on.

I started the installation as Administrator. Administrator is a member of Domain Admins. Domain Admins group is member of the local Administrators group.I have started the Configuration manager console and made a screenshot.Take a look here: http://img201.imageshack.us/img201/6985/sccmerrordl0.jpg

That doesn't help very much. You should have a look at the ConfigMgr logs to see what's going on. http://technet.microsoft.com/en-us/library/bb892800.aspx

Oke, i have found a log file called sitecomp.logA lot of error rules in this file:******************************************************************************* $$<SMS_SITE_COMPONENT_MANAGER><Thu Dec 04 09:46:04.116 2008 W. Europe Standard Time><thread=1940 (0x794)>SMS_SITE_COMPONENT_MANAGER service is starting... $$<SMS_SITE_COMPONENT_MANAGER><Thu Dec 04 09:46:04.116 2008 W. Europe Standard Time><thread=1940 (0x794)>Microsoft System Center Configuration Manager v4.00 (Build 6221) $$<SMS_SITE_COMPONENT_MANAGER><Thu Dec 04 09:46:04.116 2008 W. Europe Standard Time><thread=1940 (0x794)>Copyright (C) 2005 Microsoft Corp. $$<SMS_SITE_COMPONENT_MANAGER><Thu Dec 04 09:46:04.116 2008 W. Europe Standard Time><thread=1940 (0x794)>Running as a Win32 service. $$<SMS_SITE_COMPONENT_MANAGER><Thu Dec 04 09:46:04.116 2008 W. Europe Standard Time><thread=1940 (0x794)>Process ID: 3724 $$<SMS_SITE_COMPONENT_MANAGER><Thu Dec 04 09:46:04.116 2008 W. Europe Standard Time><thread=1940 (0x794)>Worker thread ID: 1940 $$<SMS_SITE_COMPONENT_MANAGER><Thu Dec 04 09:46:04.116 2008 W. Europe Standard Time><thread=1940 (0x794)>Initializing the status message reporting system... $$<SMS_SITE_COMPONENT_MANAGER><Thu Dec 04 09:46:04.116 2008 W. Europe Standard Time><thread=1940 (0x794)> The path to the "Status Manager" inbox is "C:\Program Files\Microsoft Configuration Manager\inboxes\statmgr.box\statmsgs". $$<SMS_SITE_COMPONENT_MANAGER><Thu Dec 04 09:46:04.116 2008 W. Europe Standard Time><thread=1940 (0x794)> SMS_STATUS_MANAGER is not running as part of this process, the SMS_EXECUTIVE to SMS_STATUS_MANAGER in-memory status message queue will not be used. $$<SMS_SITE_COMPONENT_MANAGER><Thu Dec 04 09:46:04.116 2008 W. Europe Standard Time><thread=1940 (0x794)>CStatusModule::Initialize(): ERROR: Could not register this process as a source of "SMS Server" events, Win32 LoadLibrary("C:\WINDOWS\system32\smsmsgs\srvmsgs.dll") returned error 193: $$<SMS_SITE_COMPONENT_MANAGER><Thu Dec 04 09:46:04.163 2008 W. Europe Standard Time><thread=1940 (0x794)> Sleeping for 60 seconds. $$<SMS_SITE_COMPONENT_MANAGER><Thu Dec 04 09:46:04.163 2008 W. Europe Standard Time><thread=1940 (0x794)>CStatusModule::Initialize(): ERROR: Could not register this process as a source of "SMS Server" events, Win32 LoadLibrary("C:\WINDOWS\system32\smsmsgs\srvmsgs.dll") returned error 193: $$<SMS_SITE_COMPONENT_MANAGER><Thu Dec 04 09:47:04.238 2008 W. Europe Standard Time><thread=1940 (0x794)> Sleeping for 60 seconds. $$<SMS_SITE_COMPONENT_MANAGER><Thu Dec 04 09:47:04.238 2008 W. Europe Standard Time><thread=1940 (0x794)>CStatusModule::Initialize(): ERROR: Could not register this process as a source of "SMS Server" events, Win32 LoadLibrary("C:\WINDOWS\system32\smsmsgs\srvmsgs.dll") returned error 193: $$<SMS_SITE_COMPONENT_MANAGER><Thu Dec 04 09:48:04.236 2008 W. Europe Standard Time><thread=1940 (0x794)> Sleeping for 60 seconds. $$<SMS_SITE_COMPONENT_MANAGER><Thu Dec 04 09:48:04.236 2008 W. Europe Standard Time><thread=1940 (0x794)>CStatusModule::Initialize(): ERROR: Could not register this process as a source of "SMS Server" events, Win32 LoadLibrary("C:\WINDOWS\system32\smsmsgs\srvmsgs.dll") returned error 193: $$<SMS_SITE_COMPONENT_MANAGER><Thu Dec 04 09:49:04.235 2008 W. Europe Standard Time><thread=1940 (0x794)> Sleeping for 60 seconds. $$<SMS_SITE_COMPONENT_MANAGER><Thu Dec 04 09:49:04.235 2008 W. Europe Standard Time><thread=1940 (0x794)>CStatusModule::Initialize(): ERROR: Could not register this process as a source of "SMS Server" events, Win32 LoadLibrary("C:\WINDOWS\system32\smsmsgs\srvmsgs.dll") returned error 193: $$<SMS_SITE_COMPONENT_MANAGER><Thu Dec 04 09:50:04.233 2008 W. Europe Standard Time><thread=1940 (0x794)> Sleeping for 60 seconds. $$<SMS_SITE_COMPONENT_MANAGER><Thu Dec 04 09:50:04.233 2008 W. Europe Standard Time><thread=1940 (0x794)>CStatusModule::Initialize(): ERROR: Could not register this process as a source of "SMS Server" events, Win32 LoadLibrary("C:\WINDOWS\system32\smsmsgs\srvmsgs.dll") returned error 193: $$<SMS_SITE_COMPONENT_MANAGER><Thu Dec 04 09:51:04.232 2008 W. Europe Standard Time><thread=1940 (0x794)> Sleeping for 60 seconds. $$<SMS_SITE_COMPONENT_MANAGER><Thu Dec 04 09:51:04.232 2008 W. Europe Standard Time><thread=1940 (0x794)>CStatusModule::Initialize(): ERROR: Could not register this process as a source of "SMS Server" events, Win32 LoadLibrary("C:\WINDOWS\system32\smsmsgs\srvmsgs.dll") returned error 193: $$<SMS_SITE_COMPONENT_MANAGER><Thu Dec 04 09:52:04.231 2008 W. Europe Standard Time><thread=1940 (0x794)> Sleeping for 60 seconds. $$<SMS_SITE_COMPONENT_MANAGER><Thu Dec 04 09:52:04.231 2008 W. Europe Standard Time><thread=1940 (0x794)>CStatusModule::Initialize(): ERROR: Could not register this process as a source of "SMS Server" events, Win32 LoadLibrary("C:\WINDOWS\system32\smsmsgs\srvmsgs.dll") returned error 193: $$<SMS_SITE_COMPONENT_MANAGER><Thu Dec 04 09:53:04.230 2008 W. Europe Standard Time><thread=1940 (0x794)> Sleeping for 60 seconds. $$<SMS_SITE_COMPONENT_MANAGER><Thu Dec 04 09:53:04.230 2008 W. Europe Standard Time><thread=1940 (0x794)>

I would check those things : 1) check you have fqdn name for the sql service registered . http://poseidom.wordpress.com/2007/12/16/set-spn-for-sql-2005-sccm-remote-sql-fix/2) make sure the account that is running the sccm have sysadmin rights on the sql db 3) add the sccm computer account as administrator on the sql server

SQL Server 2005 SP2 is installed on the same computer. i chose simple setup. The setup automaticly detects the local SQL server.How can i check the sysadmin rights on the sql database?

go to your SQL Server Management Studio ( you should have it under all programs ) . Once inside the sql manager go to Security-->logins Right click and add a new login or modify your login you already have and on the left cullom choose "server rools" the make sure sysadmin box is checked . and add the account .. And i would rethink about putting the SCCM , MP,DP and the SQL on the same box .... unless you have only a handful of users i would seperate them

You don't have to change anything under 'Logins' if ConfigMgr and SQL are on the same box.

SCCM and SQL are on the same server. It is for testing purposes only.Today, i tried to instal SCCM 3 times. Also did a clean Windows server 2003 install. The problem still exists.Tomorrow i try installing Windows Server 2008. Hope this "fix" my problem. If that works, i will post it here

Maarten Brand wrote: Tomorrow i try installing Windows Server 2008. Hope this "fix" my problem. If that works, i will post it here Make sure to follow http://technet.microsoft.com/en-us/library/cc431377.aspxexactly!

Oke. This weekend i tried to install SCCM on Windows Server 2008.The installation failed with the same error!The file sitecomp.log says:CStatusModule::Initialize(): ERROR: Could not register this process as a source of "SMS Server" events, Win32 LoadLibrary("C:\Windows\system32\smsmsgs\srvmsgs.dll") returned error 193: $$<SMS_SITE_COMPONENT_MANAGER><Mon Dec 08 09:31:19.804 2008 W. Europe Standard Time><thread=4776 (0x12A8)> Sleeping for 60 seconds. $$<SMS_SITE_COMPONENT_MANAGER><Mon Dec 08 09:31:19.804 2008 W. Europe Standard Time><thread=4776 (0x12A8)>Edit:I did some research on the srvmsgs.dll file. This file is copied to C:\Windows\System32\smsmsgsIn this directory there is also an file: srvmsgs.cmd When i edit this file, it is empty? Also on the orginal CD, the file is empty. Is this normal?I also tried to register the regsvr.dll file with regsvr32. That gives me an error that the file is nog a valid x86 of x64 file?Maybe it is a problem with the disc? It is an ISO file, downloaded from MSDN!Please help me!

Maarten Brand wrote: I did some research on the srvmsgs.dll file. This file is copied to C:\Windows\System32\smsmsgs In this directory there is also an file: srvmsgs.cmd When i edit this file, it is empty? Also on the orginal CD, the file is empty. Is this normal? You should download the DVD again. That .cmd is NOT empty.

Problem solved. Downloaded a new ISO of SCCM from MSDN. Now the installation was successful!

Problem solved. Downloaded a new ISO of SCCM from MSDN. Now the installation was successful! me tooMike Crowley: MCT, MCSE, MCTS, MCITP: Enterprise Administrator / Messaging Administrator

I came across this problem on a few of thenewly built 2008 R2 Servers we have here. It has taken a few weeks to resolve, however this is how I did it. The install hangs early as it is waiting on WMI to stop. Why WMI hangs I am unsure, maybe it is due to the IBM monitoring software on the server. So I ran sc queryex and grabbed the PID for Windows management Instrumentation, and killed the process. This allow the install to continue further. Installation done and site configuration components are still going. I noticed that the default shares SMS_SITE and SMS_XXX hadn't been created. The SMS_SITE_COMPONENT_MANAGER service was installed but not started. I started it, then it stopped again. So I manually created the missing Shares. I then started SMS_SITE COMPONENT_MANAGER again and to my absolute amazement the installation continued. This has taken weeks to figure out. I hope it helps someone else. Cheers