(This applies to the RTM version of SharePoint and is an extremely common problem that is occurring with all of our RTM servers. I think that it will quickly become one of those things that everyone does each and every time they install a SharePoint server.)
There are two reasons why the “Claims to Windows Token Service” (c2wts) might not be started: (looking at the state of the service with the Service Manager MMC snapin will tell you which one applies to you)
1) If the service is in the Disabled state, then you did not turn it on using Central Admin. By default, c2wts is turned off (Disabled). You have to turn it on by-hand. This is one of the BOL post-installation steps that we tell you that you must do if after an EXISTING FARM installation. It must be done on each machine as you add it to the farm. It is not a “do-it-once-for-the-whole-farm” kind of command. If you installed the PowerPivot server as a “NEW SERVER” then we start the c2wts service for you automatically.
2) If c2wts is set to Automatic, but it is not started, then there is a known bug with the service (won’t be fixed for RTM) that the service ships lacking a dependency to the Crypto service. On a slow server, like a VM or one that is heavily loaded during reboot. e.g. you installed an update and there is lots of background activity during the reboot sequence, then the service startup may fail. To fix the issue, you can add the dependency by-hand by executing the following command as an elevated administrator:
C:\> sc config c2wts depend= cryptsvc
Ultimately, if you don’t add the dependency, you will find that the service actually does restart after a reboot. It takes a few minutes but ultimately the SharePoint infrastructure will see that there is a service that should be started but isn’t and SharePoint will start it for you. If you are unwilling to wait the 5-10 minutes for it to catch this condition, then issue the command above. Alternatively you can set the service as delayed start and that will solve the problem also.
Oh, the joys of administrating a SharePoint farm.
Hmm thanks, i did get option 2 when i installed my RC at my vhd. I start the service manually every time i boot into it. thx for the tip !
I have tried the second option but the service does not start up
Any suggestion?
Victor
(win 2008 x64 SP)
Victor: What version of SharePoint are you running?
Hi,
In my case c2wts qont start because the server has no direct access to the Internet. I have filled a connect comment on this. Also check my post at http://social.technet.microsoft.com/Forums/en-US/sharepoint2010setup/thread/6b865ead-970b-4460-9dcf-1cc6d6d8530b.
Regards,
MarianoC
Hi Mariano:
Hmmm… I have never seen this. I’ve seen issues with running the prereq installer for SP and issues with Internet access in some other areas but not with c2wts. I routinely run not connected to the Internet in my own little single machine VM on a hyper-V private network (own domain, own everything) and I haven’t see that. Interesting. I’ll check out your web site and see if I can help over there.
Thanks.
OK, the service wont start the FIRST time you run it (if not connected to the Internet). Then (I think) it downloads a certificate and can run without any connection… that may explain you can run it without an Internet connection.
I have traced the connection to an Akamai server near my location, and is as far as I can go for now. I really would like that someone can explain what’s the connection for… also if the service logs something will be more easy to understand what is trying to do…
Now that I have the service running I disconnect it from the Internet and it runs without problems, but will it need the connection again in the future? Who knows…
Regards,
Mariano.
Is this ONLY for the claims-based mode of authentication (I read “This is one of the BOL post-installation steps that we tell you that you must do if after an EXISTING FARM installation.”) – just checkin’…
Hi Daragh: No, it is for all connections except those using Secure Store. The C2WTS is used by all Windows-based accounts.
[...] Read more… [...]
[...] This post was mentioned on Twitter by Kasper de Jonge. Kasper de Jonge said: again needed the “Claims to Windows Token Service” command from the PowerPivot geeks: http://bit.ly/bDK8jd [...]