Be sure you're running it locally (don't try to use WTS on those tools with 2.x) - and be sure to log in as the same account the AvCSMGr service is running as - that error means we can't bind to the running DOH (data engine under Unity).
Hmmm... I got no idea why MDAC would have anything to do with this - the 2.x version of dbWalker for instance didn't use any database access at all (ODBC, OLE Db or otherwise - all the stuff MDAC would be concerned with). It only bound to the DOH an did it's thing - MDAC would not have been in the mix here.
FullDBExport uses Jet libraries to creating the MDB files which is why the help says to make sure MDAC 2.6 is necessary - but the dbWalker report in your first post is throwing me off big time here...
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...