If successful, a pop-up window will appear stating: "DllRegisterServer in ChilkatCrypt2.dll succeeded." Launch Autodata to check if the error is gone. 2. Configure Compatibility Modes
@echo off cd "C:\Program Files (x86)\AutoData" copy %windir%\SysWOW64\borlndmm.dll . regsvr32 /s rtl60.bpl regsvr32 /s vcl60.bpl icacls "C:\ProgramData\AutoData" /grant Everyone:F /T echo Fix applied. Launch AutoData now. pause
Completely uninstall Autodata using the standard tool. autodata runtime error 217 at 00580d29 windows 10 full
Uninstall Autodata via .
If you have exhausted all of the software and registry fixes above, the installation of Autodata itself may be severely corrupted. If successful, a pop-up window will appear stating:
Windows 10 has strict security protocols that can block Autodata from accessing necessary database files. Right-click the on your desktop. Select Properties . Go to the Compatibility tab. Check the box: Run this program as an administrator . Click Apply and then OK . Use Compatibility Mode
In simpler terms: Autodata—particularly versions released before 2015—was designed for Windows XP, Vista, or Windows 7. When run on Windows 10, its older runtime libraries clash with Microsoft’s modern security and memory management systems. regsvr32 /s rtl60
In the command prompt, type the following command to navigate to the folder and press : cd c:\ADCDA2 Use code with caution.
The is a solvable problem. In 9 out of 10 cases, the culprit is missing Borland runtime libraries ( borlndmm.dll , rtl60.bpl ) combined with Windows DEP blocking legacy memory access.