Month: May 2014

First beta release of #AADSync

The pre-release program of Azure AD Sync on Connect has been updated with the first beta release of AADSync.

The beta release is available on Connect from this link:

https://connect.microsoft.com/site433/Downloads/DownloadDetails.aspx?DownloadID=53361

Make sure to read the updated installation guide and release notes available on TechNet:

http://go.microsoft.com/fwlink/?LinkID=393942

As requested by the PG, please continue to provide feedback through Connect. This allows MS to deliver a high-quality product which is solving your scenarios.

Note-to-self: Sharepoint maintenance for FIMsters (#FIM2010 running out of disk space?)

When you’re taking care of your FIM Server, more specific the FIM Portal server running Sharepoint, you might encounter some events in the event viewer, where Sharepoint is complaining about the lack of disk space.

But it’s very likely that you have plenty of disk space …

If you don’t have plenty of disk space, (*) then stop reading and fix it, bookmark this page and come back.

 

So, you have plenty of diskspace…
Then it’s very likely you have enough memory in your system to run your FIM Server smoothly… (if not go back 2 lines, and execute *)

Now, plenty of memory and plenty of disk is the problem.

By default Sharepoint runs the health analyser and has gotten 2 rules that compare the amount of memory against the amount of free space.

See here for more explanation: Drives are running out of free space (SharePoint Foundation 2010)
“This rule checks disk space as a proportion of the RAM on the computer. When disk space is less than twice the RAM on the computer, the health rule triggers an error. When disk space is less than five times the RAM on the computer, the health rule triggers a warning. Accordingly, server computers with lots of RAM are more likely to experience a failure of this rule.”

So if you have a huge amount of memory, this rule can easily fill up your application event error log in your event viewer.

What can you do about it?

First of all, there are more and other rules, tools and checks that will warn you if you REALLY have a disk issue:

  • the operating system will warn you if your hard drive is going below the usual free space thresholds
  • Better make sure you’ve got a system monitoring active (like System Center Operations Manager)
  • There are additional health rules in SharePoint that monitor the disk for % of free space

Secondly, you can disable the redundant error messages by the SharePoint Health Analyser.
Check out this post:
“SBS2011: The SharePoint Health Analyzer detected an error. Drives are running out of free space. Available drive space is less than twice the value of physical memory. [Solved]
http://www.vspbreda.nl/nl/2013/11/sbs2011-the-sharepoint-health-analyzer-detected-an-error-drives-are-running-out-of-free-space-available-drive-space-is-less-than-twice-the-value-of-physical-memory-solved/

Although the post is focusing on SBS2011, it does also apply to SharePoint Server 2010 (Foundation).

The post provides a step by step guide to disable the 2 disk analysis jobs:

  • Disks are at risk of running out of free space. (free disk space < 5x your server’s RAM)
  • Disk are running out of free space (free space < 2x your server RAM)

 

For WSS and SharePoint 2007, it’s slightly different, check this out:

http://blogs.microsoft.nl/blogs/premierfieldengineering/archive/2009/05/09/timer-jobs-in-sharepoint-2007.aspx

And also: SharePoint Timer job reference (Office SharePoint Server) at http://technet.microsoft.com/en-us/library/cc678870(v=office.12).aspx#section1

Note-to-self: Troubleshooting #FIM2010 Sharepoint error event id 6481 Application Server job failed for service instance Microsoft.Office.Server.Search.Administration.SearchDataAccessServiceInstance

Error Details:

Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Server
Date:          2014-05-21 03:04:00
Event ID:      6481
Task Category: Shared Services
Level:         Error
Keywords:
User:          DOMAIN\SPFARMSvcAccount
Computer:      FIMPORTALSERVER.DOMAIN.LOCAL
Description:
Application Server job failed for service instance Microsoft.Office.Server.Search.Administration.SearchDataAccessServiceInstance (0a460b52-213c-4cd3-8e0a-b7e33ac6b8d6).

Reason: An update conflict has occurred, and you must re-try this action. The object SearchDataAccessServiceInstance was updated by DOMAIN\SPFARMSvcAccount, in the OWSTIMER (5016) process, on machine FIMPORTALSERVER.  View the tracing log for more information about the conflict.

Technical Support Details:
Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException: An update conflict has occurred, and you must re-try this action. The object SearchDataAccessServiceInstance was updated by DOMAIN\SPFARMSvcAccount, in the OWSTIMER (5016) process, on machine FIMPORTALSERVER.  View the tracing log for more information about the conflict.
at Microsoft.Office.Server.Search.Administration.SearchDataAccessServiceInstance.UpdateWithRetrying()
at Microsoft.Office.Server.Search.Administration.SearchDataAccessServiceInstance.Synchronize(Boolean calledFromSearchServiceInstance)
at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”&gt;
<System>
<Provider Name=”Microsoft-SharePoint Products-SharePoint Server” Guid=”{C33B4F2A-64E9-4B39-BD72-F0C2F27A619A}” />
<EventID>6481</EventID>
<Version>15</Version>
<Level>2</Level>
<Task>3</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime=”2014-05-21T01:04:00.220244700Z” />
<EventRecordID>110139</EventRecordID>
<Correlation ActivityID=”{B3E7929C-18F3-208C-0D4A-7E9CBD19AFB8}” />
<Execution ProcessID=”5748″ ThreadID=”3392″ />
<Channel>Application</Channel>
<Computer>FIMPORTALSERVER.DOMAIN.LOCAL</Computer>
<Security UserID=”S-1-5-21-00000000-811273523-976865563-261671″ />
</System>
<EventData>
<Data Name=”string0″>Microsoft.Office.Server.Search.Administration.SearchDataAccessServiceInstance</Data>
<Data Name=”string1″>0a460b52-213c-4cd3-8e0a-b7e33ac6b8d6</Data>
<Data Name=”string2″>An update conflict has occurred, and you must re-try this action. The object SearchDataAccessServiceInstance was updated by DOMAIN\SPFARMSvcAccount, in the OWSTIMER (5016) process, on machine FIMPORTALSERVER.  View the tracing log for more information about the conflict.</Data>
<Data Name=”string3″>Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException: An update conflict has occurred, and you must re-try this action. The object SearchDataAccessServiceInstance was updated by DOMAIN\SPFARMSvcAccount, in the OWSTIMER (5016) process, on machine FIMPORTALSERVER.  View the tracing log for more information about the conflict.
at Microsoft.Office.Server.Search.Administration.SearchDataAccessServiceInstance.UpdateWithRetrying()
at Microsoft.Office.Server.Search.Administration.SearchDataAccessServiceInstance.Synchronize(Boolean calledFromSearchServiceInstance)
at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)</Data>
</EventData>
</Event>

Solution:

1. Check the SharePoint Farm account password, Try to (re)start the sharepoint timer service. Check for logon failure.

See: http://social.technet.microsoft.com/Forums/en-US/2663487c-748d-413e-a8fc-81f41f216297/update-conflict-in-search-service-application

2. Clear the SharePoint cache on the server where the timer service is running.

Refers to: http://www.social-point.com/sharepoint-2010-event-id-6482-application-server-administration-job-failed-for-service-instance-microsoft-office-server-search-administration-searchserviceinstance