Brent's (Mis-?)Adventures in SharePoint Land https://docs.microsoft.com/archive/blogs/brent/feed.xml Wed, 17 Apr 2019 03:24:13 GMT en-US hourly 1 SharePoint 2010 - User Profile Sync and Business Connectivity Services (BCS) https://docs.microsoft.com/archive/blogs/brent/sharepoint-2010-user-profile-sync-and-business-connectivity-services-bcs Fri, 14 Jan 2011 11:43:06 GMT https://blogs.technet.microsoft.com/brent/2011/01/14/sharepoint-2010-user-profile-sync-and-business-connectivity-services-bcs/ There are a lot of times that people ask about how SharePoint 2010's User Profile Sync service works and how BCS works to compliment/enhance our User Profiles.   I wanted to share this blog entry as it does a fantastic job of describing the conceptual view of what our User Profile Sync 'looks like' and how BCS plugs into it.

https://blogs.msdn.com/b/spsocial/archive/2010/05/04/conceptual-view-of-how-user-profile-synchronization-works-in-sharepoint-2010.aspx

 

]]> SharePoint 2010 Ratings Synchronization Timer Job errors in Publishing/Consuming MultiFarm Configuration https://docs.microsoft.com/archive/blogs/brent/sharepoint-2010-ratings-synchronization-timer-job-errors-in-publishingconsuming-multifarm-configuration Tue, 11 Jan 2011 07:04:40 GMT https://blogs.technet.microsoft.com/brent/2011/01/11/sharepoint-2010-ratings-synchronization-timer-job-errors-in-publishingconsuming-multifarm-configuration/ Consider the following scenario:

SharePoint 2010 is configured to consume the User Profile Service from a separate SharePoint 2010 farm.

In this scenario, you find errors like the following in the Publishing Farm's ULS log files:

-----------------------------------
OWSTIMER.EXE (0x1604)                              0x1718  SharePoint Foundation                 General                                       
6t8b       Verbose               Looking up  site https://ConsumingFarm/News/Pages/RatedPage.aspx in the farm SharePoint_Config   f19c8895-b179-4f07-8a5e-e343f3d81fe7

OWSTIMER.EXE (0x1604)                              0x1718  SharePoint Foundation                 General                                       88gr       Verbose               alternateUrl is null           f19c8895-b179-4f07-8a5e-e343f3d81fe7

OWSTIMER.EXE (0x1604)                              0x1718  SharePoint Foundation                 Database                                      tzku       Verbose               ConnectionString: 'Data Source=DBServer\instance;Initial Catalog=SharePoint_Config;Integrated Security=True;Enlist=False;Asynchronous Processing=False;Connect Timeout=15'    ConnectionState: Closed ConnectionTimeout: 15              f19c8895-b179-4f07-8a5e-e343f3d81fe7

OWSTIMER.EXE (0x1604)                              0x1718  SharePoint Foundation                 Topology                                      88gs       Verbose               hostHeaderSiteInfo is null            f19c8895-b179-4f07-8a5e-e343f3d81fe7

OWSTIMER.EXE (0x1604)                              0x1718  SharePoint Foundation                 Topology                                      88gv       Verbose               request is not loopback f19c8895-b179-4f07-8a5e-e343f3d81fe7

OWSTIMER.EXE (0x1604)                              0x1718  SharePoint Server                     Social Data                                   d0rj       Unexpected            RatingSync: Unexpected exception processing https://ConsumingFarm/News/Pages/RatedPage.aspx. Error:System.IO.FileNotFoundException: The Web application at https://ConsumingFarm/News/Pages/RatedPage.aspx could not be found. Verify that you have typed the URL correctly. If the URL should be serving existing content, the system administrator may need to add a new request URL mapping to the intended application.     at Microsoft.SharePoint.SPSite..ctor(SPFarm farm, Uri requestUri, Boolean contextSite, SPUserToken userToken)     at Microsoft.SharePoint.SPSite..ctor(String requestUrl)     at Microsoft.Office.Server.SocialData.SocialRatingManager.PropagateRating(SocialRatingAverage ratingAverage) f19c8895-b179-4f07-8a5e-e343f3d81fe7
-----------------------------------

These errors are occurring because the https://ConsumingFarm web application does not exist on the Publishing Farm.

In this configuration, it is important to know that the two timer jobs related to Social Ratings run in the following locations:

Social Data Maintenance Job: This must run on the Publishing Farm where the User Profile Service "lives"

Social Rating Synchronization Job: This must run on the Consuming Farm where the Web Applications "live".

NOTE: If the Publishing Farm does not have any user-accessible web applications, you can disable the "Social Rating Synchronization Job" timer job without any problems (on the Publishing Farm, itself).
]]> June 2010 Cumulative Update for SharePoint 2010 - Released! https://docs.microsoft.com/archive/blogs/brent/june-2010-cumulative-update-for-sharepoint-2010-released Thu, 22 Jul 2010 09:46:16 GMT https://blogs.technet.microsoft.com/brent/2010/07/22/june-2010-cumulative-update-for-sharepoint-2010-released/ Colleague Stefan Goßner has posted an update on his blog that the June 2010 Cumulative Update for SharePoint 2010 has been released.

You can read the full announcement from Stefan here: https://blogs.technet.com/b/stefan_gossner/archive/2010/07/22/the-first-cumulative-update-for-sharepoint-2010-family-has-been-released.aspx

The relevant KBs, for your reference, are (as taken from Stefan's blog):

Microsoft SharePoint Foundation 2010:

 Microsoft SharePoint Server 2010:

]]> SharePoint Server 2010 - MaxDownloadSize and MaxGrowFactor https://docs.microsoft.com/archive/blogs/brent/sharepoint-server-2010-maxdownloadsize-and-maxgrowfactor Mon, 19 Jul 2010 14:25:00 GMT https://blogs.technet.microsoft.com/brent/2010/07/19/sharepoint-server-2010-maxdownloadsize-and-maxgrowfactor/ After testing the MaxDownloadSize and MaxGrowFactor registry entries, I have something important to share:  SharePoint 2010's Search registry settings are not universally able to be modified in the registry directly.

 

In this case, if you directly edit MaxDownloadSize and/or MaxGrowFactor for the Crawl Component in the registry branch (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Applications\<guid>-crawl-<#>\Gathering Manager) and then restart OSearch14, the setting will simply be overwritten and restored back to its default setting of 16 and 4, respectively.

 

To fix this, you need to do the following in the SharePoint 2010 PowerShell console:

1.       Get the Search Service Application and store it in a variable by running: 

       $ssa = Get-SPEnterpriseSearchServiceApplication

2.       To get the current value of the MaxDownloadSize in the MSSConfiguration table: 

      $SSA.GetProperty(“MaxDownloadSize”)

3.       The same thing can be done for "MaxGrowFactor" - $SSA.GetProperty("MaxGrowFactor")

4.       To modify the MaxDownloadSize and MaxGrowFactor values (assuming the customer wants or needs to adjust MaxGrowFactor):

       $SSA.SetProperty(“MaxDownloadSize”, <size bigger than 16 for what you want to crawl>)

       $SSA.SetProperty("MaxGrowFactor", <size bigger than 4>)

       $SSA.Update()

 

Once this is done, you can safely restart OSearch14 and, at that time, the larger files will be able to be crawled without further problems.

]]>