Re: SMS Component errors after installing SP2
- From: Cybernijntje <Cybernijntje@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 8 Aug 2006 07:31:02 -0700
Thnx for the reply. We contacted MS for this problem and they helped us
resolve our problems.
Here's the MS answer (perhaps this might help anyone):
1. Latest MP control manager shows that the MP is working fine.
SMS_MP_CONTROL_MANAGER successfully STARTED.
SMS_MP_CONTROL_MANAGER 8/2/2006 10:33:17 AM 4776 (0x12A8)
********************************************************************************
SMS_MP_CONTROL_MANAGER 8/2/2006 10:33:17 AM 4776
(0x12A8)
Http verification .sms_aut (port 80) succeeded with status code 200, OK
SMS_MP_CONTROL_MANAGER 8/2/2006 10:45:06 AM 4828 (0x12DC)
Http verification .sms_aut (port 80) succeeded with status code 200, OK
SMS_MP_CONTROL_MANAGER 8/2/2006 10:55:19 AM 4828 (0x12DC)
Http verification .sms_aut (port 80) succeeded with status code 200, OK
SMS_MP_CONTROL_MANAGER 8/2/2006 11:05:19 AM 4828 (0x12DC)
2. Also the sitecomp.log shows that the componet SMS_SQL_MONITOR is running
now.
Component SMS_SQL_MONITOR is running.SMS_SITE_COMPONENT_MANAGER
8/2/2006 10:33:15 AM 2788 (0x0AE4)
3.You can ignore the SMS_MP_DEVICE_MANAGER , it meant for the mobile clients
and it is also a virtual component.
4. Regarding the failure of MP setup,
MPsetup.log have the following entry at 13:00 yesterday.
<08-01-2006 13:03:45> [13:03:45] @@ERR:25006
<08-01-2006 13:03:45> Setup was unable to create the Internet virtual
directory CCM_Incoming
The error code is 80020009
<08-01-2006 13:04:19> MP.MSI exited with return code: 1603
<08-01-2006 13:04:19> Backing up MPMSI.log to D:\SMS\logs\MPMSI.log.LastError
<08-01-2006 13:04:19> Fatal MSI Error - MP.MSI could not be installed.
Later when it tried the MPsetup once again it succeeded with out any error,
<08-01-2006 13:04:38> Management Point already installed (Product Code:
{A61F02C7-CE80-4941-8E5D-900804DAF6DE}). Upgrading/Reinstalling MP
<08-01-2006 13:04:38> New Management Point is a new product code
{{391CC246-8659-4973-ABAC-DB4654431DF9}}. This is a major upgrade.
<08-01-2006 13:04:38> Enabling MSI logging. MP.MSI will log to
D:\SMS\logs\MPMSI.log
<08-01-2006 13:04:38> Installing D:\SMS\bin\i386\mp.msi REINSTALLMODE=vmaus
CCMINSTALLDIR="D:\SMS_CCM" CCMSERVERDATAROOT="D:\SMS" USESMSPORTS=TRUE
SMSPORTS=80 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000
CCMLOGMAXHISTORY=1
<08-01-2006 13:09:07> MP.MSI exited with return code: 0
<08-01-2006 13:09:07> Installation was successful.
There is one KB that talk about the same error,
http://support.microsoft.com/default.aspx?scid=kb;EN-US;317872
It is explained that “This problem may occur if the removal of a previous
management point installation did not correctly clean up all the Web service
extension file names in the Metabase.xml file.”
So what I say on this is that, when the installation tried for the first
time, the old MP clean was not completed fully, when it tried again, it
succeeded.
Best regards,
Dennis
"Kim Oppalfens <MVP>" wrote:
To solve 2 you need to rerun the schema extension tool delivered with sms.
2003 sp 2.
http://support.microsoft.com/kb/829868/en-us
This could potentially solve 3 & 1.
--
Kim Oppalfens
Telindus Belgium
MVP Windows Server System - SMS
"Cybernijntje" <Cybernijntje@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:086976EC-DF97-418A-B322-31A99B8EFF6F@xxxxxxxxxxxxxxxx
Hi there,
After we installed SP2 this morning SMS 2003 keeps on giving the following
component errors:
1. SMS_MP_CONTROL_MANAGER (ID: 5436)
MP Control Manager detected MP is not responding to HTTP requests. The
http
error is 12152.
Possible cause: MP service is not started or not responding.
Solution: Manually restart the SMS Agent Host service on the MP.
Possible cause: IIS service is not responding.
Solution: Manually restart the W3SVC service on the MP.
Possible cause: MP encountered an error when connecting to SQL Server.
Solution: Verify that the SQL server is properly configured to allow
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 Management Point to use an NT integrated security account,
with
appropriate access. If using integrated security, verify the account
used
by the MP 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 Default Web Site is configured to use the same
ports which SMS is configured to use.
Possible cause: The Default Web Site is disabled in IIS.
Solution: Verify that the Default 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.
I've been searching this forum (and other sites) regarding
I've checked earlier posts (i.e. SMS_MP_Control_Manager Errors post), but
the guest account isn't listed. The only thing I noticed is that in the
site properties "Accounts" tab the SQL Server account is not defined? I'm
not sure if it was while we had SP1 (btw: SQL Authentication is SQL
Server and Windows).
2. SMS_SITE_COMPONENT_MANAGER (ID: 4918)
Systems Management Server cannot update the dNSHostName property for the
existing object "cn=SMS-MP-100-SSE0107" in Active Directory. This
property
is used to publish fully qualified host names in Active Directory.
Possible cause: The Active Directory schema has not been extended with
latest version of the SMS Active Directory classes and attributes.
Solution: Ensure the schema has been extended with the latest version of
the
SMS Active Directory classes and attributes. The schema can be extended
with
the tool "extadsch.exe" from the SMS directory on the SMS Site server that
reported this message.
We need to run extadsch.exe, but this can be done in the weekends only.
I'm listing this warning as well, because it might be connected to the
other errors?
3.SMS_SQL_MONITOR (ID:4959)
SMS Site Component Manager successfully installed this component. However
the SQL Server Principal Name (SPN) could not be validated in Active
Directory.
Possible cause: The MSSQL Service is running under a user account, instead
of the computer account. In this case, SQL does not publish its own SPN.
Solution: Manually publish the SQL SPN in Active Directory.
The component will operate correctly. However remote site systems
requiring access to SQL Server (i.e., server locator points, or
management
points) might not be able to access SQL in advanced security mode. Refer
to
your SMS documentation or the Microsoft Knowledge Base for further
information.
I honestly have NO clue?!
These are our errors. I've searched the web, but couldn't find a solution
(Q829868 is vague). Please don't flame me if someone posted a solution
earlier, my mind is blank right now :-(
Best regards,
Dennis van der Meijden
Air Traffic Control, the Netherlands
- References:
- SMS Component errors after installing SP2
- From: Cybernijntje
- SMS Component errors after installing SP2
- Prev by Date: Re: upgrade to SP2 client with new installation properties
- Next by Date: Re: Unattended Install
- Previous by thread: SMS Component errors after installing SP2
- Next by thread: SMS Client stops getting updates -- problems -- help!!
- Index(es):
Relevant Pages
|
