MSCOMCT2.OCX - File Format No Longer Supported ???

[Joacim Andersson]

Hi guys,

For some reason I'm no longer able to add the MS Common Controls-2 6.0 to a project. Everytime I do I get a 'File Format No Longer Supported' error message. So I'm not able to use the DateTimePicker control for some reason. I've tried unregister and reregister the component without any success. I've tried uninstalling and reinstalled SP6, but to no avail.

Anybody got any ideas what might have caused this?

[Static]

can u load other common controls no problem?

Maybe download a new file.. could be corrupted somehow??

[Joacim Andersson]

I don't have any problems with other components and I've tried replacing the OCX from another computer to no avail, even though it worked perfectly on the other computer.

[Hack]

Have you tried uninstalling and reinstalling Visual Basic itself?

[Joacim Andersson]

I don't think that would help since replacing the file didn't, there must be something else wrong...

[Hack]

I don't think that would help since replacing the file didn't, there must be something else wrong...

*grasping at straws he throws out* Registry corruption perhaps?

[Joacim Andersson]

I think I've found the reason, for some reason I don't have the mscomct2.oca file on my drive anymore. Some crappy uninstaller must have deleted it. Could somebody be so kind to upload that file for me?

[Harsh Gupta]

heres the file you wanted JA. JFYI, i am using Win98, VB 6 without any SP. so does it matter if you are working on other environment?

[Hack]

I'm running SP5...I suspect that does make a difference, but I'm not sure.

[Joacim Andersson]

Thanks guys, unfortunatly that didn't help do you have any other mscomct2.* files on your drive, maybe I'm missing something else?

[dglienna]

I was going to suggst reloading SP6, but if it's just the files you mentioned, here they are.

[Joacim Andersson]

Thanks dglienna, I have tried uninstalling and reinstalling SP6. Your files didn't help me either, I was sure that when I noticed that the OCA file was missing that that was the problem... but now after unregister the OCX I had and replaced all files and then register it again (which works without any errors), I still get the "File Format No Longer Supported" error message. This is starting to drive me crazy!

I don't have any problem running a compiled VB program that uses the component, but I can't open the source code for it anymore, and I can't add the component to a new project. The same kind of error appears if I try to use the component in another environment. I've tried with Delphi, Borland C++ Builder, as well as VC++ 6.0 and in VS.Net.

[dglienna]

Can you manually add it to components by browsing?

[Joacim Andersson]

No, I tried that aswell, same error. I've also tried to drag & drop the OCX file directly to the toolbox, same error.

[randem]

Can you add it to a new project?

[Joacim Andersson]

No, as I said I can't

I don't have any problem running a compiled VB program that uses the component, but I can't open the source code for it anymore, and I can't add the component to a new project.

[randem]

Sorry, I missed that. Have you tried removing the entry from the registry, cleaning the registry and re-adding it?

[Joacim Andersson]

Yes! I have used regsvr32 to unregister and reregister it. I have used two different registry cleaners, and I've even tried to manually remove all entries in the registry before running regsvr32 again... But the problem remains

[dglienna]

Look at the CLSID of another project that uses the control, and see if it is the same in the registry. It may be in there with two CLSID's.

[BrailleSchool]

I am running Win XP with SP6. files attached.

[randem]

What is the version of your MSCOMCT2.ocx file I have 6.1.97.82. It comes in VS SP6.

[Dave Sell]

If this is still a problem for you, you can try this. I have seen this before, where a filesystem gets corrupted, a file that sits on the corrupted piece of disk will stay right where it is, even if you copy a new version of the file on top of it - the new version gets corrupted.

Gotta ask - have you done the ol' CHKDSK /R?

[Joacim Andersson]

@Randem, I have the same version.
@Dave, yes I runned ChkDsk last night, and I didn't copy a new copy over it since I renamed my old file before extracting the files you guys have so kindly provided. But I will try putting them in another folder and register it there.

[randem]

Cleaning registry???

[Joacim Andersson]

Yes I have done several registry cleaning as I've mentioned already.

Yes! I have used regsvr32 to unregister and reregister it. I have used two different registry cleaners, and I've even tried to manually remove all entries in the registry before running regsvr32 again... But the problem remains

[randem]

Unregistering a components does not neccessarily mean that the registry information is cleared. What registry cleaner did you use? RegClean would probably work best for this situation. Did you make sure the compnent listing was not present. You could have multiple versions of the same control registered and it would not really be removed when you unregister it.

[randem]

Open up ********** and look in the Registered Components to see if you see it there.

[Joacim Andersson]

Well, I did use RegClean. I have also manually edited the Registry and removed all references to the component. VB's Component List did not have it listed, so I tried browsing to the file (which will cause VB to register it), it was then added to the component list and checked. But when I click the OK button the error shows up. The VB Component list also shows the path to the component you have selected so it can't be any other component. I've now also tried to put the component in another directory and registered it there with the same result.

I've tried deleting the component cache file and restarted my computer but VB still don't feel like loading it.

[blazermaniac]

Well, I did use RegClean. I have also manually edited the Registry and removed all references to the component. VB's Component List did not have it listed, so I tried browsing to the file (which will cause VB to register it), it was then added to the component list and checked. But when I click the OK button the error shows up. The VB Component list also shows the path to the component you have selected so it can't be any other component. I've now also tried to put the component in another directory and registered it there with the same result.

I've tried deleting the component cache file and restarted my computer but VB still don't feel like loading it.

I had this same problem with MSCOMCTL.OCX. I tried all of the suggestions without any luck. I then looked at the VBP file on our build machine and noticed that it had the following:
Object={831FDD16-0C5C-11D2-A9FC-0000F8754DA1}#2.2#0; MSCOMCTL.OCX
I tried changing mine from 2.0 to 2.1 and then to 2.2 and none worked. Next I looked in the registry and noticed that 2.2 pointed to the OCA file in C:\Program Files\Microsoft Visual Studio\VB98 whereas 2.0 and 2.1 pointed to C:\Windows\system32\MSCOMCTL.oca. My VBA file was still pointed at 2.2 so I removed the OCA file in C:\Program Files\Microsoft Visual Studio\VB98 and reloaded the project which generated an new OCA file and this solved the problem.

[Spooman]

blazer

Welcome to the Forums ..

Not bad for your 1st post !!
What on earth lead you to dig up (and find a solution for) a 12-year old thread?

Spoo

[TysonLPrice]

It may be twelve years old but I have been having that issue on a Windows 10 64 bit machine just this morning

I saw this post and it was --- wow!

[blazermaniac]

blazer

Welcome to the Forums ..

Not bad for your 1st post !!
What on earth lead you to dig up (and find a solution for) a 12-year old thread?

Spoo

Well believe it or not we're still using vb6 and I had my development VM crash and then after that started having the problem.

[blazermaniac]

It may be twelve years old but I have been having that issue on a Windows 10 64 bit machine just this morning

I saw this post and it was --- wow!

I'm glad you found it helpful!

[Spooman]

Well believe it or not we're still using vb6 and I had my development VM crash and then after that started having the problem.

Cool.
Aside from the solution, the impressive bit is that, as a 1st time poster, you had the inclination to do a Search as opposed to just posting a new thread.

Keep it up !!

Spoo

[skywalk]

It may be twelve years old but I have been having that issue on a Windows 10 64 bit machine just this morning

I saw this post and it was --- wow!

Thanks a bunch, I just had the same problem this afternoon!

[CDRIVE]

It is a mind blower that this thread seemed to run out of road in 2005. I'd love to read JA's input on this. After all it is his topic. What has he been doing about it all these years?

Chris

[PeterGedoens]

I had this same problem with MSCOMCTL.OCX. I tried all of the suggestions without any luck. I then looked at the VBP file on our build machine and noticed that it had the following:
Object={831FDD16-0C5C-11D2-A9FC-0000F8754DA1}#2.2#0; MSCOMCTL.OCX
I tried changing mine from 2.0 to 2.1 and then to 2.2 and none worked. Next I looked in the registry and noticed that 2.2 pointed to the OCA file in C:\Program Files\Microsoft Visual Studio\VB98 whereas 2.0 and 2.1 pointed to C:\Windows\system32\MSCOMCTL.oca. My VBA file was still pointed at 2.2 so I removed the OCA file in C:\Program Files\Microsoft Visual Studio\VB98 and reloaded the project which generated an new OCA file and this solved the problem.

Hi,

I was having the same problem with THREED32.OCX and later with Flp32a30.ocx. I search and tried to find a solution for many hours. Finally I found this Thread and particularly this *great* hint/solution.

Finding the .OCA Files and renaming them was the solution in my case.

Thank you very much - that saved me from a new Windows Installation

Cheers
Peter

[cleversonf]

Hi,

I was having the same problem with THREED32.OCX and later with Flp32a30.ocx. I search and tried to find a solution for many hours. Finally I found this Thread and particularly this *great* hint/solution.

Finding the .OCA Files and renaming them was the solution in my case.

Thank you very much - that saved me from a new Windows Installation

Cheers
Peter

Tive o mesmo problema essa semana após uma queda de energia. Win 10 X vb6, única forma que consegui resolver. Tentei de tudo, porém unica forma de resolver foi
1 - Desinstaslar o VB6,
2 - regsvr32 /u mscomctl.ocx
3 - dell mscomctl.ocx
4 - instalar vb6
5 - instalar sp6
Ai voltou a funcionar

[Shaggy Hiker]

Tive o mesmo problema essa semana após uma queda de energia. Win 10 X vb6, única forma que consegui resolver. Tentei de tudo, porém unica forma de resolver foi
1 - Desinstaslar o VB6,
2 - regsvr32 /u mscomctl.ocx
3 - dell mscomctl.ocx
4 - instalar vb6
5 - instalar sp6
Ai voltou a funcionar

The translated version courtesy of Google:

I had the same problem this week after a power outage. Win 10 X vb6, the only way I could solve it. I tried everything, but the only way to solve it was
1 - Uninstall VB6,
2 - regsvr32 /u mscomctl.ocx
3 - dell mscomctl.ocx
4 - install vb6
5 - install sp6
Then it started working again