Keith Smith - My Blog
Turn on anonymous access for a siteWednesday, April 19, 2017 - Posted by Keith A. Smith, in SharePoint
Turn on anonymous access for a site
• Open the site on which you want to turn on anonymous access. • On the Site Actions menu, click Site Permissions. • On the permissions page, click Anonymous Access. • In the Anonymous Access dialog box, select the parts of your Web site that you want anonymous users to access, and then click OK. Turn on anonymous access for a list or library that uses unique permissions Follow these steps only if you have turned on anonymous access for the site as described in the previous procedure and have granted access to either the entire site or only lists and libraries in step 4 above. Also, make sure the list or library you want to work with uses unique permissions instead of inheriting permissions from its parent site. For more information about unique permissions, see Control access to a specific piece of content or, for basics, see What is uniquely secured content? • Browse to the list or library that uses unique permissions for which you want to enable anonymous access. • Click the List tab on the List Tools menu (or the Library tab on the Library Tools menu). • Click the List Permissions (or Library Permissions) button. • On the Permissions Tools menu, click Anonymous Access. • In the Anonymous Access dialog box, select the permissions that you want to grant to anonymous users for this list or library, and then click OK. -End |
 0 Comments
Tweet
|
an unhandled exception occurred in the silverlight applicationWednesday, April 19, 2017 - Posted by Keith A. Smith, in SharePoint
Problem
an unhandled exception occurred in the silverlight application Solution Just Enable the Security Validation in the central administration from Manage Web Applications --> General Settings (from ribbon). Silverlight Application is unable to connect to the WCF endpoint configured by the product for enabling Client Object Model, if Security validation is set to Off. -End |
| 0 Comments
Tweet
|
Event ID 6398 and 5586Wednesday, April 19, 2017 - Posted by Keith A. Smith, in SharePoint
Simple fix for Event ID 6398 and 5586
Disable the Health Analysis Job (Daily, Microsoft SharePoint Foundation Timer, Any Server) in the central administration -End |
| 0 Comments
Tweet
|
Warning 1015- Failed to connect to server Error- 0x80070005Wednesday, April 19, 2017 - Posted by Keith A. Smith, in SharePoint
Problem
On a daily basis, you see the following warning appear in the SharePoint server host's Application log: Log Name: Application Source: MsiInstaller Date: [date] Event ID: 1015 Task Category: None Level: Warning Keywords: Classic User: [SharePoint farm account] Computer: [a SharePoint Server host] Description: Failed to connect to server. Error: 0x80070005 Event Xml: 0x80070005 (NULL) (NULL) (NULL) (NULL) (NULL) You may see a 100 or so similar warnings appear daily, each one accompanied by a corresponding Information event, such as the following: Log Name: Application Source: MsiInstaller Date: [date] Event ID: 1035 Task Category: None Level: Information Keywords: Classic User: [SharePoint farm account] Computer: [a SharePoint Server host] Description: Windows Installer reconfigured the product. Product Name: Microsoft InfoPath Form Services English Language Pack. Product Version: 14.0.7015.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success or error status: 0. Event Xml: Microsoft InfoPath Form Services English Language Pack 14.0.7015.1000 1033 0 Microsoft Corporation (NULL) Each of these pairs corresponds to a different component that can be configured for the farm. Discussion These are associated with the farm's Product Version Job, which by default runs daily at 12:45 AM. Compare the times of these warnings with the time that your farm's Product Version Job runs, and you'll see the association. Solution 1. Add the farm account to the host's local administrator group. 2. Restart the SharePoint 2010 Timer service. 3. Remove the farm account from the host's local administrator group. 4. Run the farm's product Version Job. 5. Check the host's Application Log. |
| 0 Comments
Tweet
|
People search relevance is not optimized when the Active DirectoryWednesday, April 19, 2017 - Posted by Keith A. Smith, in SharePoint
People search relevance is not optimized when the Active Directory has errors in the manager reporting structure.
People search relevance is not optimized when the Active Directory has errors in the manager reporting structure. Scenario: Specify the company leaders explicitly. Use the following PowerShell commands: $upap = Get-SPServiceApplicationProxy [appid]; Add-SPProfileLeader $upap [Domain]\[UserName]. Run ‘Get-SPProfileLeader $upap’ to check whether the leader was successfully added. As a last step, run a full crawl on the content source containing the start address (URL) of the user profile application. For more information about this rule, see “http://go.microsoft.com/fwlink/?LinkID=248249“. Steps: Run the follow commands in a SharePoint Management shell as administrator: 1) Get-SPServiceApplicationProxy 2) $upap = Get-SPServiceApplicationProxy -Identity c36a7818 -668b-4190-87f9-03aed906e465 3) $upap 4) Add-SPProfileLeader -ProfileServiceApplicationProxy $upap -Name “DOMAIN\Department.Head” 5) Get-SPProfileLeader $upap 6) Run a full crawl on the content source containing the start address (URL) of the user profile application If you want to check the leadres: Get-SPProfileLeader Get-SPProfileLeader -ProfileServiceApplicationProxy $upap If you want to delete the leaders: Remove-SPProfileLeader Remove-SPProfileLeader -ProfileServiceApplicationProxy $upap -Name "DOMAIN\user1" -End |
| 0 Comments
Tweet
|
Categories
All Categories
Network
VMware
FOG aka Free Open Ghost
Xen
Journal of thoughts
SharePoint
Automation
Microsoft
Linux
Security
Apple
Subscription
