Does anyone know how to fix this??
- From: "Baruch Ortiz" <baruchnews@xxxxxxxxxxx>
- Date: Mon, 12 Sep 2005 11:19:27 -0500
Hi to everyone....
I've 8 secondary servers but only 4 are giving me the same error, I
fixed any possible cause of error, but it still appearing, so I went to
Microsoft Support page, but I can't see any article of this problem....
Basically sms secondary site reports me 3 kind of error....
1.- "Systems Management Server cannot update the already existing object
"cn=SMS-MP-QAJ-QAJUSSMS1" in Active Directory.
Possible cause: This site's SMS Service account or the site server's machine
account may not have full control rights for the "System Management"
container in Active Directory
Solution: Give the site's SMS Service account full control rights to the
"System Management" container, and all child objects in Active Directory.
Possible cause: The Active Directory object "cn=SMS-MP-QAJ-QAJUSSMS1" has
been moved to a location outside of the "System Management" container, or
has been lost.
Solution: Delete the object from its current location, and let SMS create a
new object.
Possible cause: The Active Directory schema has not been extended with the
correct SMS Active Directory classes and attributes.
Solution: Turn off Active Directory publishing for each site in the forest,
until the schema can be extended. The schema can be extended with the tool
"extadsch.exe" from the SMS CD."
(The machine account has full control in system management folder and is
Extended the Schema)
2.- "MP Control Manager detected MP is not responding to HTTP requests. The
http error is Internal Server Error.
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.
For more information, refer to Microsoft Knowledge Base article 838891."
(I verified every posibility in this error and it still appearing)
3.- "The SMS Service Host (CCMEXEC) was unable to update certificate
information in the Active Directory."
(spetially in this error never found an article of this error in KB)
.
- Follow-Ups:
- Re: Does anyone know how to fix this??
- From: Baruch Ortiz
- Re: Does anyone know how to fix this??
- Prev by Date: SQL CAL for the SQL server that has SMS
- Next by Date: Re: SQL2000-SP4
- Previous by thread: SQL CAL for the SQL server that has SMS
- Next by thread: Re: Does anyone know how to fix this??
- Index(es):
Relevant Pages
|
