Main Forum > Tweaking.com Support & Help

08 - Repair MDAC/MS Jet fails

(1/9) > >>

phochief:
Everytime I run tweaking repair, it gets stuck on 08 - Repair MDAC/MS Jet

There is only low sporadic cpu activity every 15 seconds at this point, and the drive writes a bit sporadically too.  I'm running Tweaking Repair in a Safe boot window.  Here's what it says the the log window:

08 - Repair MDAC/MS Jet
   Start (12/30/2017 1:33:05 AM)
   Running Repair Under Current User Account
   Running Repair Under System Account

The current repair has failed to start for over 30 sec.
Trying Again....

   Running Repair Under System Account

The current repair has failed to start for over 30 sec.
Trying Again....

   Running Repair Under System Account

The current repair has failed to start for over 30 sec.
Trying Again....

   Running Repair Under System Account
   Done (12/30/2017 1:44:03 AM)

   Done, but failed, at (12/30/2017 1:44:03 AM)
   Total Repair Time: 00:15:55

The current repair has failed to start 4 times.
Something is keeping the repair from running.

Try running the repairs in Windows Safe Mode. (This will keep 3rd party programs from getting in the way of the repairs)
If the repairs still fail then please post in the Tweaking.com forums for support.

Thanks for any insight or bug fix.
David

Boggin:
If you use Office, go into Programs and Features by going Start - type appwiz.cpl and press enter.

Right click on Office and select Repair, but if it isn't Office related then I'll pass this on to see what else can be causing it.

machinehead:
Perhaps I should start a new  thread but  I  have  exactly the opposite issue.
08 has been running for  two hours now.
How long should I let it run?
What's the best way to exit it if I give up on it?

machinehead:
I realized a bit more info might be useful.
The program does do a brief CPU usage and Drive Write every 7 seconds.
And, if it matters, I do have a database with a lot of entries.

Boggin:

--- Quote from: machinehead on January 01, 2018, 03:20:44 pm ---I realized a bit more info might be useful.
The program does do a brief CPU usage and Drive Write every 7 seconds.
And, if it matters, I do have a database with a lot of entries.

--- End quote ---

Yes, you should open your own thread as the reasons could be different.

It may well be because of the size of your database but as long as the CPU is still working, Shane has said before that the program is working.

I can't tell you when to give up on it because that may be normal for your machine.

Navigation

[0] Message Index

[#] Next page

Go to full version