We have a solution that includes a custom object hanging off of Leads.  We have built a trigger that uses an "after update" action to populate an Opportunity lookup on that field when the lead is converted.  It basically check to see if the Lead "IsConverted", then grabs the "ConvertedOpportunityId" to populate the lookup on this custom object.

This has worked fine for months until yesterday when we introduced a time dependent WF rule on that custom object.

Now when we convert leads, we get this error.  It references our WF rule, but then also has a bunch of jibberish that I do not understand.  Here is the error.

Error: System.DmlException: Update failed. First exception on row 0 with id 00Q4000000ZAxfHEAT; first error: CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY, LeadTrigger: execution of AfterUpdate caused by: System.DmlException: Update failed. First exception on row 0 with id a0H40000002rHJZEA2; first error: CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY, The formula in the "Auto NDA DDP to DocuSign" rule or process is invalid due to the following:
java.sql.SQLException: ORA-20025: ORA-06512: at "SNEEZY.SACCESS", line 1237 ORA-06512: at "SNEEZY.CACCESS", line 2133 ORA-06512: at "SNEEZY.CACCESS", line 2064 ORA-06512: at line 1 : SQLException while executing plsql statement: {call cAccess.check_entity_access_ncu(?,?,?,?,?,?)}(common.request.SqlUserInfo@8f11af, common.request.SqlBtSettingsInfo@19ccfdf, 00Q4000000ZAxfH, 1, true, false): [] Trigger.LeadTrigger: line 104, column 9: [] (System Code) External entry point

Does anyone have a clue what is causing this?  And FYI, line 104 in the trigger is the update statement for the custom object after we have populated the Opportunity lookup.

And what the heck is SNEEZY??

Thanks.