Monday, October 11, 2010

Error: The Security Token Service is not available. The Security Token Service is not issuing tokens. The service could be malfunctioning or in a bad state.

Error:
The Security Token Service is not available. 
The Security Token Service is not issuing tokens. The service could be malfunctioning or in a bad state.
(Or) 
An exception occurred when trying to issue security token: Could not connect to http://localhost:32843/SecurityTokenServiceApplication/securitytoken.svc. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:32843. 
(Or)
The Managed Metadata Service '' is inaccessible.
Reason:
These are all unusual errors and you will get these kind of errors, if you have installed the SSL certificate on your SharePoint server. In my situation, I have installed SSL & Lync Server 2010 RC in my SharePoint 2010 server. 
Solution:
I found an very nice post about this issue in the below URL:
But unfortunately, the above post is not useful for me. Anyhow, it gave me some ideas about the actual issue. Finally I have found an simple solution. 
1. Go to InetMgr
2. Just start the "SharePoint Web Services" site and "SharePoint Web Services Root" application pool as per the below screenshot.















3. To make sure everything, do the "IISReset". 
Thats it....
Posted by at
Labels: ,

11 comments:

  1. SharePoint EngineJanuary 1, 2011 at 5:06 AM

    This comment has been removed by a blog administrator.

    ReplyDelete
  2. AnonymousFebruary 8, 2011 at 2:39 AM

    This comment has been removed by a blog administrator.

    ReplyDelete
  3. AravindFebruary 21, 2011 at 3:43 AM

    Hi I activated that service...But all my site,visual studio ,sql ,Microsoft office and no item in administrative tools ...every thing is collapsed....

    Error log shows Error:
    The identity of application pool b741904631e547a9b6786cdb591d0e67 is invalid. The user name or password that is specified for the identity may be incorrect, or the user may not have batch logon rights. If the identity is not corrected, the application pool will be disabled when the application pool receives its first request. If batch logon rights are causing the problem, the identity in the IIS configuration store must be changed after rights have been granted before Windows Process Activation Service (WAS) can retry the logon. If the identity remains invalid after the first request for the application pool is processed, the application pool will be disabled. The data field contains the error number.

    How can i recover this problem??

    ReplyDelete
  4. Sensoft2000February 21, 2011 at 5:27 AM

    Aravind,

    Try the step 3, as I mentioned in http://sensoft2000-sharepoint.blogspot.com/2009/08/error-http-404-file-not-found-in-moss.html & also, restart the IIS .

    This may be helpful to you.

    ReplyDelete
  5. Binary RepublikJuly 1, 2011 at 5:13 AM

    This comment has been removed by a blog administrator.

    ReplyDelete
  6. SaifullahDecember 28, 2011 at 12:01 PM

    Hi,
    I'm was SharePoint 2010 in test/educational environment and I have been facing the issue since I have migrated from "failing" server to new one. After going trough all possible blogs you can imagine I ended up in your blog which solved my issue. Thank you!

    ReplyDelete
  7. AndrewFebruary 7, 2012 at 7:04 AM

    Unbelievable! Thanks

    ReplyDelete
  8. HelloSharePointOctober 12, 2012 at 5:26 PM

    That did it for me. Thanks!

    ReplyDelete
  9. Uyen QuachMay 10, 2013 at 12:55 PM

    THANK YOU SO MUCH

    ReplyDelete
  10. UnknownAugust 6, 2013 at 11:28 AM

    That did it for me as well, started app pool and IISReset, finally worked.

    ReplyDelete
  11. UnknownDecember 2, 2014 at 5:42 AM

    thanks it worked for me. you have saved my day

    ReplyDelete

Subscribe to: Post Comments (Atom)