vb6 app no longer connects to Access DB on Term Server 2003

[Guest]

Hey all--

At work, we recently upgraded the Terminal Server from the 2000 version to
Windows Server 2003 R2 Enterprise Edition SP1. Actually, the 2000 box had a
catastrophic disc failure and is DEAD.

Anyways, a vb6 application that connects to an Access database is now
throwing an error on this new Terminal Server, specifically:
-2147024769 Automation Error The specified procedure could not be found

The form of the connection is:

Global gconn as New ADODB.Connection

gconn.open Provider=Microsoft.Jet.OLEDB.4.0;Data
Source=C:MyDB.mdb;Mode=ReadWrite;Persist Security Info=False;Jet
OLEDBatabase Password=abcDEF!@#

I even tried reducing the connection string by removing the password (as
well as from the database), not specifying the Persist Security Info, and not
specifying the Mode.

I have seen the kb articles that reference this (like kb: 839428), but as I
said, we already have MDAC 2.8 SP2 On Windows Server 2003 SP1 (using
ComponentChecker 2.0)--mostly version 2.82.1830.0.

We have uninstalled and re-installed every MDAC between 2.5 and 2.8 (with
reboots, shutting off virus protection during the install, etc.). We have
done numerous searches on the web, most of which point to a bad MDAC install.
The server is completely up-to-date as far as the software version is
concerned. The MDAC 2.8 is also the latest/greatest for the server.

Furthermore, we have tried simplifying the connection string by removing the
password, ensuring no spaces in the path, changing the path back to the C:\
(to rule out network drive mapping), etc.

References in the app include:
Visual Basic for Applications
Visual Basic runtime objects and procedures
Visual Basic objects and procedures
OLE Automation
Microsoft Data Binding Collection VB6.0 (SP4)
Microsoft ActiveX Data Objects 2.8 Library
Microsoft ADO Ext. 2.8 for DDL and Security
Microsoft Jet and Replication Objects 2.6 Library
Microsoft Scripting Runtime
Microsoft Word 11.0 Object Library

I've regsvr'd the jet 4.0
I've tried installing Service Pack 6 for Visual Basic 6.0: Run-Time
Redistribution Pack (vbrun60sp6.exe) on the server.
I've verified that I can create a lock file on the database by opening it
manually (it opens with no problem).
I've paired down the connection string to its most basic (struck the
password from the string and then removed the password from the database,
removed the persist security info, removed even the mode=Read/Write part).

The same connection string works fine on Windows 2000 and Windows XP PCs,
just not on Windows Server 2003. We even tried it on Windows Server 2003
Standard and got the same error.

Does anyone know what we can do to get this working? I'm at wits end and
have already posted in the Windows Server 2003 ng.

Thanks in advance.

* i_j_hutch *

 

[Guest]

Hi, you may want to check out my post below, it refers to a similar problem,
i.e. an automation error related to the CurrentProject.Connection property of
MS Access...

The trick was to re-install the appropriate MDAC in a very funky way...

This worked for me, hope it is of help.

.... ... ...

Ok, here's the solution -or, in any case, what worked on my pc- for this
mysterious bug with CurrentProject.Connection...

Here's the saviour-resource ...

http://msauer.mvps.org/images/error.pdf

Steps (1) & (2) are useful for checking MDAC versions and if there are any
missing files there, but the 'beef' comes with (3) & (4).

For (3), use WinZip to extract the files of the MDAC that corresponds to
your version of Windows (e.g. MDAC 2.8 SP1) to a temporary folder.

For (4), again use WinZip to extract the files of "mdacxpak" in another
folder.

Then go to folder C:\Windows\inf, find "mdac" (setup information file),
right-click on it and select install as the instructions specify.

During installation, you will probably need to use the Search utility of
Windows to locate various DLLs (i certainly had to to locate 4-5 DLLs in
various folders).

In my case the problem was solved once the pc was rebooted.