I get Run-time error "339"?
If you get an error message such as the following:"Run-time error 339 component 'MSCOMCTL.OCX' or one of the dependency's not correctly registered: a file is missing or invalid"
Then you will have to register the file MSCOMCTL.OCX
To do this:
1. Go to Start and then Run
2. Type the following bold text into the 'Run' window:
REGSVR32 MSCOMCTL.OCX
3. Click 'OK' and SwiftKit should now work.
IF for some reason that doesn't work, try this method.
1. Make sure that you are the Administrator of your computer.
2. Go to Start than Accessories and right-click Command prompt and select Run as Administrator
3. Enter in REGSVR32 MSCOMCTL.OCX
 |
Article Options |  |
26% 
74% 
from a total of 23 votes.
|
Visitor Comments | |
Whenever I tried this, I got an error message. It reads: "DllRegisterServer in MSCOMCTL.OCX failed. Return code was: 0x8002801c" Do you know what to do?
I don't get mscom, i get Run-Time error '339' Component 'shdocvw.dll' or one of it's dependencies not correctly registered: a file is missing or invalid What should i do?
If that doesn't work you need to enter into a command promp as the administrator "REGSVR32 comdlg32.ocx" and press enter that should fix it
I got= Run-Time error '339': Component 'ieframe.dll' or one of its dependencies not correctly registered: a file is missing or invalid. What should i do?
well this doesnt help me mine says "run-time error '339' component 'comdlg32.ocx' or one of its dependencies not correctly registered: a file is missing or invalid. i just got my internet turned back on & it updated when i turned it on & this error pops up. please help
Worked for me, thanks. @craig Read comment #3
For anyone who gets an error with a different file name/component, e.g. "Run-Time error '339': Component 'ieframe.dll' or one of its dependencies not correctly registered: a file is missing or invalid.", try using the file name (for this example: regsvr32 ieframe.dll ). Same for errors like "component 'comdlg32.ocx' or one ..." use: regsvr32 comdlg32.ocx imxtrabored: I think you need to run the command prompt as an administrator (look at the last three steps of the guide).
