In our company, we have an old VB6 application, based on COM+ and ADO 2.6. One of our customers recently started to complain that our application does not work on Windows Server 2008 R2. To reproduce the scenario, we created a VM with Windows Server 2008 and installed the app (as administrator). The app worked perfectly. But then we logged with another user (User_1) on the machine, and we received the following message: 339 - Component 'MSCOMCTL.OCX' or one of its dependencies not correctly registered: a file is missing or is invalid. Our first thought was: lack of permissions. To test this theory, we added User_1 to the administrator's group.
It didn't work. After some tries, we installed the app again, logged as User_1. The app started to work normally for User_1 and administrator.
Download Microsoft Visual Basic 6.0 Common Controls from Official Microsoft Download Center. New Surface Pro 6. Stand out from the ordinary.
Onimusha psp games. Description Capcom’s riveting samurai adventure returns! Improved controls allow players to move and fight with analog-stick precision. This version includes the original game’s intense swordplay and dramatic revenge story, plus a host of enhancements.
But then, when trying to access as User_2, we received the same message. Our conclusion is: If we install the app with the user, it works for him. For another user, it does not work.
So, probably, during installation the app configures something that only that user can see. Seaching the internet, we found that Windows Server 2008 R2 is compatible with this OCX ().
We've been trying to find the reason behind this behaviour. Anyone has a suggestion? Hi, Component MSCOMCTL.OCX or one of its dependencies not correctly registered Solution 1: MSCOMCTL.OCX is a Microsoft Library Windows Common Controls file. Occasionally when a Windows user is installing or uninstalling a bunch of software, certain Microsoft Libraries can become unregistered.
Trin arivel annaoncement tone mp3. • Continuously updated library • Removal of the attribution / credit link requirement • Get all our sound effects in the original, higher quality.WAV format as well as.mp3 • Loads of extra free sounds exclusively for Gold members added weekly • Show more results per page (up to 100) • Lists - organise our sounds into unlimited personalised lists • Quicker downloads - you won't need to wait after 3 downloads!
One such file that can become corrupt or lost is the MSCOMCTL.OCX file. Then, when the user runs a program or application that requires or is dependent on this file, they may be presented with the following error: Component 'MSCOMCTL.OCX' or one of its dependencies not correctly registered: a file is missing or invalid MSCOMCTL.OCX error screenshot: How to Correct or fix this dependency error: 1.
First search your local drive for MSCOMCTL.OCX to see if it is missing. The path to the file is typically: C: WINDOWS system32 (or) typically C: Winnt system32 COMDLG32.OCX 2. If the file is missing you can download it 3. Once downloaded, click the MSCOMCTL.exe and extract the file to your C: WINDOWS system32 directory (or) C: Winnt system32 COMDLG32.OCX Note: Some users may need to perform this additional step to register the file: 1. Click Start -> Run and type REGSVR32 MSCOMCTL.OCX Solution 2:well the best alternative is to go with Package and deployment wizard. But, If you'd like to register them manually through the code then use this. Private sub Form_load() Shell 'REGSVR32 /s c: winnt system32 mstask32.ocx' End Sub Thanks and Best Regards Anil Inampudi.
Sample Code Disclaimer NOTE - Disclaimer By using the following materials or sample code you agree to be bound by the license terms below and the Microsoft Partner Program Agreement the terms of which are incorporated herein by this reference. These license terms are an agreement between Microsoft Corporation (or, if applicable based on where you are located, on of its affiliates) and you.
Any materials (other than sample code) we provide to you are for your internal use only. Any sample code is provided for the purpose of illustration only and is not intended to be used in a production environment. I have the exact same problem.
In my company we have an older application that runs on terminal services. I noticed that only the users that started the application (and were previocly logged in on the server at some point) before the components are registered don't have an error message. If a new user tries to start the application the error Component 'SomeCommponent.OCX' or one of its dependencies not correctly registered: a file is missing or invalid SomeCommponent.OCX apears. I need to register the component again so that the new users don't get the error.
Anny suggestions on how to register ocx or dll components for all users? Confirmed damemalov's solution.
Windows 2008 R2 Datacenter Edition. Running regsvr32 mscomctl.ocx in C: Windows SysWOW64 resulted in success message 'DllRegisterServer in mscomctl.ocx succeeded'. However, our old VB 6.0 app continued to fail with the message 'Run time error '339' Component 'MSCOMCTL.OCX' or one of its dependencies is not correctly registered; a file is missing or invalid.' The error was user-specific. The user who performed the install was able to execute the application, but other users were not.
Ironically, running the application as administrator also failed. Action: Unregistered mscomctl.ocx in SysWOW64, made a copy in C: Windows, and registered the copy using the version of regsvr32 in SysWOW64. E.g., from a command line or batch file, running as administrator: C: Windows SysWOW64 regsvr32 C: Windows mscomctl.ocx Works. Hi, We have windows 2003 x86 currently running vb application. We are migrating to new windows 2008 R2 x64 OS and getting error for MSCOMCT2.OCX We had installed ms office pro plus 2010 for x86.