When user enters invalid credentials sharepoint 2010 displays white screen.
Insted of this i want it to display default Accessdenied page.
I tried below solution
View Complete Post
View Complete Post
I have a strange issue... i have one user which gets a white screen when trying to logon externally to sharepoint.
Connected to the network work's it asked him for his password and it works fine... But coming over a mobile connection it does not ask for a password or anything, just a white screen.
I have installed Sharepoint 2007 on a Windows 2008 r2 x64 server. When I browse a Sharepoint site on the server with IE 8 I get the pages displayed incorrectly.
If I use IE 6 I get the pages correctly displayed. I tryed to change the compatability view settings with no success. I have tryied this on different computes with IE 8 with same result.
Is there a solution to resolve the constant "Prompts" For user id's and passwords when a person tries to open/launch/edit office documents from sharepoint 2010.
My setup: sharepoint fqdn in the domain sp.domainname.local, The sharepoint server is a member of this internal domain. In dns I have local zone of sp.domainname.com with a cname that points to the internal sharepoint server. There is no issue
in users accessing the server both internal and external, The issue arises when Office documents are launched from SP2010.
In central admin I have configured the alternate access mappings to be
I have also tried putting the fqdn dns name of the sharepoint server in IE8 trusted zone but
no luck, I still get credential prompts.
I think the issue might be that Office does not see that the files are coming from the fqdn of sp.domainname.com so hence the prompts.
Trying to fix this as right now its a total pita. I found some previous posts on this issue with SP2007 but found nothing that really addresses this in SP2010.
Sometimes my SP page shows fully on my screen and other times it is too large to fit on my screen (the same page) This requires the annoying use of horizontal scroll bars. Any idea why this happens and how I can avoid in the future? Please
note I am a SP user not developer using page which is a subset of an enterprise SP site. Thanks