.OCX Errors are thrown when the VEDA application is installed under a different user and is being run from a different user, without registering dependencies appropriately.
For example, say if VEDA FE and VEDA BE were installed on my machine using ‘ABC’ Account, who does NOT have Administrator privileges. Now, if VEDA FE or VEDA BE were to be run from another account, say ‘XYZ’ Account, a .ocx error will be thrown.
A few common dependecies that I have observed so far are:
a) VEDA_FE & VEDA_BE: COMDLG32.OCX
b) VEDA_FE & VEDA_BE: MSCOMCTL.OCX
c) VEDA_FE: COMCT332.OCX
d) VEDA_BE: MSFLXGRD.OCX
e) VEDA_BE: TABCTL32.OCX
To resolve this error, the steps are quite simple.
1. Note down the name of the .OCX dependency which is raising an exception. The name of this dependency can be found in the error dialogue box as shown below.
2. Run Command Prompt as Administrator: Search your system for 'cmd' (Command Prompt) and once found, right click over it to select 'Run As Administrator'.
3. Navigate to VEDA Folder: If the .ocx error was thrown while running VEDA-FE, navigate to VEDA_FE sub-folder, under parent folder named, VEDA in the command prompt window. Navigate to VEDA_BE folder if the exception was raised while running VEDA_BE.
4. Registering Dependencies: In the command prompt console, run the following 2 commands, in exactly the same sequence:
a. regsvr32 /u.OCX
Example: regsvr32 /u COMDLG32.OCX
Upon running this command, a dialogue box, as shown below, will be displayed.
b. regsvr32.OCX
Example: regsvr32 COMDLG32.OCX
Upon running this command, a dialogue box, as shown below, will be displayed.
This step must be done for the .OCX Dependency raising an exception.
5. After all dependencies have been resolved, you need to run your VEDA-FE or VEDA-BE application as Administrator. To do so, right click over VEDA_FE.exe or VEDA_BE.exe (located in VEDA\ VEDA_FE or VEDA\ VEDA_BE folder, respectively) and select 'Run as Administrator'.
Once you have run the specific VEDA application as Administrator and all dependencies are registered successfully, you can run it for any user by simply double clicking the .exe or shortcut on Desktop.
For example, say if VEDA FE and VEDA BE were installed on my machine using ‘ABC’ Account, who does NOT have Administrator privileges. Now, if VEDA FE or VEDA BE were to be run from another account, say ‘XYZ’ Account, a .ocx error will be thrown.
A few common dependecies that I have observed so far are:
a) VEDA_FE & VEDA_BE: COMDLG32.OCX
b) VEDA_FE & VEDA_BE: MSCOMCTL.OCX
c) VEDA_FE: COMCT332.OCX
d) VEDA_BE: MSFLXGRD.OCX
e) VEDA_BE: TABCTL32.OCX
To resolve this error, the steps are quite simple.
1. Note down the name of the .OCX dependency which is raising an exception. The name of this dependency can be found in the error dialogue box as shown below.
2. Run Command Prompt as Administrator: Search your system for 'cmd' (Command Prompt) and once found, right click over it to select 'Run As Administrator'.
3. Navigate to VEDA Folder: If the .ocx error was thrown while running VEDA-FE, navigate to VEDA_FE sub-folder, under parent folder named, VEDA in the command prompt window. Navigate to VEDA_BE folder if the exception was raised while running VEDA_BE.
4. Registering Dependencies: In the command prompt console, run the following 2 commands, in exactly the same sequence:
a. regsvr32 /u
Example: regsvr32 /u COMDLG32.OCX
Upon running this command, a dialogue box, as shown below, will be displayed.
b. regsvr32
Example: regsvr32 COMDLG32.OCX
Upon running this command, a dialogue box, as shown below, will be displayed.
This step must be done for the .OCX Dependency raising an exception.
5. After all dependencies have been resolved, you need to run your VEDA-FE or VEDA-BE application as Administrator. To do so, right click over VEDA_FE.exe or VEDA_BE.exe (located in VEDA\ VEDA_FE or VEDA\ VEDA_BE folder, respectively) and select 'Run as Administrator'.
Once you have run the specific VEDA application as Administrator and all dependencies are registered successfully, you can run it for any user by simply double clicking the .exe or shortcut on Desktop.
Utsav Jha
VEDA Support