PRB: Component Not Registered Error When Attempting to Run a VB Application (289493)
The information in this article applies to:
- Microsoft Visual Basic Enterprise Edition for Windows 5.0, when used with:
- the operating system: Microsoft Windows NT 4.0
- the operating system: Microsoft Windows 2000
- Microsoft Visual Basic Enterprise Edition for Windows 6.0, when used with:
- the operating system: Microsoft Windows NT 4.0
- the operating system: Microsoft Windows 2000
- Microsoft Visual Basic Professional Edition for Windows 5.0, when used with:
- the operating system: Microsoft Windows NT 4.0
- the operating system: Microsoft Windows 2000
- Microsoft Visual Basic Professional Edition for Windows 6.0, when used with:
- the operating system: Microsoft Windows NT 4.0
- the operating system: Microsoft Windows 2000
This article was previously published under Q289493 SYMPTOMS
When you attempt to run a Visual Basic (VB) application on a computer that is running Microsoft Windows NT 4.0 or Microsoft Windows 2000, and you are not logged in as an Administrator or you do not have Administrator rights, you may receive the following error message
Component tabctl32.ocx or one of its dependencies not correctly registered: a file is missing or invalid.
where tabctl32.ocx is the name of the ActiveX control that is experiencing the problem. The .ocx file for the control is physically present on the computer. Any attempt to manually register this control by using Regsvr32.exe fails with the 0x00000005 (or "Access is Denied") return error code.
Users who are logged in as an Administrator or who have Administrator rights do not receive an error message.
CAUSE
The interactive user does not have access permission to the ActiveX control that is listed in the error dialog box. This problem usually occurs on computers that are formatted with Microsoft Windows NT File System (NTFS). NTFS has a built-in security system that allows you to grant various permissions to folders and to individual files. These permissions protect files and folders locally and remotely.
RESOLUTION
To resolve this problem, grant the user the necessary permissions to the control.
STATUS
This behavior is by design.
Modification Type: | Major | Last Reviewed: | 5/13/2003 |
---|
Keywords: | kbCtrl kbprb kbSecurity KB289493 |
---|
|