Possible issues with MDAC

[blbumpus]

Hi Shane!
Not sure if it will help my issue below, but I was wondering if you could upload the win7 32bit MDAC files in the ADO folder? I did try and copy the same contents from one PC to the one I am having issues on, but even as local admin, it did not allow me to copy the files?

The issue is I have an application that after trying to launch the app, it comes back with an error that says the "Main server is not responding, trying alternate server...10.68.16.29..." However I can tracert and ping that server with no problem. I have deleted the NIC card, rediscovered it and reinstalled the drivers already as well. I don't think the issue is a network connection through infrastructure though.

Tested the MDAC with your tool....
…..as it wants to connect to test.mdb using ADO, it says the Provider cannot be found, possible it is not installed..
 
Tried running “Repair MDAC & MS Jet” with repair tool….restarting windows now….below is the log file after repair attempt was run…
System Variables
--------------------------------------------------------------------------------
OS: Windows 7 Enterprise
OS Architecture: 32-bit
OS Version: 6.1.7601
OS Service Pack: Service Pack 1
Computer Name: MARNOLD-DTA
Windows Drive: C:\
Windows Path: C:\WINDOWS
Program Files: C:\Program Files
Current Profile: C:\Users\mmarnold
Current Profile SID: S-1-5-21-146353876-357311334-2057200603-43929
Current Profile Classes: S-1-5-21-146353876-357311334-2057200603-43929_Classes
Profiles Location: C:\Users
Profiles Location 2: C:\WINDOWS\ServiceProfiles
Local Settings AppData: C:\Users\mmarnold\AppData\Local
--------------------------------------------------------------------------------

System Information
--------------------------------------------------------------------------------
System Up Time: 0 Days 02:20:12

Process Count: 66
Commit Total: 1,08 GB
Commit Limit: 3,91 GB
Commit Peak: 1,25 GB
Handle Count: 21404
Kernel Total: 337,77 MB
Kernel Paged: 280,27 MB
Kernel Non Paged: 57,50 MB
System Cache: 1,07 GB
Thread Count: 939
--------------------------------------------------------------------------------

Memory Before Cleaning with CleanMem
--------------------------------------------------------------------------------
Memory Total: 1,96 GB
Memory Used: 790,49 MB(39,4741%)
Memory Avail.: 1,18 GB
--------------------------------------------------------------------------------

Cleaning Memory Before Starting Repairs...

Memory After Cleaning with CleanMem
--------------------------------------------------------------------------------
Memory Total: 1,96 GB
Memory Used: 712,43 MB(35,5763%)
Memory Avail.: 1,26 GB
--------------------------------------------------------------------------------

Starting Repairs...
   Started at (21.07.2014 15:10:24)

08 - Repair MDAC/MS Jet
   Start (21.07.2014 15:10:27)
   Running Repair Under Current User Account
   Running Repair Under System Account
   Done (21.07.2014 15:10:37)

Cleaning up empty logs...

All Selected Repairs Done.
   Done at (21.07.2014 15:10:37)
   Total Repair Time: 00:00:15

[Shane]

You should run my Windows repair tool and run the permissions repairs with it as well. After you run the permissions repairs you should be able to replace the files since you will have permissions after that

I can load up windows 7 32bit in vmware and grab the files for you, but I only have Windows 7 English, I dont know if the files are different on non English version of Windows.

Did you also check the ado files to see if any where missing?

Shane

[blbumpus]

Thanks for the advice Shane.....will do that now. The OS is all English, but with German language pack. I did compare the ADO folder with another PC ADO folder and all the files & folders were there and the size of each were the same. Perhaps after repairing the permissions it will allow me to run the app? Nonetheless I can replace the ADO files and try again. I will keep you posted.
b

[blbumpus]

Hi Shane,
I tried the folder copy of ADO from another PC after the repair permissions with tool, but same issue, even after reboot.....no permissions to copy.
b

[Shane]

I got your email and you said it is a corporate system, is the system on a domain and does your account have full admin rights? Because if it doesnt then the repairs wouldnt work because they wouldnt have permissions.

Shane

[blbumpus]

Hi Shane,
Yes on a domain, but my admin account is with elevated priviledges. The files within the two ADO folders appear to be the exact same as I compared there sizes as well and there are no files missing. So I am wondering if this could be something different?

billy

[Shane]

Could be something missing for the files from the registry.

On the other machine that you compared the broken on to, did you run the mdac test on it to make sure it works as well?

Shane

[blbumpus]

Yes it works on the other machine.
b

[blbumpus]

Hi Shane,
I seen you had an update version of the Windows repair tool, so I downloaded it as it also had improvements with Reset file permission....this allowed me to copy the ADO folder from one PC to another successfully...thanks for that update....nonetheless I still receive the same error with the test_MDAC tool, which is:
Starting Test.
Date: 25.07.2014 Time: 10:33:01
''''''''''''''''''''''''''''''''''''''''''''''''''''''''
Connecting To Test.mdb using DAO...
--Successful
Opening Table...
ERROR!: 510 - Unknown
''''''''''''''''''''''''''''''''''''''''''''''''''''''''
Connecting To Test.mdb using ADO...
ERROR!: 3706 - Provider cannot be found. It may not be properly installed.
''''''''''''''''''''''''''''''''''''''''''''''''''''''''
Done, Test Complete.

b

[Shane]

Yeah the new file permissions repair now runs the repair as the trusted installer, which has access to everything. Where as the old version ran the repair as the system account, and since it doesnt take the owner of the files it couldnt change the permissions on any trusted installer own files. It can now :-D

I have a feeling the problem is in the registry and not the files. The MDAC repair simply registers all the dll files for mdac, which as long as there is permissions it should work.

Now that you have file permissions also run the registry permissions, the register system files and the repair mdac. If that still doesnt do it then we will have to look deeper in the registry to find what keys are missing.

Shane