The display becomes blocky, and can no longer be read

Websites develop distortion in both text and pictures, thought it is more noticeable in text. Horizontal lines shift from left to right a pixel or two, sometimes more when it's really bad. i've seen some shift entire letters. this makes it very difficult to read, especially since it more spreads the text than shifts it cleanly. if i highlight the text, it disappears. if i start a new page, it disappears. it seems to inconsistently get worse the more activity there is on the page, or if i scroll up or down. No other program on my computer has this problem, and i checked today that all my drivers are up to date. i also checked for viruses on the computer and in mozilla. i have gone so far as to uninstall and reinstall the program without the problem going away. i have also seen a similar issue in your foums, but have not seen a solution given to that post from 2010.

Try to disable hardware acceleration in Firefox.
*Tools > Options > Advanced > General > Browsing: "Use hardware acceleration when available"
*https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes

Similar Messages

I got a error(The Content has expired and can no longer be used)

Hi,
I built a SharePoint 2013 Farm.
Infrastructure composition is:
・WebFrontEnd Server * 2(Web#1,Web#2)
・Application Server * 1
・SQL Server * 1
・OfficeWebApps Server * 1
・etc(DPM,AD,DocAve)
Site composition is:
・Community Site(Customize Site)
・Enterprise Search Center
After that, I added a WebWebFrontEnd Server(Web#3) to the SharePoint Farm.
So, I had a trouble.
The Enterprise Search Center had not been able to displayed in Web#1 and Web#2.
But, Web#3 is displayed Enterprise Search Center.
When The Enterprise Search Center had not been able to displayed, I get a error message.(The context has expired and can no longer be used. (Exception from HRESULT: 0×80090317))
Does Anyone have the same trouble?
Thanks,
Tomohiro

HI tomohiro,the issue could be of many reasons like the Time not set correctly,App pool.Please check the below link that gives more information on the resolution.
http://expertsharepoint.blogspot.de/2014/10/the-context-has-expired-and-can-no.html
Anil Avula[Partner,MCP,MCSE,MCSA,MCTS,MCITP,MCSM] See Me At: http://expertsharepoint.blogspot.de/

The context has expired and can no longer be used. (Exception from HRESULT: 0x80090317)

We have a problem with our wiki site collection. Once a day (and sometimes more), we get the following error message :
The context has expired and can no longer be used. (Exception from HRESULT: 0x80090317)
This message is displayed to everyone, and will stay there for an hour or so before the collection is back to life.
Doing an iisreset would get the site working but that will last for a day at the most.
This is what we checked and tried so far :
1. Our time zones are set and are correct.
2. Changing the timeout or disabling the web page security validation (followed by an iisreset) didn't work.
3. All server use the same NTP server for time sync (and they are indeed in sync).
4. It is happening only on the wiki collection, not the other collections.
5. We are unable to reproduce the behavior on the staging servers.
Some particularities :
1. Regional settings are set to French (Canada)
2. We have 500+ wiki pages in the site collection
3. We require page check-out / check-in for editing. Tried without, same problem.
Any ideas as to what should we try next ?
Regards,
homerggg

Hi,
I don't think we have changed them from the default, a quick look shows ours are set to:
Token-timeout = 24hrs
FormsTokenLifetime = 10hrs
WindowsTokenLifetime = 10hrs
LogonTokenCacheExpirationWindow = 10m
Rob

I own the very first ipod and can no longer be updated or synced any suggestions to get it back up and running, has just decided to stop 2015

I own the very first ipod and can no longer be updated or synced any suggestions to get it back up and running, has just decided to stop 2015

Try:
- iOS: Not responding or does not turn on
- Also try DFU mode after try recovery mode
How to put iPod touch / iPhone into DFU mode « Karthik's scribblings
- If not successful and you can't fully turn the iOS device fully off, let the battery fully drain. After charging for an least an hour try the above again.
- Try another cable
- Try on another computer
- If still not successful that usually indicates a hardware problem and an appointment at the Genius Bar of an Apple store is in order.
Apple Retail Store - Genius Bar
It could be that the battery has died

I have an iphone 4s and have installed the new ios download and can no longer find games and other apps that i have downloaded. Where would they be or have they been wiped?

I have an iphone 4s and have installed the new ios download and can no longer find games and other apps that i have downloaded. Where would they be or have they been wiped?

Hi,
don´t be worry, this would not be a problem.
You have to take the same Aplle ID on both devices, then you can sync them via iTunes by using all universal apps on each device, create playlists, albums and all the things you need and sync it, no problem...
cu
dienoppe

SharePoint Navigation Error:The context has expired and can no longer be used. (Exception from HRESULT: 0x80090317)

Hi,
I take a exeption on the SharePoint 2013 left navigation.
Exeption: "The context has expired and can no longer be used. (Exception from HRESULT: 0x80090317)"
I searched this exeption keyword on the internet and I find usualy 3 results
1)check datetime servers --> I checked datetime for all SP Severs ,DB server and AD server ..there is no problem
2)Disabled the WebPageSecurity Validation on CA>General Settings-->I tired and problem not solved
3) Reset IIS --> if I restart IIS problem solved but after 2-3 hours or anytime error comes again..
ULS Log:
PortalSiteMapProvider was unable to fetch children for node
at URL: /MySite/MySubSite, message: The context has expired and can no longer be used. (Exception from HRESULT: 0x80090317), stack trace:
at Microsoft.SharePoint.SPGlobal.HandleComException(COMException comEx)
at Microsoft.SharePoint.Library.SPRequest.SetHttpParameters(String bstrHttpMethod, String bstrRequestDigest, UInt32 flags, Guid gTranLockerId, Byte[]& ppsaImpersonateUserToken, Boolean bIgnoreTimeout, String bstrUserLogin, String bstrUserKey, UInt32
ulRoleCount, String bstrRoles, Boolean bWindowsMode, String bstrAppPrincipalName, Boolean bIsHostHeaderAppPrincipal, String bstrOriginalAppPrincipalIdentifier, ApplicationPrincipalInfo& pAppUserInfo, Boolean bInvalidateCachedConfigurationProperties, Int32
lAppDomainId, ISPManagedObjectFactory pFactory, Boolean bCallstack, ISPDataCallback pCanaryCallback)
at Microsoft.SharePoint.SPGlobal.CreateSPRequestAndSetIdentity(SPSite site, String name, Boolean bNotGlobalAdminCode, String strUrl, Boolean bNotAddToContext, Byte[] UserToken, SPAppPrincipalToken appPrincipalToken, String userName, Boolean bIgnoreTokenTimeout,
Boolean bAsAnonymous)
at Microsoft.SharePoint.SPWeb.InitializeSPRequest()
at Microsoft.SharePoint.SPWeb.EnsureSPRequest()
at Microsoft.SharePoint.SPWeb.get_Request()
at Microsoft.SharePoint.Publishing.Navigation.SiteNavigationSettings..ctor(SPSite site)
at Microsoft.SharePoint.Publishing.Navigation.SiteNavigationSettings.GetSiteNavigationSettings(SPSite site)
at Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapNode.GetNavigationChildren(NodeTypes includedTypes, NodeTypes includedHiddenTypes, Boolean trimmingEnabled, OrderingMethod ordering, AutomaticSortingMethod method, Boolean ascending, Int32 lcid)
at Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapNode.GetNavigationChildren(NodeTypes includedTypes, NodeTypes includedHiddenTypes, OrderingMethod ordering, AutomaticSortingMethod method, Boolean ascending, Int32 lcid)
at Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapNode.GetNavigationChildren(NodeTypes includedHiddenTypes)
at Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapProvider.GetChildNodes(PortalSiteMapNode node, NodeTypes includedHiddenTypes)
Plaase Help.

Hi Veli,
Please check the security token timeout value and it is set to 1440 as expected by default. You can check via running the command:
stsadm -o getproperty -pn token-timeout
Then check the OOB recycle times of the probkematic web application pool, and add daily recycle times for the problematic web application pool. You can do as the article:
http://technet.microsoft.com/en-us/library/cc754494(v=WS.10).aspx
Best Regards,
Wendy
Wendy Li
TechNet Community Support

The context has expired and can no longer be used. (Exception from HRESULT: 0×80090317)

I have followed the instructions on this blog. http://blog.cloudshare.com/2012/10/22/how-to-fix-sharepoint-2013-web-application-error-the-context-has-expired-and-can-no-longer-be-used/ and
it fixes the problem for a short time. I have to keep doing IISResets to get my farm backup.
Please Help.

Have you trid Ajay Khanna's suggestion from the comments field?
From Central Admin- Select the web application and Select --> Web Application General Settings --> Navigate to 'Web page Security validation', change or disable the timeout field.
Steven Andrews
SharePoint Business Analyst: LiveNation Entertainment
Blog: baron72.wordpress.com
Twitter: Follow @backpackerd00d
My Wiki Articles:
CodePlex Corner Series
Please remember to mark your question as "answered" if this solves (or helps) your problem.

The context has expired and can no longer be used

I am running across a repeatable error when accessing a specific Site Collection. EVERY TIME the SC is loaded we receive the error 'The context has expired and can no longer be used'.
I have already validated the SharePoint servers' time zones are all the same and match the web application(s), as well as set the 'Web
page Security validation' to "Off".
What else could I be missing? Could this have anything to do with Distributed Cache?
- Rick

Hi,
We just began to have the same error. The servers are also correctly set for the timezone (UTC) as well as the Web Applications.
The error happens for every site collections, there isn't a specific site where I'm able to reproduce the issue.
This is the ULS :
05/27/2014 12:59:05.98 w3wp.exe (0x1524) 0x0780 Web Content Management Publishing Cache ahh6l Verbose CreateListItemFromUrl : Parameters url : '/sitename/SitePages/Home.aspx', enableCheckedOutItem : 'True', checkedOutByCurrentUser 'False' retVal Id = '4618889e-0e1c-4503-a7fb-70fd36e2661d'. 01ff949c-98cc-d0fb-9795-c691c2852f54
05/27/2014 12:59:05.98 w3wp.exe (0x1524) 0x0780 Web Content Management Publishing Cache ahh6l Verbose CreateListItemFromUrl : Parameters url : '/sitename/SitePages/Home.aspx', enableCheckedOutItem : 'True', checkedOutByCurrentUser 'False' retVal Id = '4618889e-0e1c-4503-a7fb-70fd36e2661d'. 01ff949c-98cc-d0fb-9795-c691c2852f54
05/27/2014 12:59:06.00 w3wp.exe (0x1524) 0x0780 SharePoint Foundation Runtime tkau Unexpected System.Runtime.InteropServices.COMException: The context has expired and can no longer be used. (Exception from HRESULT: 0x80090317) at Microsoft.SharePoint.Library.SPRequestInternalClass.SetHttpParameters(String bstrHttpMethod, String bstrRequestDigest, UInt32 flags, Guid gTranLockerId, Byte[]& ppsaImpersonateUserToken, Boolean bIgnoreTimeout, String bstrUserLogin, String bstrUserKey, UInt32 ulRoleCount, String bstrRoles, Boolean bWindowsMode, String bstrAppPrincipalName, Boolean bIsHostHeaderAppPrincipal, String bstrOriginalAppPrincipalIdentifier, ApplicationPrincipalInfo& pAppUserInfo, Boolean bInvalidateCachedConfigurationProperties, Int32 lAppDomainId, ISPManagedObjectFactory pFactory, Boolean bCallstack, ISPDataCallback pCanaryCallback) at Microsoft.SharePoint.Library.SPRequest.SetHttpParameters(String bstrHttpMethod, String bstrRequestDigest, UInt32 flags, Guid gTranLockerId, Byte[]& ppsaImpersonateUserToken, Boolean bIgnoreTimeout, String bstrUserLogin, String bstrUserKey, UInt32 ulRoleCount, String bstrRoles, Boolean bWindowsMode, String bstrAppPrincipalName, Boolean bIsHostHeaderAppPrincipal, String bstrOriginalAppPrincipalIdentifier, ApplicationPrincipalInfo& pAppUserInfo, Boolean bInvalidateCachedConfigurationProperties, Int32 lAppDomainId, ISPManagedObjectFactory pFactory, Boolean bCallstack, ISPDataCallback pCanaryCallback) 01ff949c-98cc-d0fb-9795-c691c2852f54

The context has expired and can no longer be used errors making farm unusable

There are a couple of other posts on this forum about the message "The context has expired and can no longer be used" but they all suggest something related to time and time zone differences. This is not the case in my farm and I have disabled
the security checking of requests on my web applications. Hopefully someone at Microsoft is very aware of this and is working to resolve it because my farm and many others are unusable like this.
I have dug through all of the ULS errors when it happens and there is nothing useful. It barely even registers as a message although, I have not turned on verbose logging, which I am about to try. I have SP 1 installed. Just to be clear, this is happening
on SharePoint 2013 Enterprise.
I have been fighting this for a month. I can add a few things about the farm I am trying to fix:
1. It was a WSS 3.0 farm that when through a 2007-2010-2013 migration in short order.
2. I believe it is under-powered on the hardware side. All VMs on a host shared with 40 other VMs, some fairly busy. Here's the virtual farm breakdown:
-1 WFE with 12GB RAM and 2 cores
-3 app servers with similar resources
-No paging file on C: on any VM. This is a decision by sysadmin. Paging on D: is system managed. Probably irrelevant.
3. Rapidly clicking from link to link seems to bring on the failure much sooner.
Any suggestions even about how to troubleshoot this would be appreciated.

Ultimately, I think it is a time sync issue across the farm. We still have request management off on all boxes because I cannot get the admins to resolve this issue but, in my lab environment I ran into a similar thing.
I may turn RM back on later to see if it comes back but here's what I think happens: In production we have 2 ESXi hosts and our SP environment is all AD (of course). The clocks are all out of sync, sometimes beyond 5 minutes. (The time sync for AD is something
I believe a lot of admins don't understand when running virtual.)
If you allow ESXi to try to sync the time for all guests you run into problems. Maybe they are more pronounced with SharePoint. Anyway, VMware and AD start fighting over the time (check your event logs) and, for us, the clocks across the domain get out of
sync beyond the 5 minute allowable window.
I recommend disabling time sync from host to guest and do what MS recommends: make your domain controller the master time server and configure it to get its time from a reliable source (which can be a single hardware host over NTP). Make other domain controllers
sync from the PDC. The other windows machines will all sync to the domain when they log in. This will prevent SharePoint from issuing tokens from one machine that are out of sync time-wise with the other machines and thus throwing the "Context has expired
and can no longer be used" errors.
Note that disabling host to guest time sync is not as simple as just clearing / un-checking the box in the VSphere client. That doesn't do it. You will need to Google for the 6 or so custom properties you must add to each guest to prevent VMWare from re-synchronizing
after certain hardware events.

The Context has expired and can no longer be used error

Hello All,
I am getting ‘The context has expired and can no longer be used.’ error.
The last thing that was modified on the farm was Distributed Cache Service.
We stopped it on the application server and only have it run on the two WFE’s servers.
Also the cache size was changed to 2048MB.
Is it possible that this change is causing the error?
We don’t have ‘Default Time Zone’ selected for the web application.
But we never saw this error till now.
Any suggestions?
Thank you,
Zabcia

Hi Zabcia,
Thanks for posting this issue,
following could be the reason of raising this issue
1. Security context of your session might be expired
2. Somebody/you might have change the data time of your server.
you can follow below mentioned steps to fix this issue
Just change/update the Date/Time in the SharePoint server
Increase the Security context in SharePoint central admin. This can be done by following the below steps:
Go to central admin
Go to "Application management section" Go to "Web Application General Settings"
Go to "Web page Security validation" section & increase the timeout field. Or, you can simply disable this option.
I hope this is helpful to you, mark it as Helpful.
If this works, Please mark it as Answered.
Regards,
Dharmendra Singh (MCPD-EA | MCTS)
Blog : http://sharepoint-community.net/profile/DharmendraSingh

I have the mini display port cable to hdmi. When I connect I can get audio but on the video I get the display auro screen and can't get my actual display to show as that is not what shows on my display. How can I fix this?

I have the mini display port cable to hdmi. When I connect I can get audio but on the video I get the display auro screen and can't get my actual display to show as that is not what shows on my display. How can I fix this?

System Preferences>Displays
There is a little white bar. When you have your TV connected, move the white bar to the other display. Your main desktop is now the TV screen

TA22652 Some of my music was purchased with an old email address which I no longer have. I have forgotten the password to it and can no longer use music from old account. We moved and no longer have the same email service, but would like to use all music

Some of my music was purchased with an old email address (old account) which is no longer valid. Since it has been a long time since we used the email address we no longer know the password. Now I can't access the music from my old account due to using a new computer. I've purchased the music and downloaded cds with the old account and need to be able to get my music.
Thank you!!

➡ https://iforgot.apple.com/

HT1695 i downloaded the IOS software upgrade and can no longer connect to any WiFi network, what can I do to fix this?

I have attempted to reset the network settings, nothing changed. The wireless router is working and has nothing wrong with it. Ever since I downloaded the software update, WiFi connection can not happen and every time I try to do anything that uses the internet it directs me to the apple support site. How can this be resolved?

I've tried the following:
* Settings | General | Reset | Reset Network Settings (Twice)
* Settings | General | Reset | Reset All Settings (Once)
* Plugging it in and doing a "Restore" through iTunes (that's how I downloaded iOS 5.1.1 in the first place)
All the passcodes and restrictions are are turned off.
When I first try to connect to the network, I'm prompted to enter my username and password (I've elected to "forget" the network a few times so I can get this screen again). If I enter it wrong, then I just get an error that I'm not connected. When I enter it right, I get a warning that the certificate is "not verified". When I click on "More Details", I can see all the information that got pulled from the network (Issuer Name, Signature Algorithm, Public Key Algorithm, Key Usage, etc.). When I choose to "Accept", I get the little icon indicating that it's trying to connect...this never goes away (I let it run for an hour).
The encryption type on the main Wifi I'm trying to connect to says it's RSA (I'm guessing it's WEP though...I didn't set it up, our IT group did that).

Can't get the ministore to work and can no longer get album artwork!!

The ministore is blank at the bottom of my screen and when I try to get album artwork for my music it doesn't do anything. It's been doing this for a long time and I cant find a solution on this website. Someone please help?

Try sliding the words instead of tapping them.

Another question concerning Context Expired and Can No Longer be Used error

I know this has been covered many times before - each time with essentially the same recommendations: Make sure the time zone is set for the web applications, make sure the clocks are synchornized between the hosts, adjust the timeouts (I've done defaults,
1 minute/2 minute and 5 minute/10 minute), extend security validation time outs, turn off security validation time outs.
Note of these has worked. It seems, from other folks with the issue, that this is a problem that's been stumping Microsoft as well. So I don't feel like paying them $500 bucks for a support session for this.
Has anyone come accross a better fix than the above?
Here's the latest correlation data from the logs. It points to the login timeout as the problem, but I'm at a loss as to what to do about it.
Thanks in advance.
Getting Error Message for Exception System.Web.HttpUnhandledException (0x80004005): Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> Microsoft.SharePoint.SPException: The context has expired and can no longer be used. (Exception
from HRESULT: 0x80090317) ---> System.Runtime.InteropServices.COMException: The context has expired and can no longer be used. (Exception from HRESULT: 0x80090317)
at Microsoft.SharePoint.Library.SPRequestInternalClass.SetHttpParameters(String bstrHttpMethod, String bstrRequestDigest, UInt32 flags, Guid gTranLockerId, Byte[]& ppsaImpersonateUserToken, Boolean bIgnoreTimeout, String bstrUserLogin, String bstrUserKey,
UInt32 ulRoleCount, String bstrRoles, Boolean bWindowsMode, String bstrAppPrincipalName, Boolean bIsHostHeaderAppPrincipal, String bstrOriginalAppPrincipalIdentifier, ApplicationPrincipalInfo& pAppUserInfo, Boolean bInvalidateCachedConfigurationProperties,
Int32 lAppDomainId, ISPManagedObjectFactory pFactory, Boolean bCallstack, ISPDataCallback pCanaryCallback)
at Microsoft.SharePoint.Library.SPRequest.SetHttpParameters(String bstrHttpMethod, String bstrRequestDigest, UInt32 flags, Guid gTranLockerId, Byte[]& ppsaImpersonateUserToken, Boolean bIgnoreTimeout, String bstrUserLogin, String bstrUserKey, UInt32
ulRoleCount, String bstrRoles, Boolean bWindowsMode, String bstrAppPrincipalName, Boolean bIsHostHeaderAppPrincipal, String bstrOriginalAppPrincipalIdentifier, ApplicationPrincipalInfo& pAppUserInfo, Boolean bInvalidateCachedConfigurationProperties, Int32
lAppDomainId, ISPManagedObjectFactory pFactory, Boolean bCallstack, ISPDataCallback pCanaryCallback)     -
-- End of inner exception stack trace ---
at Microsoft.SharePoint.SPGlobal.HandleComException(COMException comEx)
at Microsoft.SharePoint.Library.SPRequest.SetHttpParameters(String bstrHttpMethod, String bstrRequestDigest, UInt32 flags, Guid gTranLockerId, Byte[]& ppsaImpersonateUserToken, Boolean bIgnoreTimeout, String bstrUserLogin, String bstrUserKey, UInt32
ulRoleCount, String bstrRoles, Boolean bWindowsMode, String bstrAppPrincipalName, Boolean bIsHostHeaderAppPrincipal, String bstrOriginalAppPrincipalIdentifier, ApplicationPrincipalInfo& pAppUserInfo, Boolean bInvalidateCachedConfigurationProperties, Int32
lAppDomainId, ISPManagedObjectFactory pFactory, Boolean bCallstack, ISPDataCallback pCanaryCallback)
at Microsoft.SharePoint.SPGlobal.CreateSPRequestAndSetIdentity(SPSite site, String name, Boolean bNotGlobalAdminCode, String strUrl, Boolean bNotAddToContext, Byte[] UserToken, SPAppPrincipalToken appPrincipalToken, String userName, Boolean bIgnoreTokenTimeout,
Boolean bAsAnonymous)
at Microsoft.SharePoint.SPWeb.InitializeSPRequest()
at Microsoft.SharePoint.SPWeb.EnsureSPRequest()
at Microsoft.SharePoint.SPWeb.get_Request()
at Microsoft.SharePoint.Publishing.Navigation.SiteNavigationSettings..ctor(SPSite site)
at Microsoft.SharePoint.Publishing.Navigation.SiteNavigationSettings.GetSiteNavigationSettings(SPSite site)
at Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapNode.GetNavigationChildren(NodeTypes includedTypes, NodeTypes includedHiddenTypes, Boolean trimmingEnabled, OrderingMethod ordering, AutomaticSortingMethod method, Boolean ascending, Int32 lcid)
at Microsoft.SharePoint.Publishing.Internal.CodeBehind.AreaNavigationSettingsPage.AddChildrenToControl(String parentId, PortalSiteMapNode node, Int32 depth, Int32 maxDepth)
at Microsoft.SharePoint.Publishing.Internal.CodeBehind.AreaNavigationSettingsPage.InitializeNavigationEditSort()
at Microsoft.SharePoint.Publishing.Internal.CodeBehind.AreaNavigationSettingsPage.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.HandleError(Exception e)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Barry Cohen

Hi Barry,
Thank you for your patience. Here are my suggestions about this issue:
1. Check SPNs for the application pool account for the web application ‘http://community.enet’ and take a screenshot: setSPN -L domain\app pool account (KVAERNER-NO\sno00769)
2. Ensure SharePoint WFE and APP boxes are trusted for delegation:
Trust for delegation.
Note: To perform this procedure, you must be a member of the Domain Admins group or the Enterprise Admins group in Active Directory, or you must have been delegated
the appropriate authority. As a security best practice, consider using Run as to perform this procedure.By default, no server is trusted for delegation, meaning that a service on a server in the Active Directory, cannot act on a user’s behalf, basically this
means that a service if trusted for delegation, can impersonate a user and request a Kerberos ticket in the users name.
Validate this setting in Active Directory using the following:
- Open Active Directory Users and Computers.
-In the console tree, click Computers. (Or the appropriate OU where your SharePoint Server resides)
-Right-click the computer you want to be trusted for delegation, and click Properties
-On the Delegation tab, check if ‘Trust this computer for delegation to any service (Kerberos only)’ is selected.
-Repeat this for all the servers in the SharePoint 2013 production farm.
3. Please let me know the SharePoint 2013 version. We recommend that you can upgrade to SharePoint 2013 SP1.
Best Regards,
Dats Luo

The display becomes blocky, and can no longer be read

Similar Messages

Maybe you are looking for