Re: Access Violation using CreateParameter

On Jun 26, 7:41 am, "Stephen Howe" <stephenPOINThoweATtns-
globalPOINTcom> wrote:
Unfortunately in the interval we've switched from VS7.1 to
VS8.0, switched from x86 to x64 build machines, and in the process
upgraded our version of MDAC, so I'm not sure what might be causing
the problem.

Upgraded your version of MDAC on a x64 machine?
The normal versions of MDAC make it very clear that it is for Win32 _only_:
See MDAC 2.8 at:http://www.microsoft.com/downloads/details.aspx?familyid=6c050fe3-c79...
where it details various falvorus of Win32 under "Supported Operating
Systems" but not Win64.

and under no circumstances should you try to "upgrade" MDAC on a x64
machine.
The MDAC on the x64 is specific to x64 and should not be tampered with.
Only the security patches for MDAC that are marked x64 are applicable for
this.
x64 is a special case here.
The general MDAC is available for most of the Win32 family but not Win64.
It is an exception.

Can anyone suggest what might be the problem, or at least where to
start looking?

Reinstall Windows x64. I am 99% certain you cannot uninstall MDAC.
Sorry about that.

I should clarify that. The version of MDAC on the x64 machine is later
than the version of MDAC on the win32 machine. There is a Common Files
\System\ado folder in both Program Folders and Program Folders (x86),
presumably this is what came installed on the machine in the first
place since I can't be sure since IT handled the basic setup. In both
locations the file version is 2.82.3959.0

The hotfix I mentioned is for Windows Server 2003, which I understand
is the basis of Win XP Pro x64, which is my current OS, but I did not
install the hotfix because it did not specifically say is was for XP
x64 and because the file version was wrong in any case (2.82.2589.0)

.

Relevant Pages

  • Re: Access Violation using CreateParameter
    ... Upgraded your version of MDAC on a x64 machine? ... The normal versions of MDAC make it very clear that it is for Win32 _only_: ... and under no circumstances should you try to "upgrade" MDAC on a x64 ...
    (microsoft.public.data.ado)
  • RE: Question: Buffer Overrun in Microsoft Data Access Components Coul d Lead to Code Execution (Q32
    ... Microsoft web site indicates that a backout isn't recommended... ... re-deploy is needed to undo the upgrade. ... > installations with MDAC 2.7. ... > figure out just what is going on and where the vulnerability lies. ...
    (Focus-Microsoft)
  • Re: MDAC question
    ... it is best to install the earlier version ... treated as more of a o/s upgrade and NOT simply the sole dependancy of any ... > version of MDAC than you plan to use during development. ... provides a newer 2.8 interface. ...
    (microsoft.public.vb.general.discussion)
  • RE: 80004005 Unspecified Error
    ... A very similar thing happened to us after an upgrade of WSUS, ... ASP web pages running off an ... we upgraded MDAC to version 2.8 and now our asp scripts are again ... > Microsoft JET Database Engine error '80004005' | ...
    (microsoft.public.inetserver.asp.db)
  • Re: From 2.5 to 2.8
    ... >I have a windows 2000 server with MDAC. ... Will the developers of ASP ... >consideration before upgrading to 2.8 MDAC. ... have never had a problem with an MDAC upgrade, ...
    (microsoft.public.data.ado)