locked
Errors in logs: MSSCNTRS: Cannot get perf statistics on library SSO RRS feed

  • Question

  • I noticed the following errors in the WFE of our SharePoint 2007 SP2 farm. 

    SSO is disabled on all servers in the farm. 
    Incoming email is not enabled.   

    Any idea of what could be causing this?

    02/17/2011 21:38:03.25 	sharepoint.exe (0x2E80)         	0x2478	SharePoint Portal Server   	SSO              	0	High  	MSSCNTRS: Cannot get perf statistics on library SSO.	 
    02/17/2011 21:38:03.25 	sharepoint.exe (0x2E80)         	0x2478	SharePoint Portal Server   	SSO              	0	High  	Error code is: -2147418113	 
    Thursday, February 24, 2011 8:19 PM

All replies


  • check this one: http://social.technet.microsoft.com/Forums/en/sharepointgeneral/thread/4ef661ad-38a3-47a2-b6ad-19f092fd273f

    thanks

    -ws

     


    SharePoint administrator, MCTS,MCITP
    Thursday, February 24, 2011 8:29 PM

  • check this one: http://social.technet.microsoft.com/Forums/en/sharepointgeneral/thread/4ef661ad-38a3-47a2-b6ad-19f092fd273f

    thanks

    -ws

     


    SharePoint administrator, MCTS,MCITP


    I saw that post when I searched prior to posting my question.

    The service has been disabled and no SSO database exists in SQL Server.  I do not wish to enable SSO in my Production farm to get rid of these error messages.  There has to be another way?

    Thursday, February 24, 2011 8:57 PM
  • Thank you for the post but I already saw this and it doesn't resolve the problem.  It is another post like this one with one users suggestion to read about how to  enable SSO.  Not a solution but a how that doesn't address the problem.

    My ULS logs are also cluttered with the message:

    5/31/2011 12:29:42.31  wmiprvse.exe (0x085C)                    0x1074 SharePoint Portal Server       SSO                            0 High     MSSCNTRS: Cannot get perf statistics on library SSO. 
    05/31/2011 12:29:42.31  wmiprvse.exe (0x085C)                    0x1074 SharePoint Portal Server       SSO                            0 High     Error code is: -2147418113 
    05/31/2011 12:29:42.31  wmiprvse.exe (0x085C)                    0x1074 SharePoint Portal Server       SSO                            0 High     MSSCNTRS: Cannot get perf statistics on library SSO.

    It seems to me that some service is trying to use SSO so my question is how do I know what service is trying to use it so I can find out why?

    SSO is not enabled on my MOSS 2007 farm and I don't want it to be.   I cannot find an reference for the Error code  "-2147418113"  What does this error code mean?


    dms
    Tuesday, May 31, 2011 8:25 PM
  • Thank you for the post but I already saw this and it doesn't resolve the problem.  It is another post like this one with one users suggestion to read about how to  enable SSO.  Not a solution but a how that doesn't address the problem.

    My ULS logs are also cluttered with the message:

    5/31/2011 12:29:42.31  wmiprvse.exe (0x085C)                    0x1074 SharePoint Portal Server       SSO                            0 High     MSSCNTRS: Cannot get perf statistics on library SSO. 
    05/31/2011 12:29:42.31  wmiprvse.exe (0x085C)                    0x1074 SharePoint Portal Server       SSO                            0 High     Error code is: -2147418113 
    05/31/2011 12:29:42.31  wmiprvse.exe (0x085C)                    0x1074 SharePoint Portal Server       SSO                            0 High     MSSCNTRS: Cannot get perf statistics on library SSO.

    It seems to me that some service is trying to use SSO so my question is how do I know what service is trying to use it so I can find out why?

    SSO is not enabled on my MOSS 2007 farm and I don't want it to be.   I cannot find an reference for the Error code  "-2147418113"  What does this error code mean?


    dms


    Hello, did you ever find out what the cause of this was.

    We have involved Microsoft PSS on a case and they are finding the same situaiton here. It is throwing a lot of errors but we do not have SSO enabled and we aren't sure of the ramifications of these errors.


    Keith Caravelli
    Monday, November 14, 2011 11:24 PM