The Claims to Windows Token Service is stopped by default. Typically, starting this service is easy. In fact, I’ve never come across a situation where it didn’t “just start”, until now! In this thread on the SharePoint TechNet forums, a user was unable to provision the Claims to Windows Token Service due to the error “Illegal characters in path”. With no further information, it is difficult to identify which path this error is referring to. However, we have .NET Reflector! So what we do is simply take a look at the full stack trace of the error. Within the stack trace on the thread, you can see [crayon-53e762c1349f6715297941-i/], so clearly we’re dealing with the system attempting to retrieve a file name. Down further in the stack trace, we come across the first mention of a SharePoint related method, [crayon-53e762c134a21564726885-i/]. This is the method we’ll reflect. When looking at the [crayon-53e762c134a3a698056539-i/] method, it is easily identifiable as to what path we’re looking for. [crayon-53e762c134a4f351331758/] Clearly we need to look at the registry entry to make sure it is valid. In this case, HKLM\SYSTEM\CurrentControlSet\services\c2tws should have an ImagePath value of [crayon-53e762c134a64208218411-i/]. In the case of the poster on TechNet, the value was [crayon-53e762c134a78404393258-i/]. Note the quotes within the path. While I’m unsure as to how the value ended up with quotes, removing the quotes allowed the service to start successfully.
The post Unable to provision the Claims to Windows Token Service appeared first on Nauplius.