Microsoft Access Data Components are usually fairly stable. They tend to be updated with significant OS related updates (I'm looking at you, Service Packs). That being said, issues do happen. Today I encountered an issue following a P to V migration using Hyper-V for a Windows 2000 server with an ADO connection to a MSSQL database. Somehow MDAC versions become mismatched during this process. Your actual error may vary. Your application may throw an error 429 " Active-X component can't create object", you might get a IPP_E_MDAC_VERSION error. In the case today, a line in the website's general.asa was mentioned as an invalid object. Download and execute the Microsoft Component Checker to verify a mismatch against your required Component versions - Use this for 2003 and this for 2000 . For Windows Server 2003 and 2008 systems, I would typically advise an in-place upgrade as outlined here . You can try a manual install on these OS' but frankly it is no