Windows 7 and MSCOMCTL.OCX problem

[Feng]

I moved my VB6 sp5 to Windows 7 installed system. Working with the empty project with the MSCOMCTL object in the Components. When going to get the MSCOMCTL within the Object browser, VB6 environment got crashed. I am not sure about the specific cause for this . The same things going on with the comctl32 element .some different elements looks to be fine . It did not happen in Windows XP or Windows Vista.

MSCOMCTL.OCX is 6.01.9786.

comctl32.ocx is 6.00.8105

Thanks for your help.

[Sniperz]

According to the Event log recorded, the problem occurred due to the VB6.0, to strict diagnostic and troubleshoot such type of problem , it may need gathering the crash dump associated files and completing the processing of some source coding, I would suggest you to go for the contacting with the Microsoft Visual Studio for particular solutions for this case.

[phones]

Have you committed the installation of Windows 7 32bit version or Windows 7 64bit version?

1. Just move to the Event Viewer and click on the Applications and find out if any error message is logged.

2. This looks that the MSCOMCTL.OCX is not properly registered or that it is not supported with your installed Windows. Please launch the Command Prompt in the background and run it as the Administrator and then after type out the below suggested command:

Regsvr32 MSCOMCT2.OCX

If you are working with the Window7 64bit,just type out the following :

Regsvr32 c:\windows\SysWOW64\MSCOMCT2.OCX

If the problem still going on , let’s download a new MSCOMCTL.OCX and get register the same once again.

3. Go through the same way for comctl32.ocx also.

[Feng]

Thanks for your suggestion but this is bad luck for me and it was not much helpful for me . I have installed the Windows 7 32bit on my system .I have post the App Event log that is added on each crash.

OLEAUT32.dll on Win7 computer is 6.1.7600.16385 7/13/2009 9:16

OLEAUT32.dll on working Vista computer is 6.0.6002.18005 4/11/2009 2:28

The issue is only with the object browser, otherwise the elements are going fine .Please take a look at the event log...

Log Name: Application
Source: Application Error
Date: 6/25/2010 2:02:55 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Lenkost7
Description:
Faulting application name: vb6.exe, version: 6.0.89.88, time stamp: 0x39c140a3
Faulting module name: OLEAUT32.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdaca
Exception code: 0xc0000005
Fault offset: 0x00021e1a
Faulting process id: 0x10fc
Faulting application start time: 0x01cb142c0714e3c3
Faulting application path: C:\Program Files\Microsoft Visual Studio\VB98\vb6.exe
Faulting module path: C:\Windows\system32\OLEAUT32.dll
Report Id: 4b858c06-801f-11df-8874-0015af079c03
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-06-25T06:02:55.000000000Z" />
<EventRecordID>6773</EventRecordID>
<Channel>Application</Channel>
<Computer>Lenkost7</Computer>
<Security />
</System>
<EventData>
<Data>vb6.exe</Data>
<Data>6.0.89.88</Data>
<Data>39c140a3</Data>
<Data>OLEAUT32.dll</Data>
<Data>6.1.7600.16385</Data>
<Data>4a5bdaca</Data>
<Data>c0000005</Data>
<Data>00021e1a</Data>
<Data>10fc</Data>
<Data>01cb142c0714e3c3</Data>
<Data>C:\Program Files\Microsoft Visual Studio\VB98\vb6.exe</Data>
<Data>C:\Windows\system32\OLEAUT32.dll</Data>
<Data>4b858c06-801f-11df-8874-0015af079c03</Data>
</EventData>
</Event>

[Sheravat]

We work with the calendar control as another section of so many MS Access 2007 database. It is not an issue with the Windows XP, but we are just migrating to 64 bit Windows 7 and are running with the difficulty in the registration of this OCX control within this OS. We have tried to go with as the administrator account, both from a shortcut and also with the command prompt. We have also used logging within the system as a local administration - none of these seems feasible in this case. The error when failing is 0x8002801C.

[Am_Wamika]

We have had the similar issue and have currently worked out upon the procedure to do this. You have to copy the MSCOMCT2.OCX file into the following location suggested as c:\windows\sysWOW64 not c:\windows\system32. You then able to register this by executing from the command prompt or go through the start menu regsvr32 c:\windows\sysWOW64\mscomct2.ocx and it must register although be sure that you execute the regsvr32 with admin privileges.

Please do one thing here, if you are going to register the ocx from C: windows\system32 with the help of regsvr32 you will find the following error:

The module “c:\windows\system32\mscomct2ocx” failed to load. Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependent .DLL files. The specified module could not be found.