FIM 2010 Sync not running with status "Stopped-extension-dll-exception"

Question

we are getting the following error for all our extensions when trying to run the Sync Operations. All extensions have similar errors with event ID 6159 generated in the application event log. They all started occurring after I deleted a attribute flow
rule in one of the agents. This is happening in Production and are facing lot of other issues because of this.
The management agent "Peoplesoft" failed on run profile "Full Import Full Synch" because of a problem with the initialize method on the extension object. The extension dll is "PeoplesoftExtension.dll" and the stack trace is:
Microsoft.MetadirectoryServices.UnexpectedDataException: String or binary data would be truncated.
The statement has been terminated.
   at Mms_ManagementAgent_PeoplesoftExtension.ExtFunctions.RunSQLCommand(String commandstring)
   at Mms_ManagementAgent_PeoplesoftExtension.ExtFunctions.AddSentEmailsRecord(String sAMAccountName, String MessageSubject, String MessageBody, Int16 DelayDays)
   at Mms_ManagementAgent_PeoplesoftExtension.ExtFunctions.CheckDoNotDisableInactiveGroup()
   at Mms_ManagementAgent_PeoplesoftExtension.ExtFunctions.LoadConfigSettings()
   at Mms_ManagementAgent_PeoplesoftExtension.ExtFunctions.InitializeCommon()
   at Mms_ManagementAgent_PeoplesoftExtension.MAExtensionObject.Initialize()
Please advise on how to fix this as I have no clue where to start and am new to FIM.
Only Full Import(Staging ONLY) is successful.

Answer 1

The error message you are getting is talking about data getting truncated. Any change that you had a data change alongside your other changes and now the length of data in one or more of your attributes is longer than it was?
I suspect that since you are new to FIM, something else has changed that you don't realize (beyond just the deletion of the one sync rule), but...
If truly the only thing that changed was a deletion of a flow rule, is there any chance that either of the following could have happened:
With the deletion of a flow rule the corresponding data is no longer going through the sync engine. Could there be some logic that due to precedence, is now using a different value, and this different value is too long for some other piece of logic.
With the deletion of a flow rule the corresponding data is no longer going through the sync engine. With this value missing, some extension logic is making a different choice and generating invalid data. Without the deleted data flow, there may be a null
value that extension logic is not properly dealing with.
As was suggested, the best thing to do may be to restore from backup and get the system back to a known state.
If you have development skills and if you have the source code to your custom rules extensions, it is fairly easy to debug and single step through the code. This of course must be done with extreme caution if you are in a production environment. You will
also need familiarity with how the FIM Synchronization engine works. Documentation is here:
http://msdn.microsoft.com/en-us/library/windows/desktop/ms698774