Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.basic.visual.misc > #2155 > unrolled thread

GPF caused by Coolbar control

Back to article view | Back to comp.lang.basic.visual.misc

Contents

  GPF caused by Coolbar control "Paulo" <nospam.vbstudent@syscolor.net> - 2014-10-12 17:25 +0100
    Re: GPF caused by Coolbar control Deanna Earley <dee.earley@icode.co.uk> - 2014-10-13 08:50 +0100
      Re: GPF caused by Coolbar control "Paulo" <nospam.vbstudent@syscolor.net> - 2014-10-13 17:51 +0100
        Re: GPF caused by Coolbar control Deanna Earley <dee.earley@icode.co.uk> - 2014-10-14 11:37 +0100
    Re: GPF caused by Coolbar control "Farnsworth" <nospam@nospam.com> - 2014-10-13 07:54 -0400
      Re: GPF caused by Coolbar control "Paulo" <nospam.vbstudent@syscolor.net> - 2014-10-13 17:30 +0100
    Re: GPF caused by Coolbar control "Farnsworth" <nospam@nospam.com> - 2014-10-13 08:04 -0400
      Re: GPF caused by Coolbar control "Paulo" <nospam.vbstudent@syscolor.net> - 2014-10-13 18:42 +0100
        Re: GPF caused by Coolbar control "Farnsworth" <nospam@nospam.com> - 2014-10-13 14:47 -0400
          Re: GPF caused by Coolbar control "Paulo" <nospam.vbstudent@syscolor.net> - 2014-10-14 03:34 +0100
    Re: GPF caused by Coolbar control - FOUND WORKAROUND "Paulo" <nospam.vbstudent@syscolor.net> - 2014-10-14 04:15 +0100
      Re: GPF caused by Coolbar control - FOUND WORKAROUND Deanna Earley <dee.earley@icode.co.uk> - 2014-10-14 11:42 +0100
        Re: GPF caused by Coolbar control - FOUND WORKAROUND "Paulo" <nospam.vbstudent@syscolor.net> - 2014-10-19 17:17 +0100

#2155 — GPF caused by Coolbar control

Hi, all

I maintain an application writen in VB6 that uses CoolBar control version 
6.0 (SP5). Some weeks ago a customer told me that the application was 
generating an error in Windows XP (SP3) when closing it, althoug this error 
didn't prevent from running it and didn't cause loss of data.

The error message is:
"Invoice Manager has encountered a problem and needs to close. We are sorry 
by the inconvenience."

The error report contains the following error signature:
  AppName: ivcman.exe
  AppVer: 2.1.0.117
  ModName: kernel32.dll
  ModVer: 5.1.2600.6532
  Offset: 00012fd3

After some tests I found that the error is caused by the CoolBar control. 
After some search in the web I found also that this is an old issue reported 
by Microsoft in the KB BUG report:
Title: Wrapped CoolBar Control May GPF Client EXE Program
URL: ftp://ftp.microsoft.com/misc1/DEVELOPR/VB/KB/Q189/9/14.TXT

The resolution proposed in this BUG report (Clear the Bands object) does not 
work. This is the only application where I used the CoolBar control but it 
is important for me to maintain it's VB6 interface.

Does anybody knows if any solution was ever found?

TIA
Paulo 

[toc] | [next] | [standalone]

#2156

On 12/10/2014 17:25, Paulo wrote:
> Hi, all
>
> I maintain an application writen in VB6 that uses CoolBar control version
> 6.0 (SP5). Some weeks ago a customer told me that the application was
> generating an error in Windows XP (SP3) when closing it, althoug this error
> didn't prevent from running it and didn't cause loss of data.
>
> The error message is:
> "Invoice Manager has encountered a problem and needs to close. We are sorry
> by the inconvenience."
>
> The error report contains the following error signature:
>    AppName: ivcman.exe
>    AppVer: 2.1.0.117
>    ModName: kernel32.dll
>    ModVer: 5.1.2600.6532
>    Offset: 00012fd3
>
> After some tests I found that the error is caused by the CoolBar control.
> After some search in the web I found also that this is an old issue reported
> by Microsoft in the KB BUG report:
> Title: Wrapped CoolBar Control May GPF Client EXE Program
> URL: ftp://ftp.microsoft.com/misc1/DEVELOPR/VB/KB/Q189/9/14.TXT
>
> The resolution proposed in this BUG report (Clear the Bands object) does not
> work. This is the only application where I used the CoolBar control but it
> is important for me to maintain it's VB6 interface.

That KB article also only applied to Win9x based systems. NT based (of 
which XP is one) are not affected.
http://c-bit.org/kb/189914/EN-US/
http://smallbusiness.support.microsoft.com/de-ch/Kb/189914?lcid=1033
(Affecting only 9x is probably why MS have taken the original offline)

-- 
Deanna Earley (dee.earley@icode.co.uk)
iCatcher Development Team
http://www.icode.co.uk/icatcher/

iCode Systems

(Replies direct to my email address will be printed, shredded then fed 
to the rats. Please reply to the group.)

[toc] | [prev] | [next] | [standalone]

#2160

"Deanna Earley" <dee.earley@icode.co.uk> wrote in message 
news:m1g08g$5k6$1@speranza.aioe.org...
> On 12/10/2014 17:25, Paulo wrote:
>> Hi, all
>>
>> I maintain an application writen in VB6 that uses CoolBar control version
>> 6.0 (SP5). Some weeks ago a customer told me that the application was
>> generating an error in Windows XP (SP3) when closing it, althoug this 
>> error
>> didn't prevent from running it and didn't cause loss of data.
>>
>> The error message is:
>> "Invoice Manager has encountered a problem and needs to close. We are 
>> sorry
>> by the inconvenience."
>>
>> The error report contains the following error signature:
>>    AppName: ivcman.exe
>>    AppVer: 2.1.0.117
>>    ModName: kernel32.dll
>>    ModVer: 5.1.2600.6532
>>    Offset: 00012fd3
>>
>> After some tests I found that the error is caused by the CoolBar control.
>> After some search in the web I found also that this is an old issue 
>> reported
>> by Microsoft in the KB BUG report:
>> Title: Wrapped CoolBar Control May GPF Client EXE Program
>> URL: ftp://ftp.microsoft.com/misc1/DEVELOPR/VB/KB/Q189/9/14.TXT
>>
>> The resolution proposed in this BUG report (Clear the Bands object) does 
>> not
>> work. This is the only application where I used the CoolBar control but 
>> it
>> is important for me to maintain it's VB6 interface.
>
> That KB article also only applied to Win9x based systems. NT based (of 
> which XP is one) are not affected.
> http://c-bit.org/kb/189914/EN-US/
> http://smallbusiness.support.microsoft.com/de-ch/Kb/189914?lcid=1033
> (Affecting only 9x is probably why MS have taken the original offline)
>
> -- 
> Deanna Earley (dee.earley@icode.co.uk)
> iCatcher Development Team
> http://www.icode.co.uk/icatcher/
>
> iCode Systems
>
> (Replies direct to my email address will be printed, shredded then fed to 
> the rats. Please reply to the group.)

This article:
 http://smallbusiness.support.microsoft.com/de-ch/Kb/189914?lcid=1033
says: "... The EXE will not give the above error running on NT 4.0 or 
Windows 2000..."
Windows XP (NT 5.1.2600) is not referred specificaly.

It is amazing that I didn´t notice this behavior before. This version of the 
application was developed in 2003 in Windows 2000. Now, in my Windows XP SP3 
the error occurs also.

[toc] | [prev] | [next] | [standalone]

#2165

On 13/10/2014 17:51, Paulo wrote:
> "Deanna Earley" <dee.earley@icode.co.uk> wrote in message
> news:m1g08g$5k6$1@speranza.aioe.org...
>> On 12/10/2014 17:25, Paulo wrote:
>>> After some search in the web I found also that this is an old
>>> issue reported by Microsoft in the KB BUG report:
>>> Title: Wrapped CoolBar Control May GPF Client EXE Program
>>> URL: ftp://ftp.microsoft.com/misc1/DEVELOPR/VB/KB/Q189/9/14.TXT
>>>
>>> The resolution proposed in this BUG report (Clear the Bands
>>> object) does not work. This is the only application where I used
>>> the CoolBar control but it is important for me to maintain it's
>>> VB6 interface.
>>
>> That KB article also only applied to Win9x based systems. NT based (of
>> which XP is one) are not affected.
>> http://c-bit.org/kb/189914/EN-US/
>> http://smallbusiness.support.microsoft.com/de-ch/Kb/189914?lcid=1033
>> (Affecting only 9x is probably why MS have taken the original offline)
>
> This article:
>   http://smallbusiness.support.microsoft.com/de-ch/Kb/189914?lcid=1033
> says: "... The EXE will not give the above error running on NT 4.0 or
> Windows 2000..."
> Windows XP (NT 5.1.2600) is not referred specificaly.

No, as it predates Windows XP. The "not effecting NT4/2000" implies that 
all NT based systems are equally unaffected, and that specific bug only 
occurred on Windows 9x which is thankfully long gone.

This also ties up with why the article is no longer available (in the 
normal location) as all affected systems are long out of support.

-- 
Deanna Earley (dee.earley@icode.co.uk)
iCatcher Development Team
http://www.icode.co.uk/icatcher/

iCode Systems

(Replies direct to my email address will be printed, shredded then fed 
to the rats. Please reply to the group.)

[toc] | [prev] | [next] | [standalone]

#2157

Are you doing any subclassing?

[toc] | [prev] | [next] | [standalone]

#2159

"Farnsworth" <nospam@nospam.com> wrote in message 
news:m1gei4$cug$1@speranza.aioe.org...
> Are you doing any subclassing?

Yes, but in another form, with no problem. 

[toc] | [prev] | [next] | [standalone]

#2158

Try setting the Container property for all controls on the Coolbar to the 
form before it's closed. Example:

Set Command1.Container = Form1
Set Picture1.Container = Form1
...

[toc] | [prev] | [next] | [standalone]

#2161

"Farnsworth" <nospam@nospam.com> wrote in message 
news:m1gf4t$eh3$1@speranza.aioe.org...
> Try setting the Container property for all controls on the Coolbar to the 
> form before it's closed. Example:
>
> Set Command1.Container = Form1
> Set Picture1.Container = Form1
> ...

Thanks, I will try this. 

[toc] | [prev] | [next] | [standalone]

#2162

"Paulo" <nospam.vbstudent@syscolor.net> wrote in message 
news:m1h2ud$no1$1@dont-email.me...
> "Farnsworth" <nospam@nospam.com> wrote in message 
> news:m1gf4t$eh3$1@speranza.aioe.org...
>> Try setting the Container property for all controls on the Coolbar to the 
>> form before it's closed. Example:
>>
>> Set Command1.Container = Form1
>> Set Picture1.Container = Form1
>> ...
>
> Thanks, I will try this.

This related article describes a problem that I was able to duplicate on 
XP+SP2(You have to add Err.Raise 5 line and click on the band separator to 
see the crash):

http://smallbusiness.support.microsoft.com/en-us/kb/189632

I was not able to make it crash based on the article that you originally 
gave(Q189914).

[toc] | [prev] | [next] | [standalone]

#2163

"Farnsworth" <nospam@nospam.com> wrote in message 
news:m1h6na$2vh$1@speranza.aioe.org...
> "Paulo" <nospam.vbstudent@syscolor.net> wrote in message 
> news:m1h2ud$no1$1@dont-email.me...
>> "Farnsworth" <nospam@nospam.com> wrote in message 
>> news:m1gf4t$eh3$1@speranza.aioe.org...
>>> Try setting the Container property for all controls on the Coolbar to 
>>> the form before it's closed. Example:
>>>
>>> Set Command1.Container = Form1
>>> Set Picture1.Container = Form1
>>> ...
>>
>> Thanks, I will try this.
>
> This related article describes a problem that I was able to duplicate on 
> XP+SP2(You have to add Err.Raise 5 line and click on the band separator to 
> see the crash):
>
> http://smallbusiness.support.microsoft.com/en-us/kb/189632

Yes, the GPF message is the same.

> I was not able to make it crash based on the article that you originally 
> gave(Q189914).

I think that I found the origin. The QueryUnload event of the form 
containing the CoolBar contral calls a sub that contains an End statement. 
By removing the End statement the GPF is not raised.

[toc] | [prev] | [next] | [standalone]

#2164 — Re: GPF caused by Coolbar control - FOUND WORKAROUND

Well, I knew that the use of the End statement is not advisable and that 
should be used with caution.

If the user confirms to close the application the QueryUnload of my form 
calls a Sub that contains an End statement. The GPF raised in my application 
is caused when this End statement is called.

I found that the GPF is not raised with anyone of this two workarounds :
1. Remove the End statement.
2. The Sub called by the QueryUnload of my form loads an invisible form that 
contains the End statement in the Load event.

I have chosen to deliver an update with the second "solution" that keeps the 
End statement.

Paulo 

[toc] | [prev] | [next] | [standalone]

#2166 — Re: GPF caused by Coolbar control - FOUND WORKAROUND

On 14/10/2014 04:15, Paulo wrote:
> Well, I knew that the use of the End statement is not advisable and that
> should be used with caution.
>
> If the user confirms to close the application the QueryUnload of my form
> calls a Sub that contains an End statement. The GPF raised in my application
> is caused when this End statement is called.
>
> I found that the GPF is not raised with anyone of this two workarounds :
> 1. Remove the End statement.
> 2. The Sub called by the QueryUnload of my form loads an invisible form that
> contains the End statement in the Load event.
>
> I have chosen to deliver an update with the second "solution" that keeps the
> End statement.

Why not just let it exit as normal?
As you said, End is well known to cause many problems, in another form 
or not.

-- 
Deanna Earley (dee.earley@icode.co.uk)
iCatcher Development Team
http://www.icode.co.uk/icatcher/

iCode Systems

(Replies direct to my email address will be printed, shredded then fed 
to the rats. Please reply to the group.)

[toc] | [prev] | [next] | [standalone]

#2167 — Re: GPF caused by Coolbar control - FOUND WORKAROUND

I found why I put and End statement. The application needs to close 
completely because it can be run only one instance at time (Windows session) 
due to the remote database design. So, when run the app twice in the same 
Windows session, the app abborted in the second time. At that time, as I 
didn't found why it didn't close, I found that solution.

Thank you for your support, Deanna.

> Why not just let it exit as normal?
> As you said, End is well known to cause many problems, in another form or 
> not.
>
> -- 
> Deanna Earley (dee.earley@icode.co.uk)
> iCatcher Development Team
> http://www.icode.co.uk/icatcher/
>
> iCode Systems
>
> (Replies direct to my email address will be printed, shredded then fed to 
> the rats. Please reply to the group.) 

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.basic.visual.misc

csiph-web