One such file that can become corrupt or lost is the MSCOMCTL.OCX file. Occasionally when a Windows user is installing or uninstalling a bunch of software, certain Microsoft Libraries can become unregistered. Hi, Component MSCOMCTL.OCX or one of its dependencies not correctly registered Solution 1: MSCOMCTL.OCX is a Microsoft Library Windows Common Controls file. We've been trying to find the reason behind this behaviour. Seaching the internet, we found that Windows Server 2008 R2 is compatible with this OCX ( ). So, probably, during installation the app configures something that only that user can see. Our conclusion is: If we install the app with the user, it works for him. But then, when trying to access as User_2, we received the same message. The app started to work normally for User_1 and administrator. After some tries, we installed the app again, logged as User_1. To test this theory, we added User_1 to the administrator's group. Our first thought was: lack of permissions. 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. To reproduce the scenario, we created a VM with Windows Server 2008 and installed the app (as administrator). One of our customers recently started to complain that our application does not work on Windows Server 2008 R2. In our company, we have an old VB6 application, based on COM+ and ADO 2.6.
0 kommentar(er)
