Job Sequence crashes Designer - Any ideas?
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 9
- Joined: Tue Apr 27, 2004 5:13 pm
- Location: Sydney
Job Sequence crashes Designer - Any ideas?
DataStage Server 7.5.1
UNIX on SUN Solaris
Windows 2000 Client
When creating/editing Job Sequences in Designer, the Designer application is crashing with EXTREME regularity...an activity stage is opened/closed. We have got into the habit of saving after every change, but this still occurs:
DSDesign.exe - Application Error
The instruction at "xxxxx" referenced memory at"xxxxx". The memory could not be read. Click on OK to terminate the program.
This is happening on ALL client machines.
Anyone experienced this? All suggestions welcome.
Cheers,
Pete
UNIX on SUN Solaris
Windows 2000 Client
When creating/editing Job Sequences in Designer, the Designer application is crashing with EXTREME regularity...an activity stage is opened/closed. We have got into the habit of saving after every change, but this still occurs:
DSDesign.exe - Application Error
The instruction at "xxxxx" referenced memory at"xxxxx". The memory could not be read. Click on OK to terminate the program.
This is happening on ALL client machines.
Anyone experienced this? All suggestions welcome.
Cheers,
Pete
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Kim, the 'buffering' issue *was* a performance related server side bug with row buffering and is unrelated to anything crashing on the client side.
And 7.5A is older than 7.5.1x, so that fix would be incorporated in the version you are running.
And 7.5A is older than 7.5.1x, so that fix would be incorporated in the version you are running.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
What is the most recent version of DataStage?chulett wrote:Kim, the 'buffering' issue *was* a performance related server side bug with row buffering and is unrelated to anything crashing on the client side.
And 7.5A is older than 7.5.1x, so that fix would be incorporated in the version you are running.
Is it 7.5.1A or 7.5.1D?
Thanks in Advance
Re: Job Sequence crashes Designer - Any ideas?
I thought I would try to resurrect this thread since I am having the same problem. It wasn't a particularly big problem for us in the past since we did not have many sequence jobs but now that I have written a few, it is becoming more annoying.
The designer crash only happens when I am editing a job sequence -- it has never happened when working on a server job, no matter how complex. Once there are about five items on the canvas, designer will eventually "Encounter a problem and need to close" with a error reading some low-numbered address. There is no discernable pattern to when it happens, other than the more items there are on the designer canvas, the more likely it is to crash. The crash might occur after editing the properties of a stage, it might occur when I click the "job properites" button, or it might happen after dragging one of the stages a fraction of an inch across the canvas.
I filed a ecase with Ascential/IBM back in September of '05, but the issue was not resolved. After a few exchanges, the Ascential rep. told me that she had seen some problems with my version of designer (7.5.1.38, apparently the version that shipped with DS 7.5.1.a server edition) and sent me a new copy. The "new" copy turned out to also be version 7.5.1.38 so, of course, it did not fix the problem. Neither did the XP SP2 patch, which I had already tried. After a few more exchanges, I got "Gee, it's working fine here" and that is where the matter died.
This sort of intermittent bug is going to be difficult for Ascential to fix, so if anyone else experiences designer crashes while editing job sequences, please post the details. Maybe we can establish enough of a pattern to allow the bug to be found and fixed.
Thanks,
--JV
The designer crash only happens when I am editing a job sequence -- it has never happened when working on a server job, no matter how complex. Once there are about five items on the canvas, designer will eventually "Encounter a problem and need to close" with a error reading some low-numbered address. There is no discernable pattern to when it happens, other than the more items there are on the designer canvas, the more likely it is to crash. The crash might occur after editing the properties of a stage, it might occur when I click the "job properites" button, or it might happen after dragging one of the stages a fraction of an inch across the canvas.
I filed a ecase with Ascential/IBM back in September of '05, but the issue was not resolved. After a few exchanges, the Ascential rep. told me that she had seen some problems with my version of designer (7.5.1.38, apparently the version that shipped with DS 7.5.1.a server edition) and sent me a new copy. The "new" copy turned out to also be version 7.5.1.38 so, of course, it did not fix the problem. Neither did the XP SP2 patch, which I had already tried. After a few more exchanges, I got "Gee, it's working fine here" and that is where the matter died.
This sort of intermittent bug is going to be difficult for Ascential to fix, so if anyone else experiences designer crashes while editing job sequences, please post the details. Maybe we can establish enough of a pattern to allow the bug to be found and fixed.
Thanks,
--JV
peter_dickinson wrote:DataStage Server 7.5.1
UNIX on SUN Solaris
Windows 2000 Client
When creating/editing Job Sequences in Designer, the Designer application is crashing with EXTREME regularity...an activity stage is opened/closed. We have got into the habit of saving after every change, but this still occurs:
DSDesign.exe - Application Error
The instruction at "xxxxx" referenced memory at"xxxxx". The memory could not be read. Click on OK to terminate the program.
This is happening on ALL client machines.
Anyone experienced this? All suggestions welcome.
Cheers,
Pete
Yup... Thanks.chulett wrote:Call Support. They will have to make the patch "available" to you and the specific ecase number helps them know which one you need.
![Smile :)](./images/smilies/icon_smile.gif)
I guess i need to wait.
![Wink :wink:](./images/smilies/icon_wink.gif)
-Kumar