ActiveX component that behaves in 2000 blows up in XP 1

[sparkyputerguy]

Hi there-
We've been looking all over for a solution and haven't found one yet... Thanks in advance for any advice you might have.

We design database applications and use a Greentree ActiveX control (gtnum32.ocx) for certain modules. If one of these modules/applications is open and CTRL-ALT-DEL is pressed (to lock the computer, open task manager, etc.), the application generates a fault and closes.

This is happening on 2003 server as well.

On 2000 (Pro/Server), this was not an issue.

It seems that we have the latest version of this OCX file and short of removing it (and replacing with another solution), we're running out of options.

Any ideas?

 

[sparkyputerguy]

Forgot to mention- we're running XP Pro SP2 and 2003 Server SP1 with current patches as of July of 2005.

 

[linney]

Can you run the program that uses gtnum32.ocx in a different Compatibility Mode, for example Windows 2000?

Have you tried the "GreenTree DataMask ActiveX Controls" Support Site if it exists for any help or perhaps a later or maybe uncorrupted version of the ocx?

Whereas it sounds like any problem is being caused by the ocx file, I suppose there is a slight chance some other piece of software may be causing the problem.

310353 - How to Perform a Clean Boot in Windows XP

http://support.microsoft.com/default.aspx?scid=kb;en-us;310353&FR=1&PA=1&SD=HSCH

316434 - HOW TO: Perform Advanced Clean-Boot Troubleshooting in Windows XP

http://support.microsoft.com/default.aspx?scid=kb;en-us;316434&FR=1&PA=1&SD=HSCH

310560 - How to Troubleshoot By Using the Msconfig Utility in Windows XP

http://support.microsoft.com/default.aspx?scid=kb;en-us;310560&FR=1&PA=1&SD=HSCH

Try Safe Mode (Do you have this problem in Safe Mode?).

Run the System File Checker program from the Run Box by typing.....Sfc /Scannow in it and have your XP CD handy.

 

[sparkyputerguy]

Thanks for the ideas! I'll let you know how it goes in the morning.

I have sent two messages to Greentree support and haven't heard anything yet. They don't seem to have many newer products than what we already have (purchased in '99 or so) so I'm thinking they're not going to be much help.

 

[sparkyputerguy]

Well, still no luck. I tried calling Greentree and their numbers have been disconnected.

On XP, I tried the following things:
1. Running apps in Safe Mode
2. Change the application compatibility ('.exe app that uses gtnum32.ocx' -> Windows 2000 Mode) Can't configure the OCX file for compatibility.
3. Install VB6 runtime files from MS (our app was written in VB6)
4. Disable Data Execution Prevention (DEP), which is a new feature of XP SP2
5. Uninstall antivirus software

I'm restoring a backup image of XP SP1 so I'll let everyone know how that goes.

 

[BadFrog]

Interesting thread. Is that a 16 bit app by any chance? If so try setting your campatibility mode to win95 or win98.

Do any of the modules work? Have they ever worked with that ocx? I'm guessing the problem started after you upgraded the server from 2000 to 2003. Is that accurate?

"Once you can accept the universe as matter expanding into nothing that is something, wearing stripes with plaid comes easy"
Albert Einstein

 

[sparkyputerguy]

Hi BadFrog-

All the apps should be 32bit. The OCX that's blowing up is named GTNUM32.OCX so I'm making a pretty confident assumption there.

We are having the problem on new installs of XP (haven't really done any 2000->XP upgrades) and both new 2003 installs and 2000->2003 upgrades.

The funny thing is that everything works within the normal environment (even the OCX) until CTR-ALT-DEL is pressed or a locking screensaver kicks in.

I've been reading into what happens during that and it looks like the winlogon.exe process kicks off and starts talking to the GINA. I tried running a debug version of winlogon that logs all its activities but it ended up BSODing both machines I tried it on. D'oh!

 

[BadFrog]

I tried calling Greentree and their numbers have been disconnected.

Based on that I would start looking for another solution. Perhaps thats why the numbers are disconnected. Bummer.


"Once you can accept the universe as matter expanding into nothing that is something, wearing stripes with plaid comes easy"
Albert Einstein

 

[sparkyputerguy]

Yeah, pretty much! It'll be up to our developers to figure out how to proceed. I've been working the OS/environment angle hoping to make their lives easier.

I just finished testing on XP SP1 and I get the same results so it doesn't seem to be a result of any new "features".

Here's a snippet from the Dr. Watson log if anyone is interested. Thanks to everyone for your help!

0f9688f0 55 push ebp
0f9688f1 51 push ecx
0f9688f2 50 push eax
0f9688f3 ff153440980f call dword ptr [gtnum32+0x24034 (0f984034)]
0f9688f9 50 push eax
0f9688fa e8810c0100 call gtnum32!DllUnregisterServer+0xfca0 (0f979580)
0f9688ff 8bd8 mov ebx,eax
0f968901 8b7e40 mov edi,[esi+0x40]
0f968904 3bdf cmp ebx,edi
0f968906 7420 jz gtnum32+0x8928 (0f968928)
FAULT ->0f968908 8b4320 mov eax,[ebx+0x20] ds:0023:00000020=????????
0f96890b 50 push eax
0f96890c ff15d83f980f call dword ptr [gtnum32+0x23fd8 (0f983fd8)]
0f968912 50 push eax
0f968913 e8680c0100 call gtnum32!DllUnregisterServer+0xfca0 (0f979580)
0f968918 3bc7 cmp eax,edi
0f96891a 740c jz gtnum32+0x8928 (0f968928)
0f96891c 33c0 xor eax,eax
0f96891e 5d pop ebp
0f96891f 5f pop edi
0f968920 5e pop esi

 

[sparkyputerguy]

New development!

I removed the workstation from the domain, and re-enabled fast user switching. Got some different behavior:

If I was logged in as a user and pressed CTRL-ALT-DEL, task manager comes up and the application stays intact.

If I switched users (leaving the original login), the application blew up when making the swap.

In researching winlogon, it seems to have its own 'Desktop environment'. So it seems that switching desktops (either from logged-in-user to winlogon in a domain environment or from logged-in-user to new-user in fast user switching) will blow this up. It probably has to do with the applications not being user-switch aware. MS has an interesting article on this:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwxp/html/winxpfus.asp