1754783 - ACCESS VIOLATION error when processing with the URAC transform - Data Services

• Generic URAC error
• Error pointing to the ace64.dll
• Complaining about the ace32.dll file
• Same job processed without errors previously
• How to identify or isolate the record causing the crash
• A certain address is causing the URAC transform to fail
• Job aborts when using the USA Regulatory Address Cleanse (URAC) transform
• ERROR:  System Exception <ACCESS_VIOLATION> occurred. Process dump is written to <path>
• Call stack:
                                                       0x000000000ED90E8F, ace_get_ncoalink_log_details_rec_length()+0623 byte(s)
                                                       Registers:
                                                       RAX=0000000000000000  RBX=000000001249E070  RCX=00000000FFFFFFFF  RDX=00000000FE6D4960  RSI=00000000000007DC
                                                       RDI=000000001249E071  RBP=0000000000000043  RSP=000000001249DF60  RIP=000000000ED90E8F  FLG=0000000000010297
                                                       R8=0000000013DC96E0   R9=0000000013DC96F0  R10=0000000000000007  R11=000000001249DF50  R12=0000000000000001
                                                       R13=0000000000000042  R14=0000000000000000  R15=0000000000000000
                                                       Exception code: C0000005 ACCESS_VIOLATION
                                                       Fault address:  000000000ED90E8F 01:00000000000CFE8F D:\Program Files (x86)\SAP BusinessObjects\Data Services\bin\ace64.dll
                                                       ==========================================================
                                                       Collect the following and send to Customer Support:
                                                       1. Log files(error_*, monitor_*, trace_*) associated with this failed job.
                                                       2. Exported ATL file of this failed job.
                                                       3. DDL statements of tables referenced in this failed job.
                                                       4. Data to populate the tables referenced in the failed job. If not possible, get the last few rows (or sample of them) when
                                                       the job failed.
                                                       5. Core dump, if any, generated from this failed job.

Data Services

BODS , DS , ace32 , ace64 , dll , crash , error , fail , failed , abort , aborted , aborting , URAC , ACCESS_VIOLATION  , KBA , EIM-DS , Data Services , How To