none
ERROR in two components (SMS_INVENTORY_DATA_LOADER, SMS_MP_CONTROL_MANAGER)

    Question

  • Hi all,

    I got below errors in SCCM primary site.

    1) Component: SMS_INVENTORY_DATA_LOADER
    Message ID: 599
    Description: SQL Login data is incomplete

    2) Component: SMS_MP_CONTROL_MANAGER
    Message ID: 5436
    Description: MP Control Manager detected management point is not responding to HTTP requests. The HTTP status code and text is 500. Internal Server Error.

    3) Component: SMS_MP_CONTROL_MANAGER
    Message ID: 5420
    Description: SMS management point encountered an error when connecting to the database XXX on SQL Server YYY. The OLEDB error code was 0x80004005.


    Please advice how to solve those problems. Thanks!
    Friday, November 27, 2009 7:30 AM

Answers

  • Hi Gloria,

    Could you please try the following steps:

    1.. Run  http://<MP name>/sms_mp/.sms_aut?mplist
      1.. This returns a blank screen.
    2.. Run  http://<MP name>/sms_mp/.sms_aut?mpcert
      1.. This returns a long list of numbers and letters.
    3.. Verify that the DTS Service is enabled.
    4.. Verify that the Task Scheduler is enabled.
    5.. Verify that the Windows Management Instrumentation service is running.
    6.. Verify that the SMS Agent Host service is running.
    7.. Verify that the World Wide Web Publishing Service is running.
    8.. Verify that the MP machine account has been added to the
    SMS_SiteSystemToSQLConnection_<site_code> group.
    9.. Verify that the SQL Server has named pipes enabled.
    10.. Update MDAC on the server.
      1.. Review Q820910 for details.
      2.. http://support.microsoft.com/default.aspx?scid=kb;en-us;820910
    11.. SQL boxes that are running under a user account, instead of system,
    need the SPN updated in AD.
      1.. Review Q829868 for additional details.
      2.. http://support.microsoft.com/default.aspx?scid=kb;en-us;829868
    12.. Crossing domain boundaries between MP and SQL may also need the SPN
    updated in AD.
      1.. Review Q829868 for additional details.
      2.. http://support.microsoft.com/default.aspx?scid=kb;en-us;829868
    13.. IIS Lockdown Tool
      1.. If you are using the IIS lockdown tool on your IIS 5 servers be sure
    to apply the SMS server template from the SMS 2003 toolkit.
      2.. http://www.microsoft.com/smserver/downloads/2003/tools/toolkit.asp
    14.. Deinstall the MP and IIS, then reinstall IIS and the MP.
      1.. Remove the MP role on the server.
      2.. Disable IIS. Remove completely. Reboot the server.
      3.. Verify that the DTS Service is enabled.
      4.. Verify that the Task Scheduler is enabled.
      5.. Verify that the Windows Management Instrumentation service is
    running.
      6.. Enable BITS, enable WEBDEV and install IIS.
      7.. Verify that the World Wide Web Publishing Service is running.
      8.. Verify that the MP machine account has been added to the
    SMS_SiteSystemToSQLConnection_<site_code> group.
      9.. Enable MP role on the server.
    This will fix most MP errors. I personally would start with step 11. But please check all .
    • Marked as answer by Eric Zhang CHN Wednesday, December 02, 2009 10:25 AM
    Friday, November 27, 2009 9:41 AM

All replies

  • Hi,

    Check the dataldr.log file on the site server to investigate errors related to the SQL connection. Also run http://siteservername/SMS_MP/.sms_aut?MPLIST from a browser where siteservername is the name of your server. If this returns an error then your MP is not working.
    Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products
    Friday, November 27, 2009 7:39 AM
    Moderator
  • Hi,

     


    I found "Cannot decrypt SQL server login password" and "CInvDataLoader::GetConfigurationInformation - failed" in the latest dataldr.log.

     

    When I ran http://siteservername/SMS_MP/.sms_aut?MPLIST , it turned a page with below content.

    <MPList>

    - <MP Name="XXX" FQDN="YYY">

      <Version>6221</Version>

      <Capabilities SchemaVersion="1.0" />

      </MP>

      </MPList>

     

    Is the alright, any idea what's the problem here? Thanks!

     

    Friday, November 27, 2009 7:58 AM
  • Hi Gloria,

    Could you please try the following steps:

    1.. Run  http://<MP name>/sms_mp/.sms_aut?mplist
      1.. This returns a blank screen.
    2.. Run  http://<MP name>/sms_mp/.sms_aut?mpcert
      1.. This returns a long list of numbers and letters.
    3.. Verify that the DTS Service is enabled.
    4.. Verify that the Task Scheduler is enabled.
    5.. Verify that the Windows Management Instrumentation service is running.
    6.. Verify that the SMS Agent Host service is running.
    7.. Verify that the World Wide Web Publishing Service is running.
    8.. Verify that the MP machine account has been added to the
    SMS_SiteSystemToSQLConnection_<site_code> group.
    9.. Verify that the SQL Server has named pipes enabled.
    10.. Update MDAC on the server.
      1.. Review Q820910 for details.
      2.. http://support.microsoft.com/default.aspx?scid=kb;en-us;820910
    11.. SQL boxes that are running under a user account, instead of system,
    need the SPN updated in AD.
      1.. Review Q829868 for additional details.
      2.. http://support.microsoft.com/default.aspx?scid=kb;en-us;829868
    12.. Crossing domain boundaries between MP and SQL may also need the SPN
    updated in AD.
      1.. Review Q829868 for additional details.
      2.. http://support.microsoft.com/default.aspx?scid=kb;en-us;829868
    13.. IIS Lockdown Tool
      1.. If you are using the IIS lockdown tool on your IIS 5 servers be sure
    to apply the SMS server template from the SMS 2003 toolkit.
      2.. http://www.microsoft.com/smserver/downloads/2003/tools/toolkit.asp
    14.. Deinstall the MP and IIS, then reinstall IIS and the MP.
      1.. Remove the MP role on the server.
      2.. Disable IIS. Remove completely. Reboot the server.
      3.. Verify that the DTS Service is enabled.
      4.. Verify that the Task Scheduler is enabled.
      5.. Verify that the Windows Management Instrumentation service is
    running.
      6.. Enable BITS, enable WEBDEV and install IIS.
      7.. Verify that the World Wide Web Publishing Service is running.
      8.. Verify that the MP machine account has been added to the
    SMS_SiteSystemToSQLConnection_<site_code> group.
      9.. Enable MP role on the server.
    This will fix most MP errors. I personally would start with step 11. But please check all .
    • Marked as answer by Eric Zhang CHN Wednesday, December 02, 2009 10:25 AM
    Friday, November 27, 2009 9:41 AM
  • Hi,

     


    I found "Cannot decrypt SQL server login password" and "CInvDataLoader::GetConfigurationInformation - failed" in the latest dataldr.log.

     

    When I ran http://siteservername/SMS_MP/.sms_aut?MPLIST , it turned a page with below content.

    <MPList>

    - <MP Name="XXX" FQDN="YYY">

      <Version>6221</Version>

      <Capabilities SchemaVersion="1.0" />

      </MP>

      </MPList>

     

    Is the alright, any idea what's the problem here? Thanks!

     



    I'm getting the same error message as you are after installing SCCM 2007 SP2.  Did you find a fix?
    Wednesday, December 02, 2009 5:23 PM