DataAssist Wizard "Runtime Error! R6025"

I am getting the following error when I click finish on the last page of the DataAssist wizard:

Runtime Error! R6025 - pure virtual function call

I am using the latest version of DataAssist w/Dreamweaver CS5

I have tried a few of the solutions mentioned in threads (Like choosing "Document" for the "Create Links Relative To" option on the Local Info tab before running the DataAssist wizard.
I have also tried re-installing DataAssist sever times and re-booting machine.

I keep getting the same error over and over again.

Any help would really be greatly appreciated.

Thanks,
Dave

Dave, it is most likely the cache dat file with Dreamweaver that occurs after installing extensions. For some reason, it gets corrupt and makes everything haywire. You should get in the practice of deleting it every time you install a new extension. It will help alleviate most problems.

For Windows users
1. Close Dreamweaver.
2. Open a Windows Explorer window.
3. In the Address bar enter %appdata% and click Enter.
4. Open the Adobe directory.
5. Open the Dreamweaver folder for the version of Dreamweaver you are using.
6. Dreamweaver CS4 users only – open the en_US directory.
7. Open the Configuration directory.
8. Locate the WinFileCache.dat file. There may be some other numbers appended to this filename.
9. Press Delete to delete this file.
10. Open Dreamweaver.
Note: If the problem persists, you may need to uninstall your extensions, reinstall them, then delete the WinFileCache.dat file and open Dreamweaver.

For Mac OS X users

1. Close Dreamweaver.
2. Open your OS X Finder.
3. Navigate to the following directory.
Dreamweaver CS4
/users/[username]/Library/Application Support/Adobe/Dreamweaver CS4/en_US/Configuration/
Dreamweaver CS3
/users/[username]/Library/Application Support/Adobe/Dreamweaver 9 /Configuration/
4. Locate the MacFileCache.dat file.
There may be some other numbers appended to this filename.
5. Press Delete to delete this file.
6. Open Dreamweaver.
Note: If the problem persists, you may need to uninstall your extensions, reinstall them, then delete the MacFileCache.dat file and open Dreamweaver.

I have Windows 7 with DW CS5

I deleted "versions.xml" from "AppData\Roaming\Adobe\Dreamweaver CS5\en_US\Configuration"

There was also a folder in there called "SiteCache", so I deleted the site .xml file in there as well.

I was able to run DataAssist without DW crashing. Thanks for all your help :)

Actually I was only able to get it to work that one time.. Now DW is crashing again with same error message.. frustrating..

Problem Fixed!!

I took the following steps:

Close DW
Rename the DW configuration folder to "configuration_back"
Uninstall Extensions
Start up DW
Reinstall Extensions

DataAssist seems to be working well now.

Dave

Hey someone from webassist should correct this I hame so many extensions and have to reinstall everything will take me hours

Same issue ... attempted 3 times now ... CS5 ... XP Pro SP3 ... with DataSecurity Wizard

We have spent the money to get a solution only to now get more frustration ...

I have created a support ticket so we can look into this issue further.

To view and edit your support ticket, please log into your support history:
supporthistory.php

Same issue here. I ended up calling Adobe and the only way we could get it working was to rename the adobe configuration file under my user ID and delete the registory key for Dreamweaver (ex: Resolution : Recreated the preferences by renaming and configuration folder from C:\Users\User_name\AppData\Roaming\Adobe\Dreamweaver\En_Us\Configuration to Configuration_old then
Deleted folder Dreamweaver from Regedit - HKEY_CURRENT_USER\Software\Adobe\Dreamweaver )
I then had to deinstall and reinstall all extentions for WEBASSIST to get everything working correctly. This just happen to me last night....getting very fustrated and almost scared to use DataAssist again since it forces me to start from scratch on everything I have done with the other products. The good news is that I am keeping faily good notes on what I have done up to this point so it is not a total diaster.....Someone really needs to fix this bug!!!! THANKS!

OK, glad to hear you got it fixed.

We would love to fix this bug, unfortunately, we cannot reproduce it. we are trying to work with the people that report the problem to find the cause.