Keep getting memory errors!

[daengh]

Sorry, developer-debug anal retentive hat on. When you say '...the install of Sybase', exactly what do you mean? SQL Server or something else?

Are the errors more common if they run two or more instances at the same time?

If you know, are the various versions of GOLD built with the same release of PowerBuilder? (we're currently running down something in our product that seems to be related to DLL mismatch. very annoying.)

 

[ned4spd8874]

To be honest, I'm not a developer...I'm just supposed to support their programs. Sybase is something that is required for this program to work. I don't know much more about it to be honest.

I don't think the errors are more or less common if he runs more than one instance. He has also gotten the errors with only one instance open.

There is only one version of GOLD running at a time. He would be running the same version as everyone else.

 

[daengh]

Oh, okay, I see the Sybase Open Connect database driver in the trace.
("c:\sybase\OCS-12_0\")

Do the different versions of GOLD connect to databases running on different versions of SQL Server? If yes *and* they're sharing a db connection setup (using one ODBC Data Source or connection string), the application might be setting up a connection with bad info. That could cause errors to pop up only when something trips on a particular issue - getting back a TEXT value when expecting a STRING for instance, because the connection isn't set up for it.

Is the version of Open Client on that machine current, or does that user have multiple copies installed so they can run older versions of something?

We see errors like this when something goes south while we're doing intensive operations involving the PB DataWindow engine. In your trace module list, "PBDWE105.dll", 3rd from the top. You might ask your user to add the switch ' /pbdebug' to the shortcut they use to start the app. This will write a text trace file showing all the operations PB does. WARNING:: this will slow down the application *tremendously*, but it will give your developers something to look at to see what the application is doing up to the point of failure.

 

[ned4spd8874]

Some of this info is actually a little old. We are now running version 15 of Sybase, not 12 like it's shown here.

Also, there is only one version of Gold running and connecting to the database. And there is only one database.

I'll suggest that switch, but I suspect he won't like it if it slows him down as much as you are saying. He's not the easiest user to deal with.

Also, I'm not supporting that building anymore, so it's a little hard to fully support and test some of this stuff for me anymore. But I am going to suggest that switch and we'll see what happens.

 

[daengh]

Well, I'd hope he'd only need to do it once to give your developers something to work with.

Speaking as a developer, it's maddening to get reports of crashes that can't be reliably reproduced. PBDEBUG traces put us in the general vicinity of the last one of this type that we solved here.

 

[Tedster]

use memtest 86+ to diagnose memory errors boot from a cd or floppy. run for 7 passes or more.