Skip to main content

SharePoint User Profiles and Properties error

I recently encountered an issue with the Shared Services Administration page for User Profile and Properties (the page where you schedule an Active Directory profile import).

The page in question is in the Shared Services Provider site, e.g. http://server:port/ssp/admin/_layouts/ProfMain.aspx

The error that gets displayed is:
An error has occurred while accessing the SQL Server database or the Office SharePoint Server Search service. If this is the first time you have seen this message, try again later. If this problem persists, contact your administrator.

The error was odd, because I knew SharePoint Search was functioning (search crawls were running as normal, and search queries were being filled in the web front end). After a bit of investigation, I found the following table to be missing some records that were required.

So in actual fact, the error being referred to when accessing the SQL Server database was that some expected records weren't in the table being looked up, not that the database itself is not available.

The table to look into is named MIPScheduledJob, and is located in the Shared Services Provider's "Services" database. The table typically (with this instance of MOSS 2007 SP2, at least) contains 6 records. Two of these records are required for the Profile Import configuration page, and the remaining 4 are related tasks for processing Distribution List and Audience information.

The two key records for the User Profile and Properties page to work can be inserted back into the database with the following SQL INSERT statement:

INSERT INTO MIPScheduledJob (JobId, Assembly, Class, Recurrence, JobData, NextDueTime, Disabled, DisplayName)
'Microsoft.Office.Server, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c',
'weekly between fri 15:00:00 and fri 15:00:00',
'9999-12-31 23:59:59.997',
'User Profile Full Import Job'


INSERT INTO MIPScheduledJob (JobId, Assembly, Class, Recurrence, JobData, NextDueTime, Disabled, DisplayName)
'Microsoft.Office.Server, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c',
'daily between 12:00:00 and 12:00:00',
'9999-12-31 23:59:59.997',
'User Profile Incremental Import Job'

Now, you will notice that the JobId values there are in fact of a GUID data type, and these vary per SharePoint instance. You need to look them up in another table, which hopefully still has the appropriate record intact. The table to look up is MIPObjects, and you will find a record in there which has a very large XML data set. If you copy the XML data set out, you will find it contains a number of "field" XML nodes that include GUIDs. Find the two field nodes that correspond to the name of the jobs, i.e.

  <field name="profileFullImportJobId" type="guid">a663ee08-2acd-4ccd-be93-440bc60e4728</field>
<field name="profileIncrementalImportJobId" type="guid">f525c7ec-7f23-4881-acb6-12c5eb9248e4</field>

Grab those GUIDs and put them in the INSERT statements above, run against your SQL server.

Before you execute the INSERT statements, be sure to take backups of your database. And bear in mind that directly modifying data in your SharePoint tables is not supported by Microsoft.

After inserting the records, be sure to go back into the User Profile and Properties page and check the scheduling of the full and incremental profile imports, and adjust accordingly. The data specified in the above INSERT statements I believe, specifically the Recurrence field, is in entered without time zoning applied, so depending on where you are in the world, the scheduling may be INSERTed at innapropriate times.


  1. I just found this page -- I accidentally deleted SIX timer jobs. I was able to restore the two you listed above, but I'm not sure how to restore the other four...I don't know where they live. Here's what I accidentally deleted -- if you can offer any assistance, I'd really appreciate it!

    SSP Timer Job Id="8deb1f24-5ee7-4546-b5ac-5a3df462b2ee" Display Name="User Profile Change Cleanup Job"

    SSP Timer Job Id="4ac0046a-59a7-4ccf-a3b3-c0ab513857d8" Display Name="Audience Compilation Job"

    SSP Timer Job Id="a92e2d59-a955-48c6-955c-d6c375cc7448" Display Name="Distribution List Import Job"

    SSP Timer Job Id="fd953522-17d7-4b80-83f2-f0dec38fed43" Display Name="User Profile Change Job"

  2. What a man you are... Many Many thanks!!! it worked like anything...


Post a Comment

Popular posts from this blog

Thoughts, shortcomings, gotchas on SPFx Dynamic Data capabilities

It's the festive break, and I thought I'd try the new Dynamic Data capabilities that recently went to General Availability in SharePoint Framework 1.7.

I've been building a lot of React components lately, and all the SPFx web parts and application customisers with visual elements we create at Engage Squared, are built on React.  Dynamic Data in SPFx introduces a whole new world of modularity that we haven't had before. We can now split up the page elements into multiple web parts that, in the past, have been combined as one web part so state can be passed between them.  Doing this gives control back to the page author, with the ability to position components how they wish.

Breaking components up in to individual web parts also changes the way the components are designed, and forces the developer to leverage the responsive capabilities of modern pages.  Modern pages are designed from the ground up to work on many different screen sizes, and as long as each individual co…

Apps for SharePoint 2013 - Client and Server-side code

It's about time I blew the dust off this blog. Tonight I did a presentation at the Melbourne SharePoint User Group entitled Apps For SharePoint (2013). It included two demos based on the App For SharePoint 2013 solution template in Visual Studio 2012.

The two demos illustrated how you can create a separate ASP.Net Web Application. Demo 1 showed how easy it is to hook in to SharePoint to obtain List properties via server-side code (populating an ASP.Net Repeater Control). Demo 2 showed what you can do with SharePoint 2013's Javascript hooks. Specifically, using SP.UI.Controls.js from the /_layouts/15/ SharePoint folder to pull chrome elements out of SharePoint, and render them in your ASP.Net web app.

No animals were harmed in the making of these demos, but a few articles kindly provided on the Microsoft MSDN site helped put it together:
How to: Set up an on-premises development environment for apps for SharePointHow to: Create high-trust apps for SharePoint 2013 using the se…

SharePoint "Like" button

Ever wondered what the users of your Intranet really like or don't like? Ever wanted your SharePoint 2007 site to be more "web 2.0"-ey? Well I've published this quick and dirty codeplex project that allows the addition of a "Like" button the any SharePoint List item page.
The project is available as a WSP, and source code.
It consists of two things - a Web Part that is the button that users click to "Like" or "Unlike" something, and a List Template that can be used to create a list to store who "Likes" an item.
The button has two ways of operating. If it finds a list that was built on the List Template included in the WSP, it allows each user to Like or Unlike an item as they see fit. The button uses the List it found to keep track of who likes a given item, and queries the list when it renders to determine which option should be presented. Along with the button, the web part also displays a brief message explaining how many pe…