Simple Port Forwarding and Error 3633

[Walt46]

the software installs OK but error 3633 (program can not start) when program is
run.  Operating System is Vista Ultimate.

You Suggested a MDAC test.

Results:
Starting Test.
Date: 7/8/2011 Time: 10:02:39 AM
''''''''''''''''''''''''''''''''''''''''''''''''''''''''
Connecting To Test.mdb using DAO...
ERROR!: 3633 -
''''''''''''''''''''''''''''''''''''''''''''''''''''''''
Connecting To Test.mdb using ADO...
ERROR!: 3706 - Provider cannot be found. It may not be properly installed.
''''''''''''''''''''''''''''''''''''''''''''''''''''''''
Done, Test Complete.
''''''''''''''''''''''''''''''''''''''''''''''''''''''''

Looks like I am missing a File, but What?

Walt46

[Shane]

For some reason ADO & DAO (MDAC) are corrupt or missing on your system.

These are Microsoft database components. So lets see if a system file check will replace the files.

Open a command window and put in
sfc /scannow

Wait for it to finish. Then reboot.

Once back up run my repair tool.
http://www.pcwintech.com/files/shanes_toolbox/Repair_MDAC.exe

After that run the test tool again.
http://www.pcwintech.com/files/shanes_toolbox/Test_MDAC.exe

Let me know how it goes

Shane

[Walt46]

I have run a sfc /scannow then a repair and a test of mdac.  Results are the same as before
Scannow did mention in log that there were damaged /corrupted files that could not be repaired or replaced. I could only identify "themeui.dll" and I believe that this is a nonesential file.

Starting Test.
Date: 7/8/2011 Time: 5:16:47 PM
''''''''''''''''''''''''''''''''''''''''''''''''''''''''
Connecting To Test.mdb using DAO...
ERROR!: 3633 -
''''''''''''''''''''''''''''''''''''''''''''''''''''''''
Connecting To Test.mdb using ADO...
ERROR!: 3706 - Provider cannot be found. It may not be properly installed.
''''''''''''''''''''''''''''''''''''''''''''''''''''''''
Done, Test Complete.
''''''''''''''''''''''''''''''''''''''''''''''''''''''''

What else can be suggested??

Walt46

[Shane]

Looks like the best thing to do is replace the files manually.

You said your on Vista. Is it 32 or 64 bit?

Shane

[Walt46]

Vista Ultimate 32 bit

Walt46

[Shane]

OK try this.

Extract the dll I attached and put it

C:\Program Files\Common Files\microsoft shared\DAO\

Then run my tester and see if DAO works.

Shane

[Walt46]

Successfully downloaded DAO, but the file in the common\microsoft shared\DAO directory 
is described as a system file and will not let me replace or delete. I have administrator auth
but this evidently is higher than that.

Suggestions?

Walt46

[Shane]

You may need to turn off the UAC to get access to it.

Thats the DAO file section. My program can use it or ADO.

Do me a fav and take a screen shot of this folder
C:\Program Files\Common Files\System\ado

I can then see if any of the ado files are missing.

We just need one of them to work

Shane

[Walt46]

OK! Finally replaced the DAO file by getting permission through Security preferences (TrustedInstaller).
Ran the fix and repair and test for DAO file and there has been no change in the log report (failure).
screen print of ado directory is at attachment.  What is my next step??

Walt46

[Shane]

Odd, no files are missing. Yet your ADO & DAO are broken.

Now I think I know what might be the problem. On my system a month ago I had scripting support break on it. When I followed the repair steps of registering the files for it one of the files would give me an error when I would try to register it when it shouldn't give an error. SO because of the file not getting registered my windows scripting wouldn't work.

Turns out the reg keys the registering uses where locked some how!
Once I fixed the reg permissions the files registered like they should and the scripting worked again.

Since none of the files are missing on your system I think it might be a reg permission problem.
So run my tool, it will take a little while.
http://www.pcwintech.com/files/shanes_toolbox/Repair_Registry_Permissions.exe

Once it is done run the mdac repair tool again, it registers the mdac files. When it is done reboot.

Then lets see what the mdac test shows

Shane

[Walt46]

I followed all steps, rebooted and ran Test MDAC
then ran Repair MDAC, then ran Test MDAC again.
See screen print at attachment. It appears that
I've picked up a new error - hope that it indicates
where the problem lies.  What is my next step.

Walt46

[Shane]

Looks like we are making progress

I am making a repair windows tool for a new site I am partners with. I want to find out whats broken with this and a proper fix so I can add it to the new program.

Email me and we will get on msn or yahoo chat and I will dig into it 

Shane