Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, September 5, 2017 3:09 PM
Hi, we upgraded to SP 2013 about a month ago, and everything has been running fine. This morning, we are seeing multiple errors in our logs related to SPSecurityContext. Here is the text of one of the errors (I replaced the actual user name with <myusername>:
SPSecurityContext: Could not retrieve a valid windows identity for username '<myusername>' with UPN '<myusername>@la.lcl'. UPN is required when Kerberos constrained delegation is used. Exception: System.ComponentModel.Win32Exception (0x80004005): Access is denied Server stack trace: at System.ServiceModel.Channels.AppContainerInfo.GetCurrentProcessToken() at System.ServiceModel.Channels.AppContainerInfo.RunningInAppContainer() at System.ServiceModel.Channels.AppContainerInfo.get_IsRunningInAppContainer() at System.ServiceModel.Channels.PipeSharedMemory.BuildPipeName(String pipeGuid) at System.ServiceModel.Channels.PipeSharedMemory.get_PipeName() at System.ServiceModel.Channels.PipeConnectionInitiator.GetPipeName(Uri uri, IPipeTransportFactorySettings transport...
The username in question DOES have a valid windows identity. This is happening for multiple users when using custom apps (all the users seem to be able to get on our SharePoint site just fine with no "we don't recognize your userid" errors). Again, this was working for weeks and now this morning it isn't. Everyone is saying they "didn't do anything to the servers" yet suddenly this error is happening.
Can someone point me in the right direction of where to even begin to figure this out?
Thanks for any help!
All replies (3)
Wednesday, September 6, 2017 8:40 AM âś…Answered
Hi,
Please go to Central Administration->Application Management->Manage services on server, check if Claims to Windows Token Service is started. If it is not started, please start it. If it is started, please stop and restart it.
Please have a try and let's know the result.
Thanks,
Wendy
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected]
Tuesday, September 5, 2017 5:56 PM
Similar issues
Wednesday, September 6, 2017 3:47 PM
The servers were rebooted overnight and things are working this morning. I'm thinking it was as you said the Claims to Windows Token Service that got reset with the reboot. I'm marking that as the answer. Thanks!