.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Post New Web Links

Claims to windows token service wont start in Central administration

Posted By:      Posted Date: September 01, 2010    Points: 0   Category :SharePoint
Not sure if this is a bug or some setting I just dont understand but I cannot get the claims to windows token service from manage services to show as started. When I click start I get this error in the event viewer: An attempt to start/stop instance of service Claims to Windows Token Service on server <SERVERNAME> did not succeed. Re-run the action via UI or command line on the specified server. Additional information is below. c2wts (DOMAIN\sp_farm) I have searched and searched for an answer. This thread http://social.technet.microsoft.com/Forums/en-US/sharepoint2010setup/thread/6b865ead-970b-4460-9dcf-1cc6d6d8530b talks about needing a connection to the internet, but my server is connected to the internet so i think i can rule that out. Also I have read that c2wts depends on the crypto service. I have run this command with no success: sc config c2wts depend= cryptsvc I can start the c2wts service through services.msc and it is succesful. But central administration still shows it is stopped. I have also re-run the installer in repair mode, and re-run the initial configuration wizard, maintaining all of the same settings as the previous installation. That didn't help. Basically, I'm out of ideas and I cant find much about this on the web. Any ideas?

View Complete Post

More Related Resource Links

Using the "Claims to Windows Token Service" to assist with single sign on



Does anyone know if it's possible to use the c2WTS service to achieve single-sign-on within SharePoint 2010, without turning it into a Claims-based application? My situation is that I'd like to use ADFSv2 (and/or Shibboleth) for user authentication, but instead of returning a SAML token back to SharePoint, I'd like to use c2WTS to transform that claim into a Kerberos ticket and pass that back to a SharePoint web app that's using classic Windows authentication. For this web application, we're not interested in federation - just looking to eliminate the Windows Integrated Authentication. All users will have a valid account (and thus UPN) in the domain. Our current environment is WSS 3.0 and we've mostly used AD groups for authorization. This makes it diffiuclt to simply migrate these sites to use claims in SharePoint 2010. Any feedback would be appreciated.

-joe c

Do I really need the 'Claims to Windows Token Service'

SharePoint 2010 complains when this service is not available, however if my web applications aren't using CBA, is this really necessary?
Conrad Goodman MCITP SA / MCTS: WSS3.0 + MOSS2007

Windows Identity Foundation Security Token Service can't stay logged in

I'm using the Windows Identity Foundation **(WIF)** Security Token Service **(STS)** to handle authentication for my application which is working all well and good. However I can't seem to get any long running login with the STS. From my understanding I shouldn't care about the client tokens at the application level since they can expire all they want to and it should redirect me to the STS and as long as they're still logged in on the STS it should refresh their application token. Yet it doesn't seem to want to keep them signed in. Here's what occurs in my login.aspx on the STS var cookie = FormsAuthentication.GetAuthCookie(userName, persistTicket); if (persistTicket) cookie.Expires = DateTime.Now.AddDays(14); Response.Cookies.Add(cookie); var returnUrl = Request.QueryString["ReturnUrl"]; Response.Redirect(returnUrl ?? "default.aspx"); Which was taken almost directly from existing application using normal Forms Auth. From my web.config <authentication mode="Forms"> <forms loginUrl="Login.aspx" protection="All" timeout="2880" name=".STS" path="/" requireSSL="false" slidingExpiration="true" defaultUrl="default.aspx" cookieless="UseDeviceProfile" enableCrossAppRedirects="false" /> </auth

Hw can i restart the central administration service?


Hi ,

Accidentally i stop central administration service (operations->services on server).

How can Central Administration Service be restarted? Cannot go to Central Admin, when the service is not running :-)

Please help me out




Central Administration, "User Profile Service Application" could not be provisioned


SP 2010 beta2 installed in Server Farm mode, using local account. OS = Windows 2008 R2, SQL Server 2008.

After SP Config Wizard is complete, the SP 2010 Central Administration is opened. I filled in the Service Account, clicked Next and a processing screen is spinning for abiut 3 minutes. After that IE8 displays an error message.

The service application proxy "User Profile Service Application" could not be provisioned because of the following error: The request channel timed out while waiting for a reply after 00:00:19.5439453. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.

Corelation Id: fe1bc44d-88ff-4297-85f8-4b5dcce248c1

Is it a critical error and can you please suggest where I can increase the timeout value?

Thanks very much in advance.

Central Administration returns blank page after installation on Windows 7

Hi, I have successfully installed SharePoint 2010 on Windows 7.  However when I browse to Central Administration, I just get a blank page.  I have been able to create a new web application and teamwork site using PowerShell, and that site also returns a blank page.  In the IIS log, I can see that the requests produce a 500 error.  Rerunning the Configuration Wizard has not helped.  Other ASP.NET sites run ok.

Any suggestions?

Service Unavailable opening Sharepoint 3.0 Central Administration



Hi everyone,


I have a Windows Server 2003 running WSS 3.0 that has started displaying "Service Unavailable" when I try to open the Central Administration page. I also get the following errors in the Event Viewer:



"The start address <sts3://servus-rkfdsp/contentdbid={126e686a-71da-426f-a5b1-102b6cd50f44}> cannot be crawled.

Context: Application 'Search index file on the search server', Catalog 'Search'

 Access is denied. Check that the Default Content Access Account has access to this content, or add a crawl rule to crawl this content.   (0x80041205)"


"The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again.

Context: Application 'Search', Catalog 'index file on the search server Search'"


"The Execute method of job definition Microsoft.SharePoint.Administration.Backup.SPBackupRestoreJobDefinition (ID 04a4cfe1-309c-479c-940b-e262ae9f4c23) threw an exception. More information is included below.

The backup job failed. For more information, see the error log that is located in the backup directory."


When accessing SharePoint or Central Administration 3.0 a "503 Service Unavailable" error is returne

I am running a MOSS 2007 server in a test environment. I have been off building other aspects of the environment, but I come back today and notice that SharePoint is no longer working. Whenver I try to access it or the Central Administration area I recieve a "503: Service Unavailable" error.

I have also notice that after an IISRESET that the applications pools that are associated with the SharePoint sites (Extranet, Intranet, Sharepoint - 21075, and Central Administration fail to start on their own. I can start the manually. They are all running under the DOMAIN\Administrator account (as are ALL of the SharePoint related features. I know, I know, but that is what the requestor of this test environment requested).

Additionally the following error codes are logged (NOTE: These are translated from German):

Event ID: 6641
Source: Office Sharepoint Server
The SSP timer Mandate for import distribution lists did not execute.

Reason: Registration failed: The user does not have the required logon on this computer.

Event ID: 2424
Source: Office Server Search
The update cannot be started because there is no access to

Sharepoint 2010 Central Administration Web site on Windows 7 comes up empty


Using the information presented at http://msdn.microsoft.com/en-us/library/ee554869.aspx (slightly modified to accommodate the fact that the SharePoint 2010 is today distributed in the form of an ISO file), I was able to finish all steps including all 10 steps of the configuration wizard. Dismissing the wizard should result with launching the browser showing the new SharePoint site - in my case however, that browser shows a completely empty page.

Similarly, selecting the SharePoint 2010 Central Administration entry from the Microsoft SharePoint 2010 Products folder (on the list of all installed products) results with the browser started at URL http://nik-workstation:23789/ - which is also completely empty

Since UAC is disabled - it ought to be the database. I believe that before installing SP 2010, I had SQL Server 2008 and SQL Server 2008 R2 November CTP (this is required by Azure AppFabric development) and I was hoping that the SP installer will find the database that fits the best. 

What is the best way to handle this? What is causing the problem?


Is there any way to use Process.Start in Windows Service?


We craete Deploy Windows Service. And it is installed on all servers.

When service get some new file deployment request, service deletes files and copy from ftp.

Anyway,if .exe file (deploy target file) is on process, service kills the process and copy the exe file, then start this file.

So I use Process.Start, but it does not operate.

When I debug source, there's no exception. So I checked "Allow service to interact with desktop", but the same.

And machines that installed service are various OS.

How can I solve this issue?

Windows Service Applications Tutorials

You can easily create services by creating an application that is installed as a service. For example, suppose you want to monitor performance counter data and react to threshold values. You could write a Windows Service application that listens to the performance counter data, deploy the application, and begin collecting and analyzing data.

Geneva Framework: Building A Custom Security Token Service


A Security Token Service, or STS, acts as a security gateway to authenticate callers and issue security tokens carrying claims that describe the caller. See how you can build a custom STS with the "Geneva" Framework.

Michele Leroux Bustamante

MSDN Magazine January 2009

Web Service Workflows: Deploy Distributed Business Processes With Windows Workflow And Web Services


Due to the distributed nature of a business process it makes sense for a workflow to be deployed as a distributed application. See how Windows Workflow and Web Services hold the key.

Israel Hilerio

MSDN Magazine October 2006

Service Station: Serialization in Windows Communication Foundation


Windows Communication Foundation supports several serialization mechanisms and provides a simple, interoperable foundation for future service-oriented applications. Here Aaron Skonnard explains it all.

Aaron Skonnard

MSDN Magazine August 2006

Windows Services: New Base Classes in .NET Make Writing a Windows Service Easy


Windows services are applications that run outside of any particular user context in Windows NT, Windows 2000, or Windows XP. The creation of services used to require expert coding skills and generally required C or C++. Visual Studio .NET now makes it easy for you to create a Windows service, whether you're writing code in C++, C#, or Visual Basic. You can also write a Windows service in any other language that targets the common language runtime. This article walks you through the creation of a useful Windows service, then demonstrates how to install, test, and debug the service.

Ken Getz

MSDN Magazine December 2001

Cannot Start Search service.


Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (9ca20163-f0f2-412c-a3ea-927a20205285).

Reason: Could not access the Search service configuration database 

Techinal Support Details:
Microsoft.Office.Server.Search.Administration.DatabaseException: Could not access the Search service configuration database   ---> System.Runtime.InteropServices.COMException (0xC004122D): Could not access the Search service configuration database 
   at Microsoft.Office.Server.Search.Administration.MSSITLB.IGatherApplications2.Mount(String bstrName)
   at Microsoft.Office.Server.Search.Administration.GathererApplication.ProvisionGathererApplication()
   at Microsoft.Office.Server.Search.Administration.GathererApplication.Provision()
   at Microsoft.Office.Server.Search.Administration.OSSIndexGathererApplication.Provision()
   at Microsoft.Office.Server.Search.Administration.SearchApi.<>c__DisplayClass20.<AddApp>b__1f()
   at Microsoft.Office.Server.Search.Administration.SearchApi.RunOnServer[T](CodeToRun`1 remoteCode, CodeToRun`1 localCode, Boolean useCurrentSecurityContext, Int32 versionIn)
   --- End of inner exception stack trace ---

ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend