Archive for the ‘SharePoint’ Category

An unexpected error has occurred

Monday, July 18th, 2016

Error

You go to a SharePoint site. Click on Site Actions > Site Permissions and you get the below error. You also get the same error if you go to Site Actions > Site Settings > People and Groups > Click on a group > Click New  > Add user. Your SharePoint site backups will fail for the subsite with this issue.

An unexpected error has occurred

Troubleshoot issues with Microsoft SharePoint Foundation.
Correlation ID: GUID numbers
Date and Time: 2/23/2015 2:11:34 PM
Go back to site

SP Unexpected Error Occured

ULS Logs

SharePoint ULS logs in t his care didn’t show any clue.

Time Process Area Category Level EventID Message
02/23/2015 13:11:34.62 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Logging Correlation Data Verbose 77a3 Starting correlation.
02/23/2015 13:11:34.62 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Logging Correlation Data Medium xmnv Name=Request
(GET:http://sharepoint.domain.com:80/sites/BizDept/Team/OSHA/_layouts/user.aspx)
02/23/2015 13:11:34.62 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nasq Entering monitored scope
(BeginRequestHandler)
02/23/2015 13:11:34.62 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation SQM Verbose 97qu SQM: Datapoint id 6693 marked as Increment
datapoint.
02/23/2015 13:11:34.62 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose b4ly Leaving Monitored Scope
(BeginRequestHandler). Execution Time=0.284673052021975
02/23/2015 13:11:34.62 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nass ____SQL Query Count=0
02/23/2015 13:11:34.62 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nass ____Execution Time=0.284673052021975
02/23/2015 13:11:34.62 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nasq Entering monitored scope
(PostAuthenticateRequestHandler)
02/23/2015 13:11:34.62 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Runtime Verbose 0000 Value for isAnonymousAllowed is : False
02/23/2015 13:11:34.62 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Runtime Verbose 0000 Value for checkAuthenticationCookie is :
False
02/23/2015 13:11:34.62 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose b4ly Leaving Monitored Scope
(PostAuthenticateRequestHandler). Execution Time=0.221815901182972
02/23/2015 13:11:34.62 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nass ____SQL Query Count=0
02/23/2015 13:11:34.62 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nass ____Execution Time=0.221815901182972
02/23/2015 13:11:34.62 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Logging Correlation Data Medium xmnv User=ADdomain
\SPServiceAcct
02/23/2015 13:11:34.62 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nasq Entering monitored scope
(PostResolveRequestCacheHandler)
02/23/2015 13:11:34.62 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose b4ly Leaving Monitored Scope
(PostResolveRequestCacheHandler). Execution Time=0.0282158765988415
02/23/2015 13:11:34.62 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nass ____SQL Query Count=0
02/23/2015 13:11:34.62 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nass ____Execution Time=0.0282158765988415
02/23/2015 13:11:34.62 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation General Verbose 6t8b Looking up context site
http://sharepoint.domain.com:80/sites/BizDept/Team/OSHA/_layouts/user.aspx in the farm SharePoint_Config
02/23/2015 13:11:34.62 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation General Verbose 6t8d Looking up the additional information
about the typical site http://sharepoint.domain.com:80/sites/BizDept/Team/OSHA/_layouts/user.aspx.
02/23/2015 13:11:34.62 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation General Verbose 6t8f Site lookup is replacing
http://sharepoint.domain.com:80/sites/BizDept/Team/OSHA/_layouts/user.aspx with the alternate access url http://sharepoint.domain.com.
02/23/2015 13:11:34.62 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation General Verbose 6t8g Looking up typical site
http://sharepoint.domain.com:80/sites/BizDept/Team/OSHA/_layouts/user.aspx in web application SPWebApplication Name=org Sharepoint.
02/23/2015 13:11:34.62 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation General Verbose 6t8h Found typical site /sites/BizDept
(96372276-8424-4f7a-9796-b05091a9f2ab) in web application SPWebApplication Name=org Sharepoint.
02/23/2015 13:11:34.62 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Logging Correlation Data Medium xmnv Site=/sites/BizDept
02/23/2015 13:11:34.62 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Database Verbose tkeb Setting database session for {1146e13b-
cb37-43ab-83ce-cbc2e9d34248}.
02/23/2015 13:11:34.62 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Database Verbose tzku ConnectionString: ‘Data
Source=SQLDBSrv.ADdomain.ds\cp008;Initial Catalog=WSS_Content_Sharepoint_BizDept;Integrated Security=True;Enlist=False;Connect Timeout=15′
ConnectionState: Closed ConnectionTimeout: 15
02/23/2015 13:11:34.63 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Database Verbose tkeb Setting database session for {1146e13b-
cb37-43ab-83ce-cbc2e9d34248}.
02/23/2015 13:11:34.63 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nasq Entering monitored scope
(GetWebPartPageContent)
02/23/2015 13:11:34.63 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nasq Entering monitored scope
(GetFileAndMetaInfo)
02/23/2015 13:11:34.63 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Database Verbose tkeb Setting database session for {1146e13b-
cb37-43ab-83ce-cbc2e9d34248}.
02/23/2015 13:11:34.63 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Database Verbose tzku ConnectionString: ‘Data
Source=SQLDBSrv.ADdomain.ds\cp008;Initial Catalog=WSS_Content_Sharepoint_BizDept;Integrated Security=True;Enlist=False;Connect Timeout=15′
ConnectionState: Closed ConnectionTimeout: 15
02/23/2015 13:11:34.63 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose b4ly Leaving Monitored Scope
(GetFileAndMetaInfo). Execution Time=9.83169648656463
02/23/2015 13:11:34.63 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nass ____SQL Query Count=1
02/23/2015 13:11:34.63 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nass ____Execution Time=9.83169648656463
02/23/2015 13:11:34.63 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation General Verbose 9gh2 Usage: Rights and Roles: GetWebPartPage:
Shared
02/23/2015 13:11:34.63 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation General Verbose g3qe GetServerRelativeUrlFromUrl
(http://sharepoint.domain.com/sites/BizDept/_catalogs/masterpage/orgv4.master,True,False)
02/23/2015 13:11:34.63 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation General Verbose g3ql GetUriScheme
(http://sharepoint.domain.com/sites/BizDept/_catalogs/masterpage/orgv4.master)
02/23/2015 13:11:34.63 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation General Verbose g3qf Url starts with http or https
02/23/2015 13:11:34.63 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation General Verbose g3qg fullOrRelativeUrl =
http://sharepoint.domain.com/sites/BizDept/_catalogs/masterpage/orgv4.master
02/23/2015 13:11:34.63 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation General Verbose g3qh Site.Url =
http://sharepoint.domain.com/sites/BizDept
02/23/2015 13:11:34.63 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation General Verbose g3qj url is in site
02/23/2015 13:11:34.63 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose b4ly Leaving Monitored Scope
(GetWebPartPageContent). Execution Time=10.0873155666432
02/23/2015 13:11:34.63 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nass ____SQL Query Count=1
02/23/2015 13:11:34.63 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nass ____Execution Time=10.0873155666432
02/23/2015 13:11:34.63 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation General Verbose narq Releasing SPRequest with allocation Id
{10D2D4F4-1758-4006-9CB9-D1A2EA406867}
02/23/2015 13:11:34.63 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation General Verbose g3qe GetServerRelativeUrlFromUrl
(http://sharepoint.domain.com/sites/BizDept/Team/OSHA/_layouts/user.aspx,True,False)
02/23/2015 13:11:34.63 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation General Verbose g3ql GetUriScheme
(http://sharepoint.domain.com/sites/BizDept/Team/OSHA/_layouts/user.aspx)
02/23/2015 13:11:34.63 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation General Verbose g3qf Url starts with http or https
02/23/2015 13:11:34.63 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation General Verbose g3qg fullOrRelativeUrl =
http://sharepoint.domain.com/sites/BizDept/Team/OSHA/_layouts/user.aspx
02/23/2015 13:11:34.63 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation General Verbose g3qh Site.Url =
http://sharepoint.domain.com/sites/BizDept
02/23/2015 13:11:34.63 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation General Verbose g3qj url is in site
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation General Verbose 6t8b Looking up context site
http://sharepoint.domain.com:80/sites/BizDept/Team/OSHA/_layouts/user.aspx in the farm SharePoint_Config
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation General Verbose 6t8d Looking up the additional information
about the typical site http://sharepoint.domain.com:80/sites/BizDept/Team/OSHA/_layouts/user.aspx.
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation General Verbose 6t8f Site lookup is replacing
http://sharepoint.domain.com:80/sites/BizDept/Team/OSHA/_layouts/user.aspx with the alternate access url http://sharepoint.domain.com.
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation General Verbose 6t8g Looking up typical site
http://sharepoint.domain.com:80/sites/BizDept/Team/OSHA/_layouts/user.aspx in web application SPWebApplication Name=org Sharepoint.
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation General Verbose 6t8h Found typical site /sites/BizDept
(96372276-8424-4f7a-9796-b05091a9f2ab) in web application SPWebApplication Name=org Sharepoint.
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Server Logging Correlation Data Verbose 9gc5 Thread change; resetting
trace level override to 0; resetting correlation to 7e2e3fa9-bece-449a-9442-88833eda4d2a
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Server General Verbose 0000 Looking for a cached value matching 2db94ec5-
f793-4049-aaf0-a4c23537b525 in the Profile Property Cache cache.
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Server General Verbose 0000 Cache hit.
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Server General Verbose 0000 Looking for a cached value matching 2db94ec5-
f793-4049-aaf0-a4c23537b525 in the Profile Property Cache cache.
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Server General Verbose 0000 Cache hit.
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Server General Verbose 0000 Looking for a cached value matching 2db94ec5-
f793-4049-aaf0-a4c23537b525 in the Profile Property Cache cache.
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Server General Verbose 0000 Cache hit.
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Server General Verbose 0000 Looking for a cached value matching 2db94ec5-
f793-4049-aaf0-a4c23537b525 in the Profile Property Cache cache.
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Server General Verbose 0000 Cache hit.
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Server General Verbose 0000 Looking for a cached value matching 2db94ec5-
f793-4049-aaf0-a4c23537b525 in the Profile Property Cache cache.
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Server General Verbose 0000 Cache hit.
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Server General Verbose 0000 Looking for a cached value matching 2db94ec5-
f793-4049-aaf0-a4c23537b525 in the Profile Property Cache cache.
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Server General Verbose 0000 Cache hit.
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Server General Verbose 0000 Looking for a cached value matching 2db94ec5-
f793-4049-aaf0-a4c23537b525 in the Profile Property Cache cache.
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Server General Verbose 0000 Cache hit.
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Server Taxonomy Verbose cn12 Begin: constructor
TaxonomySession.TaxonomySession
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Server Taxonomy Verbose cn13 End: constructor
TaxonomySession.TaxonomySession
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Database Verbose tkeb Setting database session for {1146e13b-
cb37-43ab-83ce-cbc2e9d34248}.
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Database Verbose tzku ConnectionString: ‘Data
Source=SQLDBSrv.ADdomain.ds\cp008;Initial Catalog=WSS_Content_Sharepoint_BizDept;Integrated Security=True;Enlist=False;Connect Timeout=15′
ConnectionState: Closed ConnectionTimeout: 15
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nasq Entering monitored scope
(PortalSiteMapDataSource: Determining Starting Node)
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose b4ly Leaving Monitored Scope
(PortalSiteMapDataSource: Determining Starting Node). Execution Time=0.0287746068285215
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nass ____SQL Query Count=0
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nass ____SPRequest Objects=0
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nass ____Execution Time=0.0287746068285215
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nasq Entering monitored scope
(PortalSiteMapDataSource: Determining Starting Node)
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose b4ly Leaving Monitored Scope
(PortalSiteMapDataSource: Determining Starting Node#1). Execution Time=0.0229079394168812
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nass ____SQL Query Count=0
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nass ____SPRequest Objects=0
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nass ____Execution Time=0.0229079394168812
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nasq Entering monitored scope (Add WebParts)
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Server General Verbose 0000 Looking for a cached value matching 2db94ec5-
f793-4049-aaf0-a4c23537b525 in the Profile Property Cache cache.
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Server General Verbose 0000 Cache hit.
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose b4ly Leaving Monitored Scope (Add WebParts).
Execution Time=0.117612713347646
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nass ____Execution Time=0.117612713347646
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Database Verbose tkeb Setting database session for {1146e13b-
cb37-43ab-83ce-cbc2e9d34248}.
02/23/2015 13:11:34.65 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Database Verbose tzku ConnectionString: ‘Data
Source=SQLDBSrv.ADdomain.ds\cp008;Initial Catalog=WSS_Content_Sharepoint_BizDept;Integrated Security=True;Enlist=False;Connect Timeout=15′
ConnectionState: Closed ConnectionTimeout: 15
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Database Verbose tkeb Setting database session for {1146e13b-
cb37-43ab-83ce-cbc2e9d34248}.
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Database Verbose tzku ConnectionString: ‘Data
Source=SQLDBSrv.ADdomain.ds\cp008;Initial Catalog=WSS_Content_Sharepoint_BizDept;Integrated Security=True;Enlist=False;Connect Timeout=15′
ConnectionState: Closed ConnectionTimeout: 15
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Database Verbose tkeb Setting database session for {1146e13b-
cb37-43ab-83ce-cbc2e9d34248}.
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Database Verbose tzku ConnectionString: ‘Data
Source=SQLDBSrv.ADdomain.ds\cp008;Initial Catalog=WSS_Content_Sharepoint_BizDept;Integrated Security=True;Enlist=False;Connect Timeout=15′
ConnectionState: Closed ConnectionTimeout: 15
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Database Verbose tkeb Setting database session for {1146e13b-
cb37-43ab-83ce-cbc2e9d34248}.
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Database Verbose tzku ConnectionString: ‘Data
Source=SQLDBSrv.ADdomain.ds\cp008;Initial Catalog=WSS_Content_Sharepoint_BizDept;Integrated Security=True;Enlist=False;Connect Timeout=15′
ConnectionState: Closed ConnectionTimeout: 15
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Database Verbose tkeb Setting database session for {1146e13b-
cb37-43ab-83ce-cbc2e9d34248}.
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Database Verbose tzku ConnectionString: ‘Data
Source=SQLDBSrv.ADdomain.ds\cp008;Initial Catalog=WSS_Content_Sharepoint_BizDept;Integrated Security=True;Enlist=False;Connect Timeout=15′
ConnectionState: Closed ConnectionTimeout: 15
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation General Verbose 8nca Application error when access
/_layouts/user.aspx, Error=Object reference not set to an instance of an object. at Microsoft.SharePoint.SPRoleDefinitionCollection.Init()
at Microsoft.SharePoint.SPRoleDefinitionCollection.get_Count() at Microsoft.SharePoint.SPRoleDefinitionCollection.GetByIdNoThrow(Int32 id)
at Microsoft.SharePoint.SPRoleAssignmentCollection.Init() at Microsoft.SharePoint.SPRoleAssignmentCollection.get_Count() at
Microsoft.SharePoint.ApplicationPages.UserRoles.ShowIMNControl() at
Microsoft.SharePoint.ApplicationPages.UserRoles.ConstructUsersDataSource(String usersSortExpression) at
Microsoft.SharePoint.ApplicationPages.UserRoles.ListAnonymousUser(String sortExpression)
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Runtime Unexpected tkau System.NullReferenceException: Object
reference not set to an instance of an object. at Microsoft.SharePoint.SPRoleDefinitionCollection.Init() at
Microsoft.SharePoint.SPRoleDefinitionCollection.get_Count() at Microsoft.SharePoint.SPRoleDefinitionCollection.GetByIdNoThrow(Int32 id) at
Microsoft.SharePoint.SPRoleAssignmentCollection.Init() at Microsoft.SharePoint.SPRoleAssignmentCollection.get_Count() at
Microsoft.SharePoint.ApplicationPages.UserRoles.ShowIMNControl() at
Microsoft.SharePoint.ApplicationPages.UserRoles.ConstructUsersDataSource(String usersSortExpression) at
Microsoft.SharePoint.ApplicationPages.UserRoles.ListAnonymousUser(String sortExpression)
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nasq Entering monitored scope
(EndRequestHandler SharePointEndRequest)
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Server Unified Logging Service Verbose cn4g Trace level override is turned
off.
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose b4ly Leaving Monitored Scope
(EndRequestHandler SharePointEndRequest). Execution Time=0.0416254021111622
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nass ____SQL Query Count=0
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nass ____Execution Time=0.0416254021111622
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nasq Entering monitored scope
(LogRequestUsage)
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Usage Infrastructure Verbose d0i2 Successfully added
requestUsageEntry to CollectUsageData with url http://sharepoint.domain.com/sites/BizDept/Team/OSHA/_layouts/user.aspx
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose b4ly Leaving Monitored Scope
(LogRequestUsage). Execution Time=0.123758745874126
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nass ____SQL Query Count=0
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nass ____Execution Time=0.123758745874126
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nasq Entering monitored scope
(ForceDehydrateHttpContextWorkflows)
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose b4ly Leaving Monitored Scope
(ForceDehydrateHttpContextWorkflows). Execution Time=0.0103365092490805
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nass ____Execution Time=0.0103365092490805
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nasq Entering monitored scope
(EndRequestHandler SPRequest Disposal)
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation General Verbose narq Releasing SPRequest with allocation Id
{16EFF3D3-DBF0-4B70-8F2B-77E434B3D77D}
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation General Verbose narq Releasing SPRequest with allocation Id
{8EFE7AF0-BD11-44A3-8DDC-80C89308B3C0}
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose b4ly Leaving Monitored Scope
(EndRequestHandler SPRequest Disposal). Execution Time=0.395022272383781
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nass ____SQL Query Count=0
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nass ____Execution Time=0.395022272383781
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Usage Infrastructure Verbose d0hz Starting write trace for type
Microsoft.SharePoint.Administration.SPRequestUsageEntry with correlationID 7e2e3fa9-bece-449a-9442-88833eda4d2a
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Usage Infrastructure Verbose d0i0 Successful wrote trace for
type Microsoft.SharePoint.Administration.SPRequestUsageEntry with correlationID 7e2e3fa9-bece-449a-9442-88833eda4d2a
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Medium b4ly Leaving Monitored Scope (Request
(GET:http://sharepoint.domain.com:80/sites/BizDept/Team/OSHA/_layouts/user.aspx)). Execution Time=59.1561217976028
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nass ____SPRequest Objects=3
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nass ____SQL Query Count=8
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nass ____Execution Time=59.1561217976028
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nass ____Current User=
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nass ____WebPart Events Offsets=0
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nass ____Service Calls=0
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nass ____Page Checkout Level=Published
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nass ____Current SharePoint Operations=1
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nass ____Critical Events=0
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Monitoring Verbose nass ____Log Correlation Id=7e2e3fa9-bece-
449a-9442-88833eda4d2a
02/23/2015 13:11:34.66 w3wp.exe (SPWFE03:0x2430) SharePoint Foundation Logging Correlation Data Verbose 77a3 Ending correlation.
02/23/2015 13:12:08.42 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Logging Correlation Data Verbose 77a3 Starting correlation.
02/23/2015 13:12:08.42 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Logging Correlation Data Verbose 77a3 Starting correlation.
Transfer from 7e2e3fa9-bece-449a-9442-88833eda4d2a
02/23/2015 13:12:08.42 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Logging Correlation Data Medium xmnv Name=Request
(GET:http://sharepoint.domain.com:80/sites/BizDept/Team/OSHA)
02/23/2015 13:12:08.42 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose nasq Entering monitored scope
(BeginRequestHandler)
02/23/2015 13:12:08.42 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation SQM Verbose 97qu SQM: Datapoint id 6693 marked as Increment
datapoint.
02/23/2015 13:12:08.42 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose b4ly Leaving Monitored Scope
(BeginRequestHandler). Execution Time=0.105879378524366
02/23/2015 13:12:08.42 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose nass ____SQL Query Count=0
02/23/2015 13:12:08.42 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose nass ____Execution Time=0.105879378524366
02/23/2015 13:12:08.42 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose nasq Entering monitored scope
(PostAuthenticateRequestHandler)
02/23/2015 13:12:08.42 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Runtime Verbose 0000 Value for isAnonymousAllowed is : False
02/23/2015 13:12:08.42 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Runtime Verbose 0000 Value for checkAuthenticationCookie is :
False
02/23/2015 13:12:08.42 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose b4ly Leaving Monitored Scope
(PostAuthenticateRequestHandler). Execution Time=0.114260331969566
02/23/2015 13:12:08.42 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose nass ____SQL Query Count=0
02/23/2015 13:12:08.42 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose nass ____Execution Time=0.114260331969566
02/23/2015 13:12:08.42 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Logging Correlation Data Medium xmnv User=ADdomain
\SPServiceAcct
02/23/2015 13:12:08.42 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose nasq Entering monitored scope
(PostResolveRequestCacheHandler)
02/23/2015 13:12:08.42 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose b4ly Leaving Monitored Scope
(PostResolveRequestCacheHandler). Execution Time=0.177955578153089
02/23/2015 13:12:08.42 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose nass ____SQL Query Count=0
02/23/2015 13:12:08.42 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose nass ____Execution Time=0.177955578153089
02/23/2015 13:12:08.42 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Logging Correlation Data Verbose 77a3 Starting correlation.
02/23/2015 13:12:08.42 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation General Medium af71 HTTP Request method: GET
02/23/2015 13:12:08.42 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation General Verbose af78 HTTP request cookie header:
NSC_bqq_p_TibsfQpjou_2010efgbvmu=ffffffffaf181bfa45525d5f4f58455e445a4a423660;
NSC_JO5jz23kdn1zi2acp25j5meonns0hdu=ffffffffaf181bf845525d5f4f58455e445a4a423660;
NSC_JOsj31a2bqjfao3eca0phxejkfr25eu=ffffffffaf181bf845525d5f4f58455e445a4a423660; OfflineClientInstalled=0;
NSC_JOjyn5j2cskk31dbricap1ce0bhxhct=ffffffffaf181bfa45525d5f4f58455e445a4a423660;
NSC_JOeljtnxb5hajavex42mgabskieebdu=ffffffffaf181bfb45525d5f4f58455e445a4a423660; SPSessionGuid=7e2e3fa9-bece-449a-9442-88833eda4d2a
02/23/2015 13:12:08.42 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation General Medium af75 Overridden HTTP request method: GET
02/23/2015 13:12:08.42 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation General Medium af74 HTTP request URL: /sites/BizDept/Team/OSHA
02/23/2015 13:12:08.42 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation General Verbose 6t8b Looking up context site
http://sharepoint.domain.com/sites/BizDept/Team/OSHA in the farm SharePoint_Config
02/23/2015 13:12:08.42 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation General Verbose 6t8d Looking up the additional information
about the typical site http://sharepoint.domain.com/sites/BizDept/Team/OSHA.
02/23/2015 13:12:08.42 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation General Verbose 6t8f Site lookup is replacing
http://sharepoint.domain.com/sites/BizDept/Team/OSHA with the alternate access url http://sharepoint.domain.com.
02/23/2015 13:12:08.42 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation General Verbose 6t8g Looking up typical site
http://sharepoint.domain.com/sites/BizDept/Team/OSHA in web application SPWebApplication Name=org Sharepoint.
02/23/2015 13:12:08.42 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation General Verbose 6t8h Found typical site /sites/BizDept
(96372276-8424-4f7a-9796-b05091a9f2ab) in web application SPWebApplication Name=org Sharepoint.
02/23/2015 13:12:08.42 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Database Verbose tkeb Setting database session for {1146e13b-
cb37-43ab-83ce-cbc2e9d34248}.
02/23/2015 13:12:08.42 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Database Verbose tzku ConnectionString: ‘Data
Source=SQLDBSrv.ADdomain.ds\cp008;Initial Catalog=WSS_Content_Sharepoint_BizDept;Integrated Security=True;Enlist=False;Connect Timeout=15′
ConnectionState: Closed ConnectionTimeout: 15
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Logging Correlation Data Verbose 77a3 Ending correlation.
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose nasq Entering monitored scope
(PostRequestExecuteHandler)
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose b4ly Leaving Monitored Scope
(PostRequestExecuteHandler). Execution Time=0.0106158743639206
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose nass ____SQL Query Count=0
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose nass ____Execution Time=0.0106158743639206
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose nasq Entering monitored scope
(EndRequestHandler SharePointEndRequest)
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Server Logging Correlation Data Verbose 9gc5 Thread change; resetting
trace level override to 0; resetting correlation to 7af19893-350d-4082-a271-ce814dc1d34f 7e2e3fa9-bece-449a-9442-88833eda4d2a
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Server Unified Logging Service Verbose cn4g Trace level override is turned
off.
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose b4ly Leaving Monitored Scope
(EndRequestHandler SharePointEndRequest). Execution Time=0.138565096960647
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose nass ____SQL Query Count=0
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose nass ____Execution Time=0.138565096960647
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose nasq Entering monitored scope
(LogRequestUsage)
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Usage Infrastructure Verbose d0i2 Successfully added
requestUsageEntry to CollectUsageData with url http://sharepoint.domain.com/sites/BizDept/Team/OSHA
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose b4ly Leaving Monitored Scope
(LogRequestUsage). Execution Time=0.112304776165686
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose nass ____SQL Query Count=0
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose nass ____Execution Time=0.112304776165686
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose nasq Entering monitored scope
(ForceDehydrateHttpContextWorkflows)
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose b4ly Leaving Monitored Scope
(ForceDehydrateHttpContextWorkflows). Execution Time=0.0106158743639206
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose nass ____Execution Time=0.0106158743639206
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose nasq Entering monitored scope
(EndRequestHandler SPRequest Disposal)
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose b4ly Leaving Monitored Scope
(EndRequestHandler SPRequest Disposal). Execution Time=0.0203936533833211
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose nass ____SQL Query Count=0
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose nass ____Execution Time=0.0203936533833211
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Usage Infrastructure Verbose d0hz Starting write trace for type
Microsoft.SharePoint.Administration.SPRequestUsageEntry with correlationID 7af19893-350d-4082-a271-ce814dc1d34f
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Usage Infrastructure Verbose d0i0 Successful wrote trace for
type Microsoft.SharePoint.Administration.SPRequestUsageEntry with correlationID 7af19893-350d-4082-a271-ce814dc1d34f
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Medium b4ly Leaving Monitored Scope (Request
(GET:http://sharepoint.domain.com:80/sites/BizDept/Team/OSHA)). Execution Time=12.0168904148432
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose nass ____SPRequest Objects=0
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose nass ____SQL Query Count=0
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose nass ____Execution Time=12.0168904148432
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose nass ____Current User=
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose nass ____WebPart Events Offsets=0
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose nass ____Service Calls=0
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose nass ____Page Checkout Level=Published
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose nass ____Current SharePoint Operations=0
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose nass ____Critical Events=0
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Monitoring Verbose nass ____Log Correlation Id=7af19893-350d-
4082-a271-ce814dc1d34f
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Logging Correlation Data Verbose 77a3 Ending correlation.
Transfer to 7e2e3fa9-bece-449a-9442-88833eda4d2a
02/23/2015 13:12:08.43 w3wp.exe (SPWFE01:0x2B9C) SharePoint Foundation Logging Correlation Data Verbose 77a3 Ending correlation.

 

Details

SharePoint Backups for t he subsite fail as well. If you try the following PowerShell to backup a subsite, it throws error

Export-SPWeb -identity http://sharepoint.domain.com/sites/Biz/Dept/Team -path \\SharePointServer01\Bkup\Team -NoFileCompression -IncludeVersions 4 -IncludeUserSecurity -UseSQLSnapshot

 

Resolution

The issue is due to SharePoint permissions for the site. Un-break the permissions using SharePoint PowerShell i.e inherit the permissions at the subsite level where this issue is happening.

$web=get-spweb http://sharepoint.domain.com/sites/Biz/Dept/Team
$web.ResetRoleInheritance()
$web.update()

Later go in to the subsite and break the permissions and add the sitename groups with permissions. You may have to add other custom SharePoint groups or Active Directory groups or direct users that had access at that subsite.

 

References

  1. http://dereksan.blogspot.com/2011/02/sharepoint-20072010an-unexpected-error.html
  2. http://leejghardy.com/2014/06/13/sharepoint-my-site-an-unexpected-error-has-occurred-after-installing-cumulative-update/
  3. https://support.microsoft.com/en-us/kb/2970281
  4. https://absolute-sharepoint.com/2013/12/unexpected-error-occurred-user-clicks-settings-access-mysites.html
  5. http://www.experts-exchange.com/questions/27553894/An-unexpected-error-has-occurred-SharePoint-2010.html
  6. http://stackoverflow.com/questions/1997803/an-unexpected-error-has-occurred

InfoPath cannot save the following form Error

Sunday, May 1st, 2016

InfoPath cannot save the following form

V: 1.0

Issue

You try to publish InfoPath form to SharePoint from a Windows Server and you get the following error:

Infopath cannot save the following form: http://sharepoint/formsLibrary
This document library was either renamed or deleted, or network problems are preventing the file from being saved. If this problem persists, contact your network administrator.

InfoPath Publish Error KB2752612

Cause

Desktop experience feature is not installed on Windows Server by default.

 

Solution

On Windows Server, use Server Manager and install the Desktop Experience feature. The feature is under ‘User Interfaces and Infrastructure’. Reboot the server after adding the feature. After the reboot, you should be able to publish the InfoPath form from the Windows Server. This issue doesn’t happen if you are publishing from the Windows client operating systems.

 

InfoPath Publish Error KB2752612 DesktopExp Feature

 

Softvative Logo

Database is up to date, but some sites are not completely upgraded

Saturday, April 2nd, 2016

Database is up to date, but some sites are not completely upgraded

Version: 1.0, Updated 03/22/2016

Applies to: SharePoint and Project Server PPM 2010, 2013, 2016

Scenario:

You review the SharePoint Central Administration site for Servers and database statuses and notice below messages:

Server Status: Upgrade Required

Central Admin Site > System Settings > Manage servers in this farm

SP2013_SomeSiteNotUpgraded_01A

 

Database Status: Database is up to date, but some sites are not completely upgraded

Cental Admin Site > Upgrade and Migration > Review Database Status.

SP2013_SomeSiteNotUpgraded_01b

 

Resolution:

First lets try to find out which site is causing that error.

  1. On one of the SharePoint / Project Server PPM server, open command prompt with elevated permissions.
  2. Go to SharePoint Bin folder c:\Program Files\Microsoft Shared\Web Server Extensions\15\Bin\ [the two digit folder name for SharePoint 2010 = 14, 2013 = 15, 2016 = 16]
  3. Type STSAdm command and use pipe to export it to a text file: stsadm.exe -o localupgradestatus > e:\UpgradeStatus.txt  SP2013_SomeSiteNotUpgraded_02 
  4. After executing the command, open the UpgradeSTatus.txt file exported in previous step. Search the text file for the status Needs Upgrade. Those sections will list the site name in question. You can see in the image below that the site name is listed.SP2013_SomeSiteNotUpgraded_03
  5. Go to the bottom of this UpgradeStatus.txt file and you will see overall status of content database(s), Site collection(s) or objects that may need upgrade.SP2013_SomeSiteNotUpgraded_04
  6. In Review Database Status page we saw the name of database(s) that had the status with the error message (second image on the top). Open PowerShell with elevated rights and run the following commands: Get-SPContentDatabase -Identity wss_epm_content [where wss_epm_content is the name of the content database]. That will give us the database ID that we’ll use in next command to upgrade the database.SP2013_SomeSiteNotUpgraded_05
  7. Now run the PowerShell command: Upgrade-SPContentDatabase -Identity GUID# [where GUID# is the ID we got from previous step]. Click Y or A to confirm the command execution. SP2013_SomeSiteNotUpgraded_06
  8. Now go to Manage Servers in the Farm and Review Database Status pages and check the status. The Servers page will still show ‘Upgrade Required’ status. The database page will not show error this time and instead will show ‘No Action Required’ message. SP2013_SomeSiteNotUpgraded_07  SP2013_SomeSiteNotUpgraded_08
  9. Run the stsadm command again and export the status with a new file name UpgradeStatus2.txt. stsadm.exe -o localupgradestatus > e:\UpgradeStatus2.txt. Review the file after command executes and you will find that none of the database, site Collection or object need upgrade this time. SP2013_SomeSiteNotUpgraded_09
  10. At this point, run either the SharePoint Configuration Wizard GUI or run the command line option. SP2013_SomeSiteNotUpgraded_10 Run the PowerShell command on each server in the farm one at a time. PSConfig.exe -cmd upgrade -inplace b2b -wait -cmd applicationcontent -install -cmd installfeatures -cmd secureresourcesSP2013_SomeSiteNotUpgraded_11
  11. After executing the command on all servers, go to the Central Admin site and review the status of servers in the farm. All the servers should have ‘No Action Required’ as the status. SP2013_SomeSiteNotUpgraded_13

 

 

References:

  1. Sharepoint Troubleshooting: Data base is Up to date but some sites are not completely upgraded
  2. Data base is Up to date but some sites are not completely upgraded
  3. sharepointdiary – Database is up to date, but some sites are not completely upgraded
  4. Stefan Gossner – Why I prefer PSCONFIGUI.EXE over PSCONFIG.EX

 

BDC Database is in compatibility range and upgrade is recommended

Friday, February 19th, 2016

Database is in compatibility range and upgrade is recommended

V: 1.1

Issue

Your apply a Cumulative Update (CU) for SharePoint or Project Server PPM. After the update deployment you run the SharePoint Configuration Wizard to update the farm to new patch version. Now you go to Central Administration > Upgrade and Migration > Review Database Status. You will find that the status of Business Data Connectivity (BDC) database shows the message:

Database is in compatibility range and upgrade is recommended 

SP2013_BDC_In_Compatibility_Range_01

SP2013 BDC In Compatibility Range 01

Even running the SharePoint Configuration Wizard again will not fix this issue.

Resolution

The databases should not be left in the compatibility range for long. To resolve this issue for BDC service application, run the following Power Shell commands from one of the SharePoint server. Launch Power shell with elevated admin rights.

 

(Get-SPDatabase | ?{$_.type -eq “Microsoft.SharePoint.BusinessData.SharedService.BdcServiceDatabase”}).Provision()

SP2013_BDC_In_Compatibility_Range_02

SP2013 BDC In Compatibility Range 02

BDC database should be in good state now. Go to SharePoint Central Administration > Upgrade and Migration > Review Database Status and review the status for BDC database.

SP2013 BDC In Compatibility Range 03

SP2013_BDC_In_Compatibility_Range_03

References

  1. SharePoint Updates – CU Updates
  2. Project Server Updates – CU Updates

Best Practices on using OneNote with SharePoint

Monday, January 18th, 2016

Best Practices on using OneNote with SharePoint

Version: 1.1, Modified Date: 01/19/2016

Scenario:
There are few other ways to use Microsoft OneNote with SharePoint. For this scenario, assume that you didn’t deploy Office Web App 2013, a server product that allows browser based Onenote editing / updates.

SharePoint Online (part of Office 365) has Onenote syncing features by default enabled.SharePoint and OneNote There is a way to use Microsoft OneNote with SharePoint Server 2013 on-premises version.

1. Click on the gear on top right and choose Add an App
2. Click on Documents Library app
3. Click on Advanced Option link on ‘Adding Document Library’ dialog box
4. Enter name e.g ‘ProjectNotes’ and other information for the library. Choose ‘Microsoft OneNote 2010 Notebook’ under Document Template drop down
5. Click Create
6. Copy the URL address for the OneNote Library you just created

That will create a library specifically for OneNote. Now go into that library and follow steps listed below:

1. Click on Files ribbon tab on top left
2. Click on the New Document icon on the ribbon.
3. Click Allow if prompted to allow website to open program
4. That will bring Unpack OneNote window.
5. Enter name for workbook. In Path field, enter the path of your OneNote Library that you created in step 4 of first section.
6. Click Create button
7. Create OneNote pages, sections etc as you normally like to organize information in your OneNote workbook
8. OneNote will Sync the changes back to the Site’s OneNote library
9. In OneNote 2013 / 365 on desktop, click on File > Info to view your workbook showing SharePoint Site URL and not the local path.
10. Click the ‘View Sync Status’ button there to see the sync status

 

More to come in next version of this post.

Six Steps to Remove Project Server from SharePoint Farm

Tuesday, December 22nd, 2015

Six Steps to Remove Project Server from SharePoint Farm

Version: 1.0, Last Modified: 12/22/2015

Applies to: Project Server 2010, Project Server 2013

Microsoft Project Server PPM relies on SharePoint Farm for the base architecture. There are situations where you have to remove Project Server from the farm. The situation could be due to erroneous servers, Farm or the data might have been migrated over to next version and you need to decommission just the Project Server from the farm.

I’ll take the example of  SharePoint / Project Server 2010 farm. Following are the high level steps needed to remove Project Server:

  1. Delete Project Web App (PWA) 2010 instance
  2. Delete Project Server 2010 Service Application
  3. Delete Web Application for Project Web App 2010
  4. Stop ‘Project Application Service’ on each server in the Farm
  5. Remove custom Solutions related to PPM
  6. Other configuration items that may need removal / release from config books

CAUTION – Don’t remove Project Server software bits. Doing so will cause the whole farm to go in a bad state.

 

1 Delete Project Web App (PWA) 2010 instance

Follow the steps to delete the PWA instance.

  1. Go to SharePoint Central Administration > Manage Service Applications.
  2. Click on Project Server Service Application name.
  3. That will bring you to ‘Manage Project Web App sites’ page. Hover over the Project Web App (PWA)  instance and click on the drop down menu on the right. Choose Delete option.

    SharePoint 2010 Unprovision Project Server PWA 2010

    SharePoint 2010 Unprovision Project Server PWA 2010

  4. Review the information on next page and hit the delete button

    SharePoint 2010 Unprovision Project Server PWA 2010 b

    SharePoint 2010 Unprovision Project Server PWA 2010 b

  5. You will be back to Manage Project Web App Sites page after instance is deleted.

    SharePoint 2010 Unprovision Project Server PWA 2010 c

    SharePoint 2010 Unprovision Project Server PWA 2010 c

 

2 Delete Project Server 2010 Service Application

Follow the steps to delete the Project Server Service Application.

  1. Go to SharePoint Central Administration > Manage Service Applications.
  2. Click anywhere in the row for Project Server Service Application except the name to highlight the service application.
  3. Click the delete button on the top ribbon

    SharePoint 2010 Delete Project Server Service Application

    SharePoint 2010 Delete Project Server Service Application

  4. On ‘Delete Service Application‘ dialog box, check the box ‘Delete data associated with the Service Application‘ and click Ok button

    SharePoint 2010 Delete Project Server Service Application b

    SharePoint 2010 Delete Project Server Service Application b

  5. Project Server Service application will be deleted.

 

3 Delete Web Application for Project Web App 2010

Now delete the web application including its content database and IIS Website by following step below:

  1. Go to SharePoint Central Administration >  Manage Web Applications
  2. Click on Web Application that hosted the PWA. Make sure there are no other site collection that may have been created besides /PWA site collection.
  3. Click on the Delete drop down button in the ribbon and then choose Delete Web Application
  4. Under ‘Delete Web Application’ dialog box, check Yes for ‘Delete content database’ and for ‘Delete IIS web sites’

    SharePoint 2010 Delete PWA Web App

    SharePoint 2010 Delete PWA Web App

  5. Click the Delete button
  6. The web application including its Content Database from SQL Server and IIS website will be deleted.

 

4 Stop ‘Project Application Service’ on each server in the Farm

Follow the steps below.

  1. Go to SharePoint Central Admin > Manage Servers in this Farm.
  2. Click on one of the Server name that is running ‘Project Application Service’
  3. On the next page, click stop link on the right of ‘Project Application Service’. That will stop the two windows services console services for Events and Queue. The service will show Stopped status.

    SharePoint 2010 Stop Project Server Service

    SharePoint 2010 Stop Project Server Service

  4. Switch to other server(s) in the farm and perform the same steps to stop the service.

 

5 Remove custom solutions related to PPM

Remove any custom solutions that might have been deployed for the PPM. Go under System Settings > Manage Farm Solutions and remove those solutions. You may have to review and update the web.config file for other web applications.

 

6 Other configuration items that may need removal / release from config books:

  1. Load Balancer Virtual IP (VIP) and configurations related to PWA Web App
  2. Remove DNS entries if the PWA Web App name is no longer needed
  3. Release the IP configuration that may have been reserved for PWA
  4. Remove the PWA Web App from the SharePoint Search Content Source and other configurations
  5. Remove the PWA related Service Accounts that may not be needed
  6. Remove the Active Directory Kerberos SPN that are no longer valid under the service accounts
  7. Remove any SSL certificates related to PWA
  8. Remove any IIS Application Pools that may not be needed
  9. Any firewall / proxy configuration updates
  10. Removing / upgrading older versions of MS Project Professional

 

After all these removal steps, you should be fine. Don’t try to uninstall the Project Server software bits on the servers. That will cause your farm to go worst.

 

References:

  1. Uninstall Project Server from SharePoint Farm
  2. How do you remove a server from the SharePoint 2010 Farm which includes Project Server 2010
  3. Uninstalling Project Server from a farm? Don’t forget to run PSConfig!
  4. Deleting a Project Service Application within SharePoint 2010

Protected: Custom Page Layouts for Wiki Pages

Monday, December 14th, 2015

This content is password protected. To view it please enter your password below:

Configure SharePoint 2013 Hostname based User Profile Service Application

Friday, November 27th, 2015

Configure SharePoint 2013 Hostname based User Profile Service Application

Scenario: All Service Application configured except UPS.

  1. Have a cname record that redirect to existing My.svdomain.com Citrix LB VIP
  2. Create a new Web App with host header set to My.svdomain.com and using Farm admin account for App Pool
  3. Create a Quota Template with 5000 MB limit and 4000 MB warning
  4. Create a root site collection using ‘My Site Host’ template
  5. Go to CA > Manage Services on Server and start:
    1. User Profile Service on one app and two WFE servers
  6. Create User Profile Service Application
    1. SA Name: User Profile Service Application
    2. App Pool: SharePoint Web Services System
    3. Use PPMTest_ as prefix for databases name
    4. Profile Sync Instance: SPAppSrv01
    5. Mysite Host URL: http://My.svdomain.com
    6. MySite Managed Path: /personal
  7. Go to CA > Manage Services on server and turn on User Profile Synchronization Service on one App server. Enter the password for the service account there
    • That will enable two Forefront services in Windows Services console
      • Forefront Identity Manager Service
      • Forefront Identity Manager Synchronization Service
  8. Go back to Manage Service Application > User Profile SA Properties and make sure the Profile Sync instance has the correct server selected and click cancel.
  9. Make sure Service Account (Farm account) has permissions under User Profile SA > Administrators.
  10. Go to User Profile Service Application configure:
    1. Under My Site Settings > Setup My Sites: Under Email notifications, enter My_Sharepoint@svdomain.com as the sender email
    2. Under Configure Synchronization Connections, click ‘Create new connection’ to setup AD connection for profile sync.
      1. Connection Name: svdomain UserProfile ADSync Test
      2. Forest Name: svdomain.ds
      3. Account Name: svdomain\FarmAdmin
      4. Pass: Yourpass
      5. Populate Containers and select the AD OU levels to sync with.
        • svdomain.com
        • Main
          • Admin – checked
          • App – checked
          • Contacts – checked
          • Groups – checked
          • Journaling – checked
          • Users – [Check then uncheck these sub levels]
            • Migrated Users
          • Termed Accounts – checked
          • Users – checked
    3. Click on AD Connection Name and from dropdown choose ‘Edit Connection Filters’. Add user filter for userAccountControl Bit on equal 2. Click OK
  11. Review the Forefront Identity Manager client “C:\Program Files\Microsoft Office Servers\15.0\Synchronization Service\UIShell\miisclient.exe”
  12. Go to User Profile Service Application > Synchronization > Start Profile Synchronization. Perform a full sync. In case the profiles are not imported, review the FIM client for error.
  13. Assign AD Replicate Directory changes permissions to SharePoint account used in User Profile SA (Farm Admin)
  14. Reboot the servers if needed.

 

References:
  1.  https://technet.microsoft.com/en-us/library/hh296982.aspx
  2. User profile properties and profile synchronization planning worksheets for SharePoint Server 2013
  3. Plan user profiles in SharePoint Server 2013
  4. Planning worksheets for SharePoint 2013
  5. Grant Active Directory Domain Services permissions for profile synchronization in SharePoint Server 2013
  6. Administer the User Profile service in SharePoint Server 2013
  7. Plan profile synchronization for SharePoint Server 2013 – Active Directory Domain Services
  8. FIM 2010 Technical Overview
  9. Creating User Profile Synchronization Exclusion Filters using the userAccountControl attribute
  10. Connection filter data types and operators in SharePoint Server 2013
  11. SharePoint 2013: User Profile Syncronization – Direct Active Directory Import
  12. First Look: SharePoint Server 2013 Active Directory Import
  13. Required User Profile Synchronization Permissions in Active Directory for SharePoint 2010

SharePoint HTTP 400 Bad Request Error

Sunday, November 22nd, 2015

SharePoint and HTTP 400 Bad Request Error

V: 1.0

Scenario

Users go to SharePoint site and get HTTP 400 Error. They may be able to see partial page but in most cases will get the error on all the sites.

SP2010_HTTP400_BadRequest_Error

 

The error is consistent between Internet Explorer and Chrome browsers. Go to Internet Explorer Tool > Internet Options > Advanced tab and uncheck the option ‘Show friendly HTTP error messages‘. Click OK.

SP2010_HTTP400_BadRequest_Error_IEUncheckOption

Internet Explorer HTTP Error messages option

 

Then refresh the page and you will see the error details.

HTTP 400 – Bad Request (Request Header Too Long)

 

Cause

The issue can happen if a user is part of too many Active Directory groups. Too many groups can increase the Kerberos authentication token size.  The HTTP request sent to IIS web server will be rejected by IIS and users get this error.

SP2010_HTTP400_BadRequest_TooManyADGrps

Active Directory Users and Computer Management – User Account Properties

 

Note: Active Directory uses Kerberos protocol.

 

Resolution

There are two options. Either remove extra AD groups from the user’s AD account or configure the registry settings on IIS (Internet Information Server) web servers.

Registry loaction on IIS web servers:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters

Set values for MaxFieldLength and MaxRequestBytes registry keys.

Name Value Type Value Data
MaxFieldLength DWORD 65534
MaxRequestBytes DWORD 16777216

 

Registry file contents. Save below as .reg file and run on servers.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HTTP\Parameters]
“MaxFieldLength”=dword:00065534
“MaxRequestBytes”=dword:16777216

 

Click here to Download registry file

 

After theses settings, restart your servers. In case of SharePoint, I recommend to apply this setting on all WFE and App servers in the farm.

 

References:

  1. “HTTP 400 – Bad Request (Request Header too long)” error in Internet Information Services (IIS)
  2. Problems with Kerberos authentication when a user belongs to many groups

Keywords:

  • HTTP 400 error in SharePoint
  • HTTP 400 on sharepoint page and site
  • SharePoint Bad Request error

 

Setup Workflow Manager on SharePoint 2013

Tuesday, November 10th, 2015

V: 1.0

Full video on Workflow Manager 1.0 deployment for SharePoint 2013 or Project Server 2013 is at the bottom of this article.

 

  1. Download Workflow Manager 1.0 and run WorkflowManager.exe (94 KB)
  2. Click Option and uncheck Customer Experience setting
  3. On the Workflow Manager Configuration Wizard page, click Advanced button.
    1. Enter SQL Server name. A highly available SQL Server setup will help the Workflow Manager database availability as well. Use SQL Server Availability Group during Workflow Manager config. Like SQLAG\MSSQLServer,1464
    2. Configure database names for (default name listed below):
      1. Farm Management DB: WFManagementDB
      2. Instance Management DB: WFInstanceManagementDB
      3. Resource Management DB: WFResourceManagementDB
    3. Configure Service Account. Use SP Farm Account
    4. Leave Configure Certificates to Auto-Generate
      1. Use SP2013 as the ‘Certificate Generate Key’ [use a secure key instead of words ‘SP2013’ in production]
    5. Configure Ports
      1. Workflow Manager Management Port: 12290
      2. HTTP Port: 12291
    6. Check the box “Allow Workflow management over HTTP on this computer”
    7. Configure Admin Group (gets access to all DBs): Leave BUILTIN\Administrators
  4. Service Bus Configuration
    1. Farm Management DB: SbManagementDB
    2. Gateway DB: SbGatewayDatabase
    3. Message Container DFB: SBMessageContainer01
    4. Check the box under ‘Configure Service account’ to use same account as used in Workflow Manager config.
    5. Under ‘Configure Certificate’ section use Auto-Generate and check the box to use same certificate generation key as was used for Workflow Manager.
    6. Under Configure Ports use:
      1. HTTPS Port: 9355
      2. TCP Port: 9354
      3. Message Broker: 9356
      4. Internal Communication Port Range: 9000
    7. Configure Admin Group (gets access to all DBs): Leave BUILTIN\Administrators
  5. Review Summary page of the wizard, save the summary using copy and PowerShell options and then click Apply check mark icon on bottom right. That will start the configurations.
  6. At the end of Configuration, click on View Log link to review and save the log. then click on check mark at the bottom to close the wizard.
  7. Exit the Web platform Installer.
  8. Review the database server. You should see 6 new databases.
  9. Review IIS for Workflow Manager Site. Make sure you can get to http://servername:12291 site address for non-SSL: https://servername:12290 for SSL enabled site. You may need to have a DNS address / Load balancer configuration for Workflow URL, if you plan on using multiple servers in the same farm with Workflow Manager.
  10. Review SharePoint Central Admin > Manage Service Applications page to review ‘Workflow Service Application’.
  11. Open SharePoint Management PowerShell with run As admin. Enter following command to connect SP and Workflow Manager.
    • Single Server with HTTP
      Register-SPWorkflowService -SPSite “http://Sharepoint.SVdomain.com” -WorkflowHostUri “http://SPWFE1:12291” -AllowOAuthHttp
    • With DNS FQDN through Citrix Netscaler / Load Balancer
      Register-SPWorkflowService -SPSite “http://Sharepoint.SVdomain.com” -WorkflowHostUri “http://Sharepoint.SVdomain.com:12291” –
      AllowOAuthHttp -forceNote:
      -force parameter will override the previous setting.MSP2013_WorkflowManager_with_FQDN_via_LB_WO_Persistence
  12. Go back to SharePoint Central Admin site > Manage Service Applications > Workflow Service Application. You should see
    ‘Workflow is Connected’ message confirming the workflow manager is connected to SharePoint.
  13. Go to SharePoint Designer, connect to a site and try to create new site workflow. Review the dropdown option for SharePoint 2013 workflow option.

 

To verify the Workflow Manager Deployment

Go to SharePoint Central Administration > Manage Service Applications > Click on Workflow Service Application. If you see the following message, then Workflow Manager is not registered with the SharePoint. You will see Workflow is connected message if the workflow manager is setup correctly with SharePoint.

MSP2013_WorkflowManager_Installed_SP_Serviceapp_NotConnected

 

b. Go to the Workflow Manager URL from one of the SharePoint server. If you get the response, then it is working.

MSP2013_WorkflowManager_with_FQDN_via_LB_WO_Persistence_IE

 

Review the Workflow Changes in SharePoint Designer

In SharePoint 2013 (or Project Server 2013) launch SharePoint Designer, connect to a site and create a new workflow and you will notice that only SharePoint 2010 workflow type is an option. That is due ti missing Workflow Manager setup in the farm.

PPM2013_Dev_SPD_2013WorkflowsNotAvailable

 

Setup Workflow Manager, register it in the SharePoint 2013 farm and then review the SharePoint Designer 2013 Platform Type option. You will notice SharePoint 2013 Workflow as an option. If you will be connected to Project Server 2013 PPM site, you will notice Project Server 2013 as additional option.

PPM2013_Dev_SPD_Showing_Workflows_for_3_Platforms

 

Softvative Video – Workflow Manager 1.0 for SharePoint 2013 / Project Server 2013

 

Softvative Logo

References:

  1. Install and configure workflow for SharePoint Server 2013
  2. Download Workflow Manager 1.0
  3. Video series: Install and configure Workflow in SharePoint Server 2013
  4. Installing and Configuring Workflow Manager 1.0
  5. Configure workflow in SharePoint Server 2013
  6. Service Bus 1.0 for Windows Server – Architecture Overview