Tabctl32 causing problem in XP SP3

[putta]

Dear All,

I have a application which uses Tabbed Dialogue panes. I used the ocx Tabctl32 of VB SP6. The application works properly in Windows XP SP2. With XP SP3 it just wouldn't start. The error “Failed to load control ‘SSTab’ from tabctl32.ocx. Your version may be outdated. Make sure you are using the version of the control that was provided with your application.” comes when the application is installed and opened in the machines running XP SP3. I have used inno setup to build the setup. The ocx is getting registered properly. The application works perfectly in the windows 2000 and XP SP2. I have tried out with lots of versions of Tabctl32.ocx. Nothing seems to solve this problem. Has anyone come across this problem? Please help if possible.. :-)

Regards,
Putta

[RobDog888]

Thread Moved

[dilettante]

Works fine here on both Vista SP1 and XP SP3. Perhaps you are deploying an ancient version of the OCX? Version 6.1.97.82 here.

I tested this using SxS deployment to avoid disturbing anything already in place on those machines.

[putta]

How do I find the version of tabctl32.ocx I am using? I am using the ocx which is present in my windows\system32 directory. Please help...

[dilettante]

Check the file's Properties. The Properties dialog should have a tab with file details including the version.

[putta]

I tried with the tabctl32.OCX of "6.1.97.82" version. No luck . The OS which is causing problem is "Windows XP Professional version 2002" with SP3.

No clue why this problem is happening. Please help me coz my application wont work where it is really supposed to work. Else I have remove the tab component completely and modify the program. Please help...

Regards,
Putta

[dilettante]

I should have recognized this. It would help if you mentioned you were getting runtime error 339. Another description for this error is:

"Component 'item' or one of its dependencies not correctly registered: a file is missing or invalid."

Most likely you have a bad setup package.

The target system may also have improperly registered this component to some other filesystem location but the file is no longer there. The latter can happen if someone has previously done something like copying an EXE with associated OCX files in the same folder and then run the EXE there. This happens a lot when people follow erroneous advice about using .local files.

If possible clean up the registry on the machine where you see this error. Then try reinstalling the application. An incorrect component registration may be keeping your setup package from installing the OCX properly.

[putta]

Thanks for the reply. I am not getting the error "Component 'item' or one of its dependencies not correctly registered: a file is missing or invalid." The ocx is getting registered properly. I have built the setup using innosetup and this is the line which pumps in the tabctl32.ocx in the machine where it is being delivered.

[Files]
Source: "vbfiles\tabctl32.ocx"; DestDir: {sys}; Flags: restartreplace  sharedfile regserver

I have noticed one more thing. I followed these steps in a hope to isolate the problem.

• Installed new windows XP professional
• installed SP2
• Installed SP3
• Installed the application -- "application works perfectly"
• Uninstalled the application
• Did a complete live update of microsoft XP
• Re-installed my application -- "Application does not work"

Looks like XP SP3 after update does not support Tabctl32.ocx. Any idea why? I have completely become clueless ...

-Regards,
Putta

[dilettante]

What is the error number of the exception you are seeing?

What do you mean by "live update?"

I just set up an XP SP3 VM and brought it up to date using Windows Update. A small sample program using Tabctl32.ocx works fine there.