"Build and Export Cache" fails to export 100% Previews:

Question

"Build and Export Cache" fails to export 100% Previews:
I am moving from Bridge CS5 to CS6 and have a very large number of 100% Previews in my CS5 cache.  The idea of regenerating all these 100% Previews in CS6 is NOT amusing.  It is amazing that there is not a simple import function for this task as a way to make the software upgrade more "seamless"… but apparently there is not.
I have read the Adobe documents:
    "Bridge Help / Manage the cache | Adobe Bridge CS4, CS5"
    "Creative Suite / Work with the Adobe Bridge cache"
Based on these documents, in Bridge CS5 I used the export function in
Tools>Cache>Build and Export Cache…
    with "Build 100% Previews" checked
    and "Export Cache To Folders" checked.
Unfortunately, the "Build and Export Cache" fails to export 100% Previews to the target directory.  They should appear in the target directory as hidden files in the format xxxxx.NEF.JPG.  Yes, I do know how to view hidden files in both the Finder and in Bridge.
In Bridge CS5 I tried Purging and rebuilding the Cache for the target directory with no luck.
I tried running "Build and Export Cache" in Bridge CS6….  still no hidden Preview files in the target directory.
My settings in both CS5 & CS6 Bridge - Preferences:
    "Keep 100% Previews in Cache" is checked
    "Automatically Export Cache to Folders When Possible" is checked
My settings in both CS5 & CS6 Bridge - Options for thumbnail quality and preview generation:
    "Generate 100% Previews" is checked
Using OS X 10.6.8
Anyone have a suggestion?????

Answer 1

Bridge is the only piece of software I have used, which incorporates a database, where new versions do not provide for importing the objects of the older version.  Very strange.
That is a very mildly conclusion but unfortunately until the cache strategy for Bridge is finally sorted out this problem will exist.
Now I have to confess that I can't use the 'Auto export cache when possible' for several versions now due to a rare problem that after the first time usage without problem created export cache almost every second time generates a warning message that due to failure it needs to replace the Cache T file, hence I deselected this option permanently.
I would think that if you have those already cached and exported files for 100 % preview in the dedicated folders it would read those files and add it to the database and central cache file when having pointed Bridge to that folder, but I'm far from sure about that.
Also after rereading your first post you state to expect the build and export cache to build also hidden files with the two extensions from original filetype followed by .jpg from cache in the folder itself (target directory)? Here I'm a bit lost. The mentioned double extension files only appear in the central cache folder and are visible but buried  in the subfolders for each quality in the central cache file at user library (default) or custom set location in Bridge prefs.
The exported cache to folder are hidden files and as long as I can remember that where 2 files already in the File browser (forgot the extension they used for this) and currently .BridgeCache (very small, few KB) and the for me problematic .BridgeCacheT file that can grow very large and has about the same size as the subfolder generated under full in the central cache.
I can see the content of the central cache without problem including the double extensions and previews of the files as thumbs in the Finder, jet with option to show hidden files I can see the CacheT file but only as a blank document icon and I can't find an application on my system to open this file to reveal its content.
Just tried it on a folder with small sized files and having set preview quality to HQ and 100 % preview (checkerboard icon in Path Bar) and then used the option from menu tools to build and export cache to folder including 100 %. Both subfolder in Central Cache and about same sized hidden CacheT file where generated without problems and the full preview was instantly on demand using magnifier. (but all this without the option in prefs to auto export to folder)
So to me it seems (if I understand everything correctly) that either the existing exported files from CS5 do cause the problem or your setup of CS6 is not working correctly.
Are we still on the same track or am I completely lost?