So I was just doing some checking up and making sure everything was running correctly, which it seems it is, but I have come across a lot of errors in the Windows logs attached to the FIMSync Service. Was wondering if anyone could give me any advice.

This is happening on our cycles, delta sync and exports

I know that some of the errors have to do with ADMIN accounts and the MA account does not have access to manage them. But not sure what the rest are

APPLICATION LOG ERROR

Forefront Identity Manager 4.1.3599.0

The server encountered an unexpected error in the synchronization engine:

 "BAIL: MMS(5504): d:\bt\37281\private\source\miis\server\sqlstore\csobj.cpp(8254): 0x80230404 (The operation failed because the attribute cannot be found)

BAIL: MMS(5504): d:\bt\37281\private\source\miis\server\sqlstore\csobj.cpp(8254): 0x80230404 (The operation failed because the attribute cannot be found)

BAIL: MMS(5504): d:\bt\37281\private\source\miis\shared\entry\tower.cpp(3989): 0x80004005 (Unspecified error)

ERR_: MMS(5504): d:\bt\37281\private\source\miis\shared\entry\tower.cpp(12133): BAIL: MMS(5504): d:\bt\37281\private\source\miis\server\sqlstore\csobj.cpp(1833): 0x80004005 (Unspecified error)

BAIL: MMS(5504): d:\bt\37281\private\source\miis\server\sync\expcall.cpp(905): 0x80004005 (Unspecified error)

ERR_: MMS(5504): d:\bt\37281\private\source\miis\server\sync\expbase.cpp(2957): PutAnchorWithDnInternal failed on CS object {0E6B94B6-4416-E211-ABF9-005056BA0089} with 0x80004005 (pass 1 of 5)

Forefront Identity Manager 4.1.3599.0"

The management agent controller encountered an unexpected error.

 "BAIL: MMS(5504): d:\bt\37281\private\source\miis\cntrler\cntrler.cpp(12498): 0x80004005 (Unspecified error)

BAIL: MMS(5504): d:\bt\37281\private\source\miis\cntrler\cntrler.cpp(9395): 0x80004005 (Unspecified error)

BAIL: MMS(5504): d:\bt\37281\private\source\miis\cntrler\cntrler.cpp(8158): 0x80004005 (Unspecified error)

Forefront Identity Manager 4.1.3599.0"

OPERATIONAL LOG ERROR TONS OF THESE, NO OTHER DETAILS

HRESULT: '0x80230507' Source: 'd:\bt\37281\private\source\miis\server\rules\project.cpp(1635)'  Thread ID: '0x109c' Additional Info: ''

Russell,

These errors are more or less saying "Contact administrator".  Very generic, failure of some sort, uncaught exception.

The errors you are aware of, most likely are related to this generic failure.

what worries me is the number of them occurring.. it is almost one for every object each sync.

I cannot seem to find what the cause maybe. Any idea where I could dig to find why is causing the offense?

This is why I always suggest that the runcycles are kept clean.  You need to solve the issues below, so you can better manage the real issues.

I know that some of the errors have to do with ADMIN accounts and the MA account does not have access to manage them. But not sure what the rest are

If you look at the History of runCycles, in FIM Management Console, there are the details of each error.

ok thanks I will take a look.
I exported the log and saved it then cleared it so I can get an exact number of errors occurring for each MA. Maybe that will help.

I see about 300 error in total that should occur, which are correct due to some of the changes that were needed to be made.

I appreciate your advice.

I am sorry to pound over this, but I have seen it way too many, and it almost always ends up the same.  You cannot let 300 errors repeat every runcycle. 

While I strongly believe you have nothing to worry about, I suggest you do clear out the 300 errors. When the number is that large, it is hard to eyeball.  the total 300 may be the same, but the errors may have changed.

You cannot be sure based on the number of errors. 

they are all permission errors, trying to modify connected attributes of _admin accounts. We keep them connected due to password sync, but have taken away the MA accounts right to modify the attributes of the admin accounts.

Not sure if we want to disconnect them, then the password sync would not work for the admin accounts

Understood.

So if your event logs match the 300, you can almost be sure they are related. and they will all say the same thing anyways.

I will see the next cycle runs in a few minutes and will let you know.

Thanks again.