Thanks a lot for all that, Scook. I'll give it a go and let you know. 
 
In the mean time, another issue has popped up, but that's for another thread. 

The quickest is to find all the folders associated with DP, including samples, and presets and synchronize them. I have at least 4 folders with DP and other samples cuz historically I have placed samples on the samples disk. I have repeatedly had to change registry paths to get stuff to work with new installations since DP and other programs do not place stuff here ya want it.
 
 I still have many 32 bit plugs installed cuz I have some very old programs that use them. Such as 32 bit direct x DP.
 
 Another distraction was when DP stopped using wav files and installed flac files. All kinds of presets did not work for on new computer installation. Had to copy all the wav files to the same folders.
 
And now the CCC demands using the default folders which are unreasonably placed in buried folders that should never contain user defined settings. A user should not be able to save stuff to folders not on the default paths of most backup programs.
 
I think the CCC is defining paths. It did not obey the paths I had set for sysx, programs files,...
 
Where are your presets saved?   Some are buried in the user folder where the sun never shines.
 
Also do not use the sonar preset function. These presets are saved in a non-standard file format and requires the use of the plugin manager to export/import.  This is a way bad idea. Disks die. Sometimes it is possible to retrieve files. These files are in folders with names of many numbers. Not easy to find. Difficult to get to ever work again.
 
Whenever possible use the VST/plugin preset save/retrieve function.
 
OP: DP with identify the sample not found by listing it as 0 bytes.

scook
To fix the immediate issue, copy Saw Mini 3.sfz and saw mini.wav into where ever Dimension Pro\Multisamples\00 - Wavetables is located. Note just like the CSC, there should only be one copy of the DimPro multisamples, either the 64bit or 32bit path, not both.
 
Removing and reinstalling DimPro is not that difficult. The exact instructions are slightly different depending on if the synth was installed using the Control Center or a previous version of SONAR and if both 64bit and 32bit versions are needed. Here is the process:

• run the uninstall - If installed using the Control Center the uninstall process is started by right-clicking DimPro in the Control Center, otherwise run the uninstaller from Windows Control Panel > Programs.
• remove the registry keys HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software\dp and HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cakewalk Music Software\dp
• run the installer - The Control Center will install the 64bit version. If you need the 32bit version installed too, run the DimPro installer by hand. The default location for the installer is C:\ProgramData\Cakewalk\Command Center\Downloads.

To determine which installation of CSC is being used look at the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cakewalk Music Software\Cakewalk Sound Center\1.0\Installation Folder. The other location is not being used.

 
I'm working on this now. I have uninstalled the DP via windows uninstaller, and it seemed to remove the registry keys you directed me to delete. But it left all the DP folders under the two cakewalk sound centers (multisamples, etc). Should I just delete those folders  prior to re-installing DP? 
 
Also, regarding Cakewalk Sound Centers: I checked the registry, and the Program Files location (the 64 bit version) is the one referenced in the registry. Should I delete the other (32 bit) sound center folder? (it contains multisamples for DP and Rapture.) (The Rapture folder has an identical copy in the 64 bit folder)
 
Thanks for your help!

The DP folders under CSS have nothing to do with DP plug-in. They were put there by the CSS installer and are only used by CSS. Even though the content is from DP, DP does not use it or know anything about it. Leave it alone or you will break CSS.
 
Before deleting CSS from anywhere, rename the directory you intend to delete then test CSS from every version of SONAR you might use in the future. If CSS works as expected then it is safe to delete the directory, however; sometimes rather than delete directories right away, I move them to a scratch area on another drive. After a few weeks/months or when I need to free up some scratch space, the directories will be deleted. This gives me more time to determine if removing a directory was a mistake.
 
And then the standard recommendation, make a backup and/or have a plan to recover should something go wrong. In this case the worst is a reinstall so there is not much risk.