Hi all,

we have upgraded to SQL Server 2008 R2 from SQL Server 2008 and since then our fuzzy matching process has failed when trying to re-use existing index with the error:

[Fuzzy Lookup] Progress: Warming caches - 0 percent complete
[Fuzzy Lookup [9824]] Warning: Catastrophic failure
[SSIS.Pipeline] Error: component "Fuzzy Lookup" (9824) failed the pre-execute phase and returned error code 0x8000FFFF.

Warming cache property is set to False though.

Has anyone experienced the same error?

When building a new index fuzzy matching runs without problems.

Thanks a lot.
Fran

Could be that the new box is 64Bit and the old one was 32Bit

I'd recommend deleting the component in question, then re-adding, hopefully that fixes the issue.

Thanks. Though both machines are 64bit.

We think it may be because of Windows. We upgraded from Windows Server 2003 to Windows Server 2008 R2...

Hi Fran,

The error may occur due to a memory issue such as the Fuzzy Lookup task consumes high memory buffers. Please try the following steps:

1. Run the package in 64-bit mode by setting the Run64BitRuntime property of the project to True.
2. Right click the Fuzzy Lookup task and click Show Advanced Edior
3. Switch to the Component Properties tab, and set the following properties:
   CopyReferenceTable: 0
   DropExistingMatchIndex: 0
   WarmCaches: False

Hope this helps.

Regards,

Thanks! Though that didn't work either. It fails during pre-execute so I don't think it hits memory issues at all.

Here details from the dump file:

[M:1]   Ring buffer entry: (*pRecord)
[D:2]      <<<CRingBufferLogging::RingBufferLoggingRecord>>> ( @ 00F5E038 )
[E:3]         Time Stamp: 2013-10-04 12:58:56.494 (szTimeStamp)
[E:3]         Thread ID: 1652 (ThreadID)
[E:3]         Event Name: OnError (EventName)
[E:3]         Source Name: (SourceName)
[E:3]         Source ID: (SourceID)
[E:3]         Execution ID: (ExecutionGUID)
[E:3]         Data Code: -1073450982 (DataCode)
[E:3]         Description: component "Fuzzy Lookup" (9824) failed the pre-execute phase and returned error code 0x8000FFFF.

After long testing I found the issue causing the error: the index table contains an empty string Token.

The work-around is to update the empty string to NULL.

Microsoft hasn't confirm yet why is this Token created in the first place. As far as I know, it is created only when using Windows Server 2008 R2 and not on Windows Server 2003.

Thanks all for your support.

Fran

• Marked as answer by FataFranci Thursday, October 31, 2013 11:12 AM

Hi FataFranci,

Can you provide more details on how you fixed this?

I have the same problem but am unable to find any blank strings in my source table or any of the system generated index tables.

Disabling the warm cache options works around the problem - however I'm in a position where I need to warm the cache.

Also you said Microsoft hasn't confirmed why the token was created - is there a connect case for this? Maybe a fix is expected.

Thanks

Simon

Microsoft Certified Master: SQL Server 2008