Managed metadata column value not visible

Posted on by Leave a comment

Symptom:

You have a document library and then you add Managed Metada column. You add a new document and assign values to the Managed Metadata column and save

Site collection admins are able to view the values assigned in the managed metadata column but the values are not visible to all the users.

 

Solution:

Each site collection has a hidden taxonomy list and all authenticated users should have read permissions to the list. Check the permissions by visiting the below URL

http://webapplication/sitecollectionname/Lists/TaxonomyHiddenList

Assign READ permissions to NT AUTHORITY\Authenticated Users

 

 

Active Directory groups not showing up in People Picker SharePoint

Posted on by Leave a comment

SharePoint is working fine and suddenly you find that AD groups are not resolving or Active Directory groups are not showing up in People Picker. You create a new site collection but you can not add Active Directory groups.

I have seen many posts on internet where many of us are having this issue.  Just wanted to share what has worked for me and it might work out for you as well.

Resolution:

This can happen for a number of reasons and i have spent few days trying to troubleshoot the issue. To start with, please check the following:

- Make sure your application pool account has read permissions to active directory

- Make sure User Profile Sync is running correctly. Try to do a full Sync

If the issue is happening for just a newly created site collection, just make sure it is not limited to a particular directory path.

  • Run the following command for the working site and broken site
    • $site = get-spsite {YourSiteURL}
      $site.UserAccountDirectoryPath
  • Compare the results
  • Run the second command to set the value for the broken site and check people picker
    • Set-SPSite -Identity {YourSiteURL}  -UserAccountDirectoryPath “”

If  the issue still persists then try to run the following  PowerShell commands to find out if there are any filters enabled on your web applications

stsadm -o getproperty -pn peoplepicker-searchadcustomfilter -url {YourSiteURL}

if you find any filters enabled, try running the above command for your other web applications (working ones) and compare the results.

For me it was wrong filters and it might just be for you as well.

Below are some PowerShell commands with different filters.

Filter accounts without any emails

stsadm -o setproperty -pn peoplepicker-searchadcustomfilter -pv “(|(mail=*)(objectcategory=group))” -url {YourSiteURL}

Note: I’ve added (objectcategory=group) with OR condition, as security groups don’t normally have E-Mails.

Do not get Disabled accounts and get users from only a particular Forest/Domain

stsadm -o setproperty -pn peoplepicker-searchadcustomfilter -pv “(&(userPrincipalName=*{yourdomain.com})(!(userAccountControl:1.2.840.113556.1.4.803:=2)))” -url {YourSiteURL}
Do not get Disabled accounts and get users from only a particular Forest/Domain including Groups

stsadm -o setproperty -pn peoplepicker-searchadcustomfilter -pv “(|(&(userPrincipalName=*{yourdomain.com})(!(userAccountControl:1.2.840.113556.1.4.803:=2)))(objectcategory=group))” -url {YourSiteURL}

Example:

stsadm -o setproperty -pn peoplepicker-searchadcustomfilter -pv “(|(&(userPrincipalName=*xyz.com)(!(userAccountControl:1.2.840.113556.1.4.803:=2)))(objectcategory=group))” -url http://mywebapp.com

 

 

Event 6398 The Execute method of job definition Microsoft.SharePoint.Administration.SPImmediateAlertsJobDefinition

Posted on by Leave a comment

Symptoms

The Execute method of job definition Microsoft.SharePoint.Administration.SPImmediateAlertsJobDefinition (ID e296817c-5c42-4dd1-a4cf-0830dbecbdcc) threw an exception. More information is included below.

stswel.dll: (unresolved symbol, module offset=0000000000014DF1) at 0x000007FEEF834DF1

stswel.dll: (unresolved symbol, module offset=0000000000015E10) at 0x000007FEEF835E10

stswel.dll: (unresolved symbol, module offset=00000000000163F0) at 0x000007FEEF8363F0

OWSSVR.DLL: (unresolved symbol, module offset=0000000000290DA5) at 0x000007FEED1D0DA5

OWSSVR.DLL: (unresolved symbol, module offset=000000000020126A) at 0x000007FEED14126A

OWSSVR.DLL: (unresolved symbol, module offset=0000000000201166) at 0x000007FEED141166

OWSSVR.DLL: (unresolved symbol, module offset=0000000000201562) at 0x000007FEED141562

OWSSVR.DLL: (unresolved symbol, module offset=00000000000CD433) at 0x000007FEED00D433

mscorwks.dll: (unresolved symbol, module offset=00000000002C8E77) at 0x000007FEF8AD8E77

Microsoft.SharePoint.Library.ni.dll: (unresolved symbol, module offset=0000000000101D38) at 0x000007FEF2861D38

Microsoft.SharePoint.ni.dll: (unresolved symbol, module offset=0000000001AF505C) at 0x000007FEE3CE505C

Microsoft.SharePoint.ni.dll: (unresolved symbol, module offset=00000000025F4251) at 0x000007FEE47E4251

Microsoft.SharePoint.ni.dll: (unresolved symbol, module offset=00000000025F146F) at 0x000007FEE47E146F

Microsoft.SharePoint.ni.dll: (unresolved symbol, module offset=00000000025F0DB7) at 0x000007FEE47E0DB7

mscorwks.dll: (unresolved symbol, module offset=00000000002CAC62) at 0x000007FEF8ADAC62

mscorwks.dll: (unresolved symbol, module offset=00000000001C9783) at 0x000007FEF89D9783

mscorwks.dll: (unresolved symbol, module offset=00000000001D615E) at 0x000007FEF89E615E

mscorwks.dll: (unresolved symbol, module offset=00000000007A83C6) at 0x000007FEF8FB83C6

mscorwks.dll: (unresolved symbol, module offset=0000000000210A54) at 0x000007FEF8A20A54

mscorwks.dll: (unresolved symbol, module offset=00000000001D0B51) at 0x000007FEF89E0B51

mscorwks.dll: (unresolved symbol, module offset=00000000002CADDE) at 0x000007FEF8ADADDE

stswel.dll: (unresolved symbol, module offset=000000000015CCA0) at 0x000007FEEF97CCA0

stswel.dll: (unresolved symbol, module offset=

ULS Logs

AlertsJob, Filter for Scheduled subscription with id {GUID} matched event with Id 8247430

ULSSendExceptionTag beginning for tag = 942880620

Resolution:

  • Turn ON verbose logging
  • Check ULG logs and try to find failed the subscription GUID
  • Run below PowerShell to find out about the list/document library where the alerts are subscribed

$webs=Get-SPWebApplication {WEBAPPURL}|Get-SPSite -Limit All| Get-SPWeb -Limit All
$alert=$webs|%{$_.Alerts}|?{$_.Id -eq “{SUBSCRIPTION GUID}“}
$alert|Select @{Name=”User”;Expression={$_.User.LoginName}}, List, @{Name=”Url”;Expression={$_.List.ParentWeb.Url}}

  • Once you got the document library/list name
  • Browse to the list and Site Actions ->Site Settings -> User Alerts
  • Check if SharePoint\System has any subscriptions.
  • Delete all the subscriptions for the system account

That’s it