Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Experiencing frequent crashing issues since upgrading to PB12. Need help.

6 posts in General Discussion Last posting was on 2013-03-05 12:39:01.0Z
Chris Polson Posted on 2013-03-01 17:58:06.0Z
Sender: 6ec0.5130e501.1804289383@sybase.com
From: Chris Polson
Newsgroups: sybase.public.powerbuilder.general
Subject: Experiencing frequent crashing issues since upgrading to PB12. Need help.
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <5130ec2e.724e.1681692777@sybase.com>
NNTP-Posting-Host: 172.20.134.41
X-Original-NNTP-Posting-Host: 172.20.134.41
Date: 1 Mar 2013 09:58:06 -0800
X-Trace: forums-1-dub 1362160686 172.20.134.41 (1 Mar 2013 09:58:06 -0800)
X-Original-Trace: 1 Mar 2013 09:58:06 -0800, 172.20.134.41
Lines: 47
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.general:249770
Article PK: 1308033

Hello,

Since building our application with PB12 EBF 6639, (our last
was built with PB11.2 Build 8869.

During this upgrade of our application we did two things. We
upgraded our clients to SQL Server 2008. Many had been on
SQL Server 2005, and on Sybase. The other thing we did was
upgrade PB to 12 EBF 6639.

Our clients are seeing our application 'randomly crash' in
dozens of areas in the application.

The typical one we are seeing is in

module: PBVM120.dll, exception code 0xc0000005 fault offset:
0x000c0cbf

We have also seen module: pbdwe120.dll, exception code
0xc0000005 fault offset: 0x00092015 and

module: pbshr120.dll, exception code 0xc0000005, fault
offset: 000f2040

But mostly we are seeing the first in PBVM120.dll.

Most of the crashing issues are not recreatable for us. Our
clients seems to run into them randomly. There was one given
to us by clients that was 100% recreatable. It would crash
for the client when closing a window of ours. We seemed to
be able to solve this one by calling Yield() when the user
would close. However, replacing the Yield() with a
GarbageCollect() also worked. Replacing it with a MessageBox
also worked. Whatever seemed to give the code 'time to catch
up' so to speak... seemed to work for this one specific
area. No clue why it worked, but these 3 'solutions' did.

Are there any reports of this out there anywhere? I called
Sybase to open a ticket, but they no longer do the $400
ticket thing where you can open a ticket.

Our application was running fine at 100's of client sites
when built in PB11.2 and running SS2005 or Sybase. Now with
PB12 6639 and SS2008, the application is crashing frequently
and in many areas for the 30+ clients we have upgraded.

Is there anything on this, or anyone experiencing this?


Scott Morris Posted on 2013-03-01 18:31:13.0Z
Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes
Newsgroups: sybase.public.powerbuilder.general
Subject: Re: Experiencing frequent crashing issues since upgrading to PB12. Need help.
References: <5130ec2e.724e.1681692777@sybase.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: "Scott Morris" <bogus@abc.def>
Message-ID: <op.ws95qazfq59cbq@scott-win7.divinv.net>
User-Agent: Opera Mail/11.51 (Win32)
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Date: 1 Mar 2013 10:31:13 -0800
X-Trace: forums-1-dub 1362162673 172.20.134.152 (1 Mar 2013 10:31:13 -0800)
X-Original-Trace: 1 Mar 2013 10:31:13 -0800, vip152.sybase.com
Lines: 78
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.general:249771
Article PK: 1308037


On Fri, 01 Mar 2013 12:58:06 -0500, Chris <Polson> wrote:

> Hello,
>
> Since building our application with PB12 EBF 6639, (our last
> was built with PB11.2 Build 8869.
>
> During this upgrade of our application we did two things. We
> upgraded our clients to SQL Server 2008. Many had been on
> SQL Server 2005, and on Sybase. The other thing we did was
> upgrade PB to 12 EBF 6639.
>
> Our clients are seeing our application 'randomly crash' in
> dozens of areas in the application.
>
> The typical one we are seeing is in
>
> module: PBVM120.dll, exception code 0xc0000005 fault offset:
> 0x000c0cbf
>
> We have also seen module: pbdwe120.dll, exception code
> 0xc0000005 fault offset: 0x00092015 and
>
> module: pbshr120.dll, exception code 0xc0000005, fault
> offset: 000f2040
>
> But mostly we are seeing the first in PBVM120.dll.
>
> Most of the crashing issues are not recreatable for us. Our
> clients seems to run into them randomly. There was one given
> to us by clients that was 100% recreatable. It would crash
> for the client when closing a window of ours. We seemed to
> be able to solve this one by calling Yield() when the user
> would close. However, replacing the Yield() with a
> GarbageCollect() also worked. Replacing it with a MessageBox
> also worked. Whatever seemed to give the code 'time to catch
> up' so to speak... seemed to work for this one specific
> area. No clue why it worked, but these 3 'solutions' did.
>
> Are there any reports of this out there anywhere? I called
> Sybase to open a ticket, but they no longer do the $400
> ticket thing where you can open a ticket.
>
> Our application was running fine at 100's of client sites
> when built in PB11.2 and running SS2005 or Sybase. Now with
> PB12 6639 and SS2008, the application is crashing frequently
> and in many areas for the 30+ clients we have upgraded.
>
> Is there anything on this, or anyone experiencing this?

First - there are two different versions of PB and they create multiple
types of applications. Be specific. The next point to make is that you
should use an EBF only if you really need it. It is safer to stay on an
actual MR. FWIW, We upgraded a classic app from 11.2 to 12.1 and had no
problems. Other factors caused us to upgrade to 12.5.1 (classic still)
without issues.

Outside of that, random crashing is often a sign of a corrupted
installation. Typically this means that there are multiple versions of PB
DLLs on the system - mixing versions is known to cause this. When you say
you cannot repeat these problems, are you running the EXE on a machine
that does **NOT** have the IDE installed? If not, then you should get in
the habit of testing in this fashion.

If one workaround is to call yield or messagebox, that is an indication of
an assumption somewhere in your application that events occur in a
particular order. If your code posts events, that would be one place to
look. In my own code, I've never called garbagecollect anywhere, ever -
in classic-style applications and never had any problems. garbagecollect
should call destructors - perhaps in an order you do not expect? The
release bulletin documents one such behavior change, though you should
have encountered it during development if it applies.

One last suggestion - make sure that your build process (and all of the
developers) are using the same version of PB and that you build/deliver
the correct support files (assuming you use the runtime packager) to the
client. Of course, your testing procedure should use the same installation
process that your customers use.


Chris Polson Posted on 2013-03-01 19:16:10.0Z
Sender: 7766.5130f89f.846930886@sybase.com
From: Chris Polson
Newsgroups: sybase.public.powerbuilder.general
Subject: Re: Experiencing frequent crashing issues since upgrading to PB12. Need help.
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <5130fe7a.7ae9.1681692777@sybase.com>
References: <op.ws95qazfq59cbq@scott-win7.divinv.net>
NNTP-Posting-Host: 172.20.134.41
X-Original-NNTP-Posting-Host: 172.20.134.41
Date: 1 Mar 2013 11:16:10 -0800
X-Trace: forums-1-dub 1362165370 172.20.134.41 (1 Mar 2013 11:16:10 -0800)
X-Original-Trace: 1 Mar 2013 11:16:10 -0800, 172.20.134.41
Lines: 12
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.general:249774
Article PK: 1308039

To specify, we are still on PB Classic.

When you say the mixing of DLL's can cause crashing, we do
have some clients who will have one version of our
application in Production, with a newer version of our
application in Test. The newer version may be built in
PB12.0 Classic, while the Production one is in 11.0.
However, these are always installed on different boxes.

If you did have them installed on the same box, can
PBVM120.dll and PBVM110.dll conflict, and cause the errors
seen?


Scott Morris Posted on 2013-03-01 19:59:28.0Z
Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes
Newsgroups: sybase.public.powerbuilder.general
Subject: Re: Experiencing frequent crashing issues since upgrading to PB12. Need help.
References: <op.ws95qazfq59cbq@scott-win7.divinv.net> <5130fe7a.7ae9.1681692777@sybase.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: "Scott Morris" <bogus@abc.def>
Message-ID: <op.ws99td2hq59cbq@scott-win7.divinv.net>
User-Agent: Opera Mail/11.51 (Win32)
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Date: 1 Mar 2013 11:59:28 -0800
X-Trace: forums-1-dub 1362167968 172.20.134.152 (1 Mar 2013 11:59:28 -0800)
X-Original-Trace: 1 Mar 2013 11:59:28 -0800, vip152.sybase.com
Lines: 23
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.general:249775
Article PK: 1308040


On Fri, 01 Mar 2013 14:16:10 -0500, Chris <Polson> wrote:

> To specify, we are still on PB Classic.
>
> When you say the mixing of DLL's can cause crashing, we do
> have some clients who will have one version of our
> application in Production, with a newer version of our
> application in Test. The newer version may be built in
> PB12.0 Classic, while the Production one is in 11.0.
> However, these are always installed on different boxes.
>
> If you did have them installed on the same box, can
> PBVM120.dll and PBVM110.dll conflict, and cause the errors
> seen?

You can safely host multiple major versions on the same machine. So, it
is safe to have apps built with 11, 12, and 12.5 on the same machine (due
to the way SAP names the dlls). The concern is that your customer has
dlls from some other build of PB 12 in addition to (or instead of) dlls
from your specific build. If you have apps built with different builds of
PB12, they will all use runtime DLLs of the same name. Presumably you
have verified that your client configurations meet the requirements for
PB12.


Paul Murray Posted on 2013-03-02 02:46:29.0Z
From: "Paul Murray" <pemurray@interrasys.com>
Newsgroups: sybase.public.powerbuilder.general
References: <op.ws95qazfq59cbq@scott-win7.divinv.net> <5130fe7a.7ae9.1681692777@sybase.com> <op.ws99td2hq59cbq@scott-win7.divinv.net>
Subject: Re: Experiencing frequent crashing issues since upgrading to PB12. Need help.
Lines: 31
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-RFC2646: Format=Flowed; Response
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <51316805$1@forums-1-dub>
Date: 1 Mar 2013 18:46:29 -0800
X-Trace: forums-1-dub 1362192389 172.20.134.152 (1 Mar 2013 18:46:29 -0800)
X-Original-Trace: 1 Mar 2013 18:46:29 -0800, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.general:249779
Article PK: 1308046

By any chance are you using PBRuntime files? If yes, make sure that they
correspond to the build of the development tool that you are using.

"Scott Morris" <bogus@abc.def> wrote in message
news:op.ws99td2hq59cbq@scott-win7.divinv.net...
> On Fri, 01 Mar 2013 14:16:10 -0500, Chris <Polson> wrote:
>
>> To specify, we are still on PB Classic.
>>
>> When you say the mixing of DLL's can cause crashing, we do
>> have some clients who will have one version of our
>> application in Production, with a newer version of our
>> application in Test. The newer version may be built in
>> PB12.0 Classic, while the Production one is in 11.0.
>> However, these are always installed on different boxes.
>>
>> If you did have them installed on the same box, can
>> PBVM120.dll and PBVM110.dll conflict, and cause the errors
>> seen?
>
> You can safely host multiple major versions on the same machine. So, it
> is safe to have apps built with 11, 12, and 12.5 on the same machine (due
> to the way SAP names the dlls). The concern is that your customer has
> dlls from some other build of PB 12 in addition to (or instead of) dlls
> from your specific build. If you have apps built with different builds of
> PB12, they will all use runtime DLLs of the same name. Presumably you
> have verified that your client configurations meet the requirements for
> PB12.


Chris Pollach Posted on 2013-03-05 12:39:01.0Z
From: Chris Pollach <cpollach@travel-net.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130215 Thunderbird/17.0.3
MIME-Version: 1.0
Newsgroups: sybase.public.powerbuilder.general
Subject: Re: Experiencing frequent crashing issues since upgrading to PB12. Need help.
References: <5130ec2e.724e.1681692777@sybase.com>
In-Reply-To: <5130ec2e.724e.1681692777@sybase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <5135e765$1@forums-1-dub>
Date: 5 Mar 2013 04:39:01 -0800
X-Trace: forums-1-dub 1362487141 172.20.134.152 (5 Mar 2013 04:39:01 -0800)
X-Original-Trace: 5 Mar 2013 04:39:01 -0800, vip152.sybase.com
Lines: 76
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.general:249808
Article PK: 1308100

Hi Chris;

1) Ditto on what Scott said about EBF's versus MR's. I would suggest
only applying an EBF in a production down situation and *only* after
careful thought and extensive testing.
- The current MR build BTW is 4015 for PB 12.5.1

2) What DB client are you using to connect to SS2008?

3) Did you set the "Free DB Libraries" option on in your Application object?

4) Does your application use the PFC?

--

Regards ... Chris
President: OSUG / STD Inc.
Vice President: ISUG-TECH
Blog: http://chrispollach.blogspot.com
SourceForge: http://sourceforge.net/projects/stdfndclass
PBDJ: http://chrispollach.sys-con.com
TKD: http://www.syeoh.com

On 3/1/2013 12:58 PM, Chris Polson wrote:
> Hello,
>
> Since building our application with PB12 EBF 6639, (our last
> was built with PB11.2 Build 8869.
>
> During this upgrade of our application we did two things. We
> upgraded our clients to SQL Server 2008. Many had been on
> SQL Server 2005, and on Sybase. The other thing we did was
> upgrade PB to 12 EBF 6639.
>
> Our clients are seeing our application 'randomly crash' in
> dozens of areas in the application.
>
> The typical one we are seeing is in
>
> module: PBVM120.dll, exception code 0xc0000005 fault offset:
> 0x000c0cbf
>
> We have also seen module: pbdwe120.dll, exception code
> 0xc0000005 fault offset: 0x00092015 and
>
> module: pbshr120.dll, exception code 0xc0000005, fault
> offset: 000f2040
>
> But mostly we are seeing the first in PBVM120.dll.
>
> Most of the crashing issues are not recreatable for us. Our
> clients seems to run into them randomly. There was one given
> to us by clients that was 100% recreatable. It would crash
> for the client when closing a window of ours. We seemed to
> be able to solve this one by calling Yield() when the user
> would close. However, replacing the Yield() with a
> GarbageCollect() also worked. Replacing it with a MessageBox
> also worked. Whatever seemed to give the code 'time to catch
> up' so to speak... seemed to work for this one specific
> area. No clue why it worked, but these 3 'solutions' did.
>
> Are there any reports of this out there anywhere? I called
> Sybase to open a ticket, but they no longer do the $400
> ticket thing where you can open a ticket.
>
> Our application was running fine at 100's of client sites
> when built in PB11.2 and running SS2005 or Sybase. Now with
> PB12 6639 and SS2008, the application is crashing frequently
> and in many areas for the 30+ clients we have upgraded.
>
> Is there anything on this, or anyone experiencing this?
>