Re: Upgrade killed my connection, ASP to SQL doesn't work
From: Richard (rb_at_sts1.com)
Date: 03/22/04
- Previous message: Sue Hoegemeier: "Re: error message not being logged to windows event log"
- Messages sorted by: [ date ] [ thread ]
Date: 22 Mar 2004 13:35:35 -0800
Scot --
I have the same problem with those mismatched DLLs after a 2K to 2K3
upgrade. But I can't find any way to copy. I have a Win2K machine with
MDAC 2.8 installed, but every time I try to copy oledb32.dll to the
2K3 machine, I get "Access denied. The source file may be in use". Yet
I can make a copy of the dll onto another directory of the same
machine -- no error. When I try to copy that copy onto the target
machine... same error!
You mention you can copy the file from the redistributable -- do you
mean the mdac_typ.exe? If so, how? I can find nothing else designated
as the "redistributable" for MDAC, and there's no obvious way to pull
a single file out of it. Running the 2.8 MDAC on the W2K3 server of
course does nothing at all.
It seems that if I can make a local copy of the DLL, then the DLL is
not read locked. Yet even that copy can't be copied to the target.
I've tried shutting down everything possible, with no luck.
So exactly how does one get a copy of the DLL in a form that it can be
copied onto W2K3? And I've found about a dozen similar posts of this
same upgrade problem? Hasn't Microsoft ever gotten the message that
something as "unimportant" as data access is broken in the upgrade?
Any recommended fix from anybody that addresses this?
Thanks!
"Scot Kelly" <scot_kelly@hotmail.com> wrote in message news:<eanI7V0#DHA.268@TK2MSFTNGP10.phx.gbl>...
> I may have found a fix.
>
> On a machine running Windows 2003 Server that was upgraded from Windows 2000
> Server, look for OLEDB32.DLL in "c:\Program Files\Common Files\System\Ole
> DB".
>
> Check the version of OLEDB32.DLL. If it is the correct version for Windows
> 2003 Server, it should be (at least) version 2.80.1022.0 according to the
> MDAC 2.8 manifest.
>
> On my servers that were upgraded from Windows 2000 Server to Windows 2003
> Server, that OLEDB32.DLL file was version 2.71.9042.0. The wrong version.
>
> I copied the OLEDB32.DLL that was version 2.8.1022.0 to c:\Program
> Files\Common Files\System\Ole DB on the upgraded machines, and it seems to
> have solved the "The procedure entry point GetTextExtentPointI could not be
> located in the DLL MSDART.dll" problem.
>
> The correct OLEDB32.DLL can be found from the MDAC 2.8 redistributable, or
> from a cleanly installed Windows 2003 Server.
>
>
> "Bruce Bean" <bruceb@idxonline.com> wrote in message
> news:%23Lqn0iV8DHA.1504@TK2MSFTNGP12.phx.gbl...
> > Hi Alex
> >
> > I've just encountered the same issue with upgrading my W2K to Windows
> > 2003 when installing our application for testing on Windows 2003. I
> > have no issues on WinNT, W2K, WinXP.
> >
> > I ran a client configuration application (VB6 based) that requires
> > access to MSDE or SQL Server database.
> >
> > I am also unable to create a simple test.udl file.
> >
> > I also get the "The procedure entry point GetTextExtentPointI could not
> > be located in the DLL MSDART.dll" error.
> >
> > Did you find a resolution?
> >
> > I am going to attempt to address it now. If I find a resolution I post
> > it here.
> >
> >
> > *** Sent via Developersdex http://www.developersdex.com ***
> > Don't just participate in USENET...get rewarded for it!
- Previous message: Sue Hoegemeier: "Re: error message not being logged to windows event log"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|