Sync Service updated fine but the Service is failing. It seems to install with no issue but then fails to start the service at the end of the process. Any thoughts would be apprectiated. Found this in the patch log: MSI (s) (84:98) [16:37:12:242]: Attempting to delete file C:\Windows\Installer\c2e61e.msp MSI (s) (84:98) [16:37:12:242]: Unable to delete the file. LastError = 32 MSI (s) (84:98) [16:37:12:249]: Attempting to delete file C:\Windows\Installer\c2e61e.msp MSI (s) (84:98) [16:37:12:253]: MainEngineThread is returning 1603 MSI (s) (84:5C) [16:37:12:269]: RESTART MANAGER: Session closed. MSI (s) (84:5C) [16:37:12:269]: No System Restore sequence number for this installation. MSI (s) (84:5C) [16:37:12:277]: User policy value 'DisableRollback' is 0 MSI (s) (84:5C) [16:37:12:277]: Machine policy value 'DisableRollback' is 0 MSI (s) (84:5C) [16:37:12:277]: Incrementing counter to disable shutdown. Counter after increment: 0 MSI (s) (84:5C) [16:37:12:277]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 MSI (s) (84:5C) [16:37:12:279]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 MSI (s) (84:5C) [16:37:12:283]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1 MSI (s) (84:5C) [16:37:12:283]: Restoring environment variables MSI (s) (84:5C) [16:37:12:310]: Destroying RemoteAPI object. MSI (s) (84:64) [16:37:12:311]: Custom Action Manager thread ending. MSI (c) (40:C4) [16:37:12:322]: Back from server. Return value: 1603 MSI (c) (40:C4) [16:37:12:322]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1 MSI (c) (40:C4) [16:37:12:323]: PROPERTY CHANGE: Deleting SECONDSEQUENCE property. Its current value is '1'. Action ended 16:37:12: ExecuteAction. Return value 3. MSI (c) (40:C4) [16:37:12:323]: Doing action: FatalError Action 16:37:12: FatalError. Action start 16:37:12: FatalError. MSI (c) (40:C4) [16:37:12:325]: Transforming table CustomAction. MSI (c) (40:C4) [16:37:12:326]: Transforming table CustomAction. MSI (c) (40:C4) [16:37:12:326]: Note: 1: 2262 2: CustomAction 3: -2147287038 MSI (c) (40:F8) [16:37:12:332]: Transforming table Binary. MSI (c) (40:F8) [16:37:12:332]: Transforming table Binary. MSI (c) (40:F8) [16:37:12:332]: Note: 1: 2262 2: Binary 3: -2147287038 Action 16:37:12: FatalError. Dialog created Action ended 16:37:18: FatalError. Return value 2. Action ended 16:37:18: INSTALL. Return value 3. MSI (c) (40:C4) [16:37:18:999]: Destroying RemoteAPI object. MSI (c) (40:FC) [16:37:19:002]: Custom Action Manager thread ending.

OK - this sounds like the AD user account you're installing the update with is not one of the two WSS site administrators defined for the FIM portal. Go to the WSS Central Admin site, navigate to the site administrators page for your FIM site, and ensure the site administrators includes your logged in installation account.Bob Bradley (FIMBob @ http://thefimteam.com/) ... now using Event Broker 3.0 @ http://www.fimeventbroker.com/ for just-in-time delivery of FIM 2010 policy via the sync engine

That might actually be the trick - this was set up by a vendor and he has several of the service set to run as his AD account (good thing it is only DEV) I will get in with his account and see if this fixes the issue.

Well that sounds similar to my experience ... it was about this time last year, but with a production system ... the guy who did the install was away @ TechEd at the time and had done the same thing :)Bob Bradley (FIMBob @ http://thefimteam.com/) ... now using Event Broker 3.0 @ http://www.fimeventbroker.com/ for just-in-time delivery of FIM 2010 policy via the sync engine

That was the trick, I reset his PW and logged in as him and the update ran correctly. Next I add myself to all of the SP sites so this doesn't happen again... Thanks for your help Bob.