Best way to start is to show you those errors in the good ole event log:

Error 1001:

Fault bucket , type 0

Event Name: CLR20r3

Response: Not available

Cab Id: 0

Problem signature:

P1: owstimer.exe

P2: 14.0.5128.5000

P3: 4cace1f1

P4: mscorlib

P5: 2.0.0.0

P6: 4bebe8e2

P7: 420f

P8: 51

P9: DI4EQZGVCWKDLTHKQTZWPXE3YRFKN1I2

P10:

Attached files:

These files may be available here:

C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_owstimer.exe_8e20523ad5db1439a93c757fe02d53f596a2ef32_435aa75b

Analysis symbol:

Rechecking for solution: 0

Report Id: 43b091e0-304b-11e0-b81c-005056932bb3

 

Error 8312:

SharePoint Web Services Round Robin Service Load Balancer Event: Initialization

Process Name: OWSTIMER

Process ID: 6160

AppDomain Name: DefaultDomain

AppDomain ID: 1

Service Application Uri: urn:schemas-microsoft-com:sharepoint:service:829500b757c944debc8e4e5da76e5b07#authority=urn:uuid:69453d27abe74895b8385be3dc9c2e35&authority=https://plonapdmps01:32844/Topology/topology.svc

Active Endpoints: 1

Failed Endpoints:0

Endpoint List:

http://sharepointindexserver:32843/829500b757c944debc8e4e5da76e5b07/ProfileService.svc

 

Error 6398:

Log Name: Application

Source: Microsoft-SharePoint Products-SharePoint Foundation

Date: 04/02/2011 01:00:01

Event ID: 6398

Task Category: Timer

Level: Critical

Keywords:

User: SERVICEACCOUNT

Computer: sharepointindexserver.com

Description:

The Execute method of job definition Microsoft.Office.Server.UserProfiles.UserProfileImportJob (ID bee5da2c-0ec8-4dce-9f13-7116fdaa9256) threw an exception. More information is included below.

User profile import is in progress!Import could not be started. Please start import later or stop import now for new import to start.

 

So what’s the problem?

Noticed that when attempting to run Sync jobs that the log was not being updated and a sync job would immediately go to Idle.

Noticed also that no profiles had been updated for over a week.

Tried to check the Sync Connections. Noticed that if Sync is running the Query on Sync Connections shows nothing (most confusing) and the only way you find out that everything is actually ok is to click ADD NEW CONNECTION – actually, I decided to check instead ForeFront in Services and this is what greeted me.

04-02-2011 10-56-07.png

Forefront Identity Manager Service not started? Er – How? WT? 

And the Fix is? Drum Roll…

Seems that the ForeFront Identity Manager had stopped? [Shocked]

So, restarted ForeFront Identity Manager, and restarted the sync jobs.

Result? Success!

Why did the Fix work?

Now ‘why’ – am asking myself – can only imagine that:

1: If the Identify Manager is not working it seemed that no connections were displayed in Sync Connections, and if a new connection is attempted to be created then the Correlation Error MOSS MA was displayed – restarting Identity Manager fixed that.

2: If Forefront is configured to look at the Forest and not a specific domain in that forest then it is possible that the import will stop if the user id does not have access to that domain in the forest

3: Error 1001 showed that the job attempted to start then immediately failed, but did not indicate that ForeFront had anything to do with the job itself. I suppose the synchronisation job failed, but that would mean checking all other related jobs, and not any of the services (unless you decided to check Forefront first – as I did!)

4: Error 8312 showed an issue with the Profile Status service meaning that that job did not start or shutdown prematurely; again seems to relate to ForeFront and the Sync job

5: Finally, good old 6398 – showing that the import process could not be started – I suppose that means a fault in attempting to even start the sync process!

6: I have a very strong suspicion that the installation of the culmulative updates for Dec 2010 SharePoint affected the User Profiles sync and shut down ForeFront Identity Manager. In future for any culmulative update I will check that all those relevant services are running – in fact, a good idea is to note the state of services on the index box before applying the update. I know that sounds a bit over the top, but this kind of error completely threw me and I spent I think far too long attempting to get to the bottom of it!!

So, the upshot? Scratching Head Time but at least the problem has been corrected. So, am still investigating this one, but hope this little nugget helps you guys out there.