asked on

Receiving an error from VB.net after upgrading from Office 2013 32-bit to 64 bit

I have an application (see screen shot attached) that requires Outlook to function. The application inserts an event into the default Outlook calendar. The application has been working and it still works on user machines; but not mine which is the development machine. Further background, I had Visio 2007 and Office 2007 on this same machine that were all removed in favor of just this version. I received a message that I should run the repair on these applications which I disregarded because they were all removed as far as I can/could see. Are they? Is there somewhere else to look?

Specifically this began to occur after the Office 2013 "upgrade" from 32 bit to 64 bit which I did to accommodate some other applications I'm developing. I've read around that there is a registry key not removed from a previous uninstall. That notion seems to go along with the error message in the attachment.

Have you run into this specifically? What would you suggest to repair the problem?

Thank you!
Doc1.pdf

it_saige

Please post the contents of the following registry keys:

HKEY_CLASSES_ROOT\CLSID\{0006F03A-0000-0000-C000-000000000046}
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{0006F03A-0000-0000-C000-000000000046}
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Classes\CLSID\{0006F03A-0000-0000-C000-000000000046}

-saige-

SchoolTeacher54

ASKER

Thank you for looking at this for me. I appreciate the work!
HKEY.pdf

it_saige

Take a backup of the following keys:

HKEY_CLASSES_ROOT\CLSID\{0006F03A-0000-0000-C000-000000000046}
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{0006F03A-0000-0000-C000-000000000046}

And then remove the following keys from within each:

InprocHandler32
LocalServer32
ProgID
Typelib

DO NOT REMOVE THE INPROCSERVER32 KEY!!!

These are the remnant keys from the 32-bit installation.

You can copy the following into a text file, save it with a .reg extension and run it (by double clicking on the file) in order to remove these keys automatically:

Windows Registry Editor Version 5.00

[-HKEY_CLASSES_ROOT\CLSID\{0006F03A-0000-0000-C000-000000000046}\InprocHandler32]
[-HKEY_CLASSES_ROOT\CLSID\{0006F03A-0000-0000-C000-000000000046}\LocalServer32]
[-HKEY_CLASSES_ROOT\CLSID\{0006F03A-0000-0000-C000-000000000046}\ProgID]
[-HKEY_CLASSES_ROOT\CLSID\{0006F03A-0000-0000-C000-000000000046}\Typelib]

[-HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{0006F03A-0000-0000-C000-000000000046}\InprocHandler32]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{0006F03A-0000-0000-C000-000000000046}\LocalServer32]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{0006F03A-0000-0000-C000-000000000046}\ProgID]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{0006F03A-0000-0000-C000-000000000046}\Typelib]

Open in new window

You may need to restart your computer in order for these changes to take affect.

-saige-

SchoolTeacher54

ASKER

I didn't make it back to my office today. I wanted you to know that I received the message and I really appreciate the thoughtfulness and the complete work that you put in this.

I'll work on this Tuesday afternoon and let you know how it worked out for me.

I said it once but I'll say it again. You really did good!

SchoolTeacher54

ASKER

Hi,

It looks like the keys were removed by your suggestion of auto removing the keys. I have an additional error after doing so and running the vb 2015 file. I've included a shot of the error when (trying) to run it. I also captured the keys that show that the keys were in fact removed as intended.

Thoughts?
Retrieving-the-COM-class-factory-for.pdf

ASKER CERTIFIED SOLUTION

it_saige

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SchoolTeacher54

ASKER

Agreed. I'll let you know how it turns out.

SchoolTeacher54

ASKER

Here is what I ended up doing.

1. I uninstalled Office 2013 using the control panel.
2. I reinstalled Office 2013 and had the same error so I uninstalled again and restarted
3. I used the MSO 2013 Quick fix tool that removed another 7 Reg keys.
4. I used the MSO 2007 Quick fix tool which also removed another 8 keys. I had previously had Visio 2007 installed. I removed 2007 at the same time I originally installed MSO 2013. The uninstaller gave me a message that I should go back and repair MSO 2007. My problem was that there were no components showing in the control panel. I think that it was seeing the stray Reg keys.
5. I reinstalled Office 2013 64-bit and it runs fine.

In summary I could have uninstalled MSO 2013, run the quick fix tool and reinstalled. It probably would have been fine.

Thank you for your help!