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
SchoolTeacher54Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

it_saigeDeveloperCommented:
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-
0
SchoolTeacher54Author Commented:
Thank you for looking at this for me. I appreciate the work!
HKEY.pdf
0
it_saigeDeveloperCommented:
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-
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

SchoolTeacher54Author Commented:
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!
0
SchoolTeacher54Author Commented:
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
0
it_saigeDeveloperCommented:
Did you try restarting the computer?  If you did, then the next course of action is probably unistalling and reinstalling Outlook/Office.  I would recommend, though, that you ensure that the keys we discussed earlier are removed after the uninstall is completed.  From the research I have done, this error occurs because the operating system cannot correctly determine the dll path of the ComObject you are loading because of duplicate entries between the 32-bit and 64-bit registry entries.

We could probably try to reverse the changes we made by reloading the key backups that were made earlier.  And then perform the removal from the WOW6432Nodes of both the HKEY_CLASSES_ROOT and HKEY_LOCAL_MACHINE tree's but it's probably just simpler to uninstall and reinstall.

-saige-
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
SchoolTeacher54Author Commented:
Agreed. I'll let you know how it turns out.
0
SchoolTeacher54Author Commented:
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!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic.NET

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.