Microsoft KB Archive/289493

= PRB: Component Not Registered Error When Attempting to Run a VB Application =

Article ID: 289493

Article Last Modified on 5/13/2003

-

APPLIES TO

 Microsoft Visual Basic 5.0 Enterprise Edition, when used with:  Microsoft Windows NT 4.0

 Microsoft Windows 2000 Standard Edition  Microsoft Visual Basic 6.0 Enterprise Edition, when used with:  Microsoft Windows NT 4.0

 Microsoft Windows 2000 Standard Edition</li></ul> </li> Microsoft Visual Basic 5.0 Professional Edition, when used with:  Microsoft Windows NT 4.0</li></ul>

 Microsoft Windows 2000 Standard Edition</li></ul> </li> Microsoft Visual Basic 6.0 Professional Edition, when used with:  Microsoft Windows NT 4.0</li></ul>

 Microsoft Windows 2000 Standard Edition</li></ul> </li></ul>

-

<div class="notice_section">

This article was previously published under Q289493

<div class="symptoms_section">

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 &quot;Access is Denied&quot;) return error code.

Users who are logged in as an Administrator or who have Administrator rights do not receive an error message.

<div class="cause_section">

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.

<div class="resolution_section">

RESOLUTION
To resolve this problem, grant the user the necessary permissions to the control.

<div class="status_section">

STATUS
This behavior is by design.

<div class="moreinformation_section">

MORE INFORMATION
To change file permissions, follow these steps:
 * 1) Log on to the system as an Administrator or as a user with Administrator rights.
 * 2) Search for the .ocx file that is listed in the error message. It is usually located in the System32 folder.
 * 3) Right-click the file and click Properties.
 * 4) In the Properties dialog box for this control, click the Security tab.
 * 5) If you are using Windows NT 4.0, on the Security tab, click Permissions. The File Permissions dialog box appears. Make sure that the Type of access is at least set to Read for the interactive user.

If you are using Windows 2000, on the Security tab, select a user or group from the list, select the permissions that you want to grant (which must include at least Read), and then click either OK or Apply.

Keywords: kbctrl kbprb kbsecurity KB289493

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.