SMS_REPORTING_POINT

Problem viewing report using IE

An error occurred when the report was run. The details are as follows:
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
Error Number: -2147217843
Source: Microsoft OLE DB Provider for SQL Server
Native Error: 18456

Also in mpcontrol.log file
“Http verification .sms_aut (port 80) failed with status code 500, Internal Server Error”
End of the file…
Solution

http://support.microsoft.com/?id=832109

Run the command cliconfg on the site server make sure that namedpipe and tcpip are added.
Check all the settings and Restart the IIS server, SMS site component server

You need to run dcomcnfg.exe from the Site server.
Expand:
Computers
My Computer
DCOM Config

Locate the component:
SMS_REPORTING_POINT

Right-Click, select Properties, select Security

Customize and edit:

Launch and Activation Permissions
Configuration Permissions

Add the necessary user's.

SMS_SITE_COMPONENT_MANAGER

SMS Site Component Manager failed to reconfigure site system "\\" to receive SMS server components.

Solution: Review the previous status messages to determine the exact reason for the failure. SMS Site Component Manager cannot reinstall any SMS server components on this site system until the site system is reconfigured successfully. SMS Site Component Manager will automatically retry this operation in 60 minutes. To force SMS Site Component Manager to immediately retry this operation, stop and restart SMS Site Component Manager using the SMS Service Manager.

SOLUTION

Run the command cliconfg on the site server make sure that namedpipe and tcpip are added

SMS_MP_CONTROL_MANAGER

MP Control Manager detected MP is not responding to HTTP requests. The http error is Unauthorized.

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_ 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_.)

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.

SOLUTION

http://support.microsoft.com/?id=832109

Use cmd line “cliconfg” and make sure that you selected “Named Pipes” TCP/IP on “Enabled protocols by order:” box on right side of “General” tab.

Check “colleval.log and slpsetup.log” file.

Go to
1)
• Site Hierarchy  NYC-  site Settings  Site Systems

• Right click \\ go to properties

• Click Reporting Point” and make sure “use this site system as a reporting point” is checked.
2)
• make sure if your using advanced security that the MP machine account is in the SiteSystemToSQLServer connection group.

If you are in standard security, make sure that the account specified on the admin UI has rights to the SQL server (is a member of the SiteSystemToSQLserver connection group)
1. Click Start, point to Programs, point to Windows 2000 Support Tools, click Tools, and then click ADSI Edit.
2. Expand Domain NC, and then expand CN=Users.
3. Right-click the account that starts the SQL services, and then click Properties.
4. In the Properties dialog box, click ServicePrincipalName in the Select a property to view box, and verify that entries that are similar to the following entries exist:

FQDN SPN entry:
MSSQLSvc/sqlhost.mydomain.com:1433
NetBIOS SPN entry:
MSSQLSvc/sqlhost:1433