Previously working Macro-enabled file now throwing "Class not registered"

[jbayko]

Hello -

I have a large Excel file with a bit of code that I found on the web and copied because it accomplished exactly what I needed. It worked fine for months.. I subsequently had a laptop issue and had to reset my Windows installation, which also required me to re-download Office 365 from the MS website and install it again. Now the Excel file throws this error upon file save: "Run-time error '-2147221164 (80040154)':" and "Class not registered".

When I click Debug in the pop-up window, it appears to be choking on this line of code:
Set GetJavaScriptControlObject = CreateObject("MSScriptControl.ScriptControl")

I tried implementing some suggestions I found on a Google search but kind of hit a dead end. A lot of this is Greek to me. Can anyone help identify a cause / fix for this?

Much appreciated!
jbayko

[dotchiejack]

If you go to the vba Editor (alt + F11) -> Tools -> References do you have a line that says missing? If so, uncheck it and see if this solves your problem.
Also make sure that in the references Microsoft Office xx.x Object library is checked. (xx.x is the officeversion for example 16.0)

[jbayko]

If you go to the vba Editor (alt + F11) -> Tools -> References do you have a line that says missing? If so, uncheck it and see if this solves your problem.
Also make sure that in the references Microsoft Office xx.x Object library is checked. (xx.x is the officeversion for example 16.0)

Thank you for your reply. Unfortunately, I don't believe either of these suggestions is relevant (see screenshot linked below). I don't see anything which says "missing", and "Microsoft Office 16.0 Object Library" is checked.

Do you have any other suggestions? This constant error message is very annoying and obviously is causing functionality in my workbook to fail.

Attachment 660629

[Marc L]

Hi,

as a Windows issue see with your IT …

[jbayko]

Hi,

as a Windows issue see with your IT …

Hmmmm...sitting on my couch, unfortunately, my IT is me. Thanks anyways.

If anyone else has suggestions, I'd greatly appreciate it.

[Marc L]

By default this error message means your Windows does not have the necessary, whatever a file or a key in the Registry database.

The other error sources as yet stated can be a missing reference in error in the references list or an add-in which badly interferates …

[jbayko]

If you go to the vba Editor (alt + F11) -> Tools -> References do you have a line that says missing? If so, uncheck it and see if this solves your problem.
Also make sure that in the references Microsoft Office xx.x Object library is checked. (xx.x is the officeversion for example 16.0)

Hi dotchiejack. I just noticed something. This Microsoft Office xx.x Object library which you say I need to have checked. Well, I noticed that this DLL is not in the location it is expecting. I also performed a search of my entire C: drive and that DLL is nowhere to be found. How does this happen? I installed MS Office 365 without any customization. What am I supposed to do now?

Screen shot of Excel > VBA Editor > Tools > References (shows file path where it is expecting Microsoft Office xx.x Object library to be):
Attachment 660660

This directory on my computer with hidden files showing, but DLL nowhere to be found:
Attachment 660661

[dotchiejack]

Attachments are invalid.

[rorya]

An error with CreateObject is unlikely to be due to a reference issue, since it just looks up the class in the registry and doesn't depend on references.

Are you using 32bit Office (not Windows) or 64bit?

Also, you should really mention that you have cross-posted this in other forums.

[jbayko]

An error with CreateObject is unlikely to be due to a reference issue, since it just looks up the class in the registry and doesn't depend on references.

Are you using 32bit Office (not Windows) or 64bit?

Also, you should really mention that you have cross-posted this in other forums.

Hello -

Sorry for the late reply. This problem is important to me. I didn't realize the cross posting thing was a faux pas. I'll be more careful next time.

To answer your question, I just verified that my Office installation is 64bit.

Really hope you can help me

[rorya]

As far as I know, the script control is a 32bit component and there isn't a 64bit version of it, so it won't work on 64bit Office.

[jbayko]

As far as I know, the script control is a 32bit component and there isn't a 64bit version of it, so it won't work on 64bit Office.

Yes! Installing the 32-bit version worked. Thank you so much.