Results 1 to 4 of 4
  1. #1
    5 Star Lounger
    Join Date
    Feb 2001
    Location
    Youngstown, Ohio, USA
    Posts
    705
    Thanks
    1
    Thanked 0 Times in 0 Posts

    Install problems (Office 2000)

    A sad tale of woe... <img src=/S/hairout.gif border=0 alt=hairout width=31 height=23> I was working in Access and tried to access the Linked Table Manager, whereupon Access gave me a <img src=/w3timages/censored.gif alt=censored border=0> error message. Fine. Not the first time. "I'll just run 'Detect & Repair' again," I thought to myself. In the middle of the process, Windows decided that it was an appropriate time to spontaneously reboot. (Nothing else was running at the time.)

    I couldn't restart the 'Detect & Repair' -- something to do with a different / incorrect version of Windows Installer -- and Office was really beginning to act up. Time for a complete uninstall & reinstall. Simple? Far from it. <img src=/S/sigh.gif border=0 alt=sigh width=15 height=15> The uninstall hung a couple of times, and then once it finally did run all the way through, Eraser2K didn't clean out the registry, leading to more problems during the next install. The biggest errors: two DLL's failed to register.
    <hr>Error 1904. Module C:Program FilesCommon FilesSystemOLE DBMSDAORA.DLL failed to register. HRESULT -2147024865. Contact your support personnel. (His response was an emphatic <img src=/S/shrug.gif border=0 alt=shrug width=39 height=15>.)

    Nearly identical error in C:WindowsSystemMSRCLR40.DLL, HRESULT -2147023739.<hr>
    After receiving these messages, I continued on and installed the SR-1a update which thankfully loaded without any more error messages. Everything now appears to be running normally, though it will be some time before I can get all of my settings back to normal.

    Now the questions... What would cause Office functions to start acting up and not working? If a feature is not working properly, shouldn't 'Detect & Repair' or even a reinstall be able to correct the problem? How do you correct installation problems if DLL's fail to register?

  2. #2
    Silver Lounger
    Join Date
    Apr 2001
    Location
    New York, New York, USA
    Posts
    2,328
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Install problems (Office 2000)

    As I see, nobody can answer you. In complicated configurations like yours, software conflicts are possible. Resolving software conflicts is very difficult and requires deep digging in the registry. Example from my experience: installation of Novell client AFTER Attachmate Extra!PC causes lost of CD-ROM drive. Installation in reverse order causes no problems. Both programs are for networking and have nothing in common with CD-ROM.
    What I

  3. #3
    5 Star Lounger
    Join Date
    Feb 2001
    Location
    Youngstown, Ohio, USA
    Posts
    705
    Thanks
    1
    Thanked 0 Times in 0 Posts

    Re: Install problems (Office 2000)

    <img src=/S/drop.gif border=0 alt=drop width=23 height=23> Good thing I wasn't expecting a simple, straight-forward answer. You are right about the number of programs; if not exact, it is a pretty good approximation.

    I've asked our tech-support 'Santa' for a new pc with the hard drive set up from scratch and all software installed fresh. Previously this would not have been possible, since I was 'lucky' enough to still be able to run some old legacy programs, but now we have a computer set up strictly to run these 'hate-em but need-em' programs (it doesn't even have Windows installed, just DOS).

    If I'm lucky all this will take place before Office or some other system decides to crash and burn again, and I won't need to worry about REGSVR32. If not, I think I'm almost due to run fdisk and format, even if I have to do it all on my own time.

  4. #4
    Lounger
    Join Date
    Nov 2001
    Location
    Buckinghamshire, UK
    Posts
    25
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Install problems (Office 2000)

    I have never had success with detect and repair in Access. Typically when one gets these errors one of your Access system files is corrupted. Way around it is to open a brand new Access database and do the File Import routine and bring in all of your tables, queries, macros, modules etc from the non working database into the new blank database. This way you are left with a fresh batch of access system files and more often than not a working database again. The only thing you'll lose is your custom toolbar...that's if you had one.

    If you do this and still get the error messages then I would manually register the DLL's and not use the ones that remain on your HDD but get them from another working copy of your vesion of Access.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •