Check ADO/MDAC installation. Verify MDAC version: HKEY_LOCAL_MACHINE\Software\Microsoft\DataAccess. The reinstallation is little difficult for MS XP and Vista that comes initially with a new MDAC version.
As we know the later MDAC sw is an integral part of XP or Vista OS. Another version: Full21Install: 0xffffffff FullInstallVer: 6.0.5308.17 RollbackVersion: 2.71.9030.9 Version: 6.0.5308.17 Windows Installer is version 6.0 and I think that MS wants to sync up all the version numbers for apps and components.
Try to roll back to an earlier vesion of MDAC. Run Dasetup.exe with the following command name: dasetup.exe /u
I am receiving the same error when trying to install HP Openview 4.5 SP 15 with Vista Beta 2. I tried to register the MDAC 2.8 components and that did not work. I would also be interested to here if anyone has a fix for this error. Thanks.
Hello, I confirm same problem with Vista RC1 build 5600. I cannot work without Service Desk. Anyway SD still needs only MS Java which is potentialy point of unstability on Vista because Java from MS is not supported any more and it is old installation package. Anyway ADO DB is still the main issue.
I could not get it to work. I tried editing the MDAC dll files and just changing the "FILEVERSION" tab to 2.81.1117.0 and replaced the originals with the edited ones, no luck. I tried changing the FILEVERSION and the PRODUCTVERSION to 2.81.1117.0 and that didnt work. I copied the 13 MDAC files from my XP SP2 machine and tried it again and it didnt work. I uninstalled the SD client, rebooted and reinstalled, rebooted and tried again - no change in error message. I removed the text in the FILEVERSION about Vista, does that need to stay in there? I can try that too. The interesting thing is even after editing the files and removing all references to 6.0, i ran the MDAC CC 2.0 tool and it still saw some references to 6.0 in the DLL files, but I could not find any 6.0 text when I edited the files after running the CC. I changed the FILEVERSION at the top of the DLL file and in the middle - do I only edit the StringFileInfo section? I checked the registry and could not find anything - i am using RC1 as well and I tried SD client with no service pack and with SP15.
I figured you needed reverse engineering, so I found ResHacker. I havent tried it out yet, but I tried to take the "13" files from XP SP2 and place them the appropiate places in vista, and CC now sees MDAC as 2.8 SP1 XP SP2, instead of unknown.
Still doesnt work, I will try using the tool later.
I was able to find the one file that reproduced the error message on Windows XP, but unable to solve the issue on Vista. The one file is msado15.dll. I can change the FileVersion (at the top) to 1,0,0,0 and on XP it gives me the ADO 2.1 error message. If I change it anything past 2,1 then the error message goes away on XP. I tried to modify this file on vista but it doesnt work, meaning I get the same error message. I am able to edit the files, so permissions is not the issue. i can verify the DLL file is changed to the edit version that I created. I reinstalled vista and just changed the FileVersion text to 2,81,0,0 (it works in XP) but could not get it to work in Vista RC1. Not sure what else to try, i am unable to get SD4.5 working on Vista RC1
Using Softricity worked and we are able to get the client working on a Vista machine, however the icons are missing. My test user is trying to user Windows 2K as the virtual profile and couldn't get the JVM installed. Has any one else has trouble with W2K and the JVM?
Or does any one have an idea why the icons would be missing on Vista?
HI I found the source of problem: mdac not changed, they stay ver 6, but if on your SD application server turn on Remote Update and you install the client lower version then your Application server - the Application server try update the \service desk folder by new verion servicepack.jar, then you recive the error messages " Microsoft ADO DB 2.1". But if you install clinet with same version as applic server - working withour errors.