Unknown software exception - followed by designer crashing
Posted: Fri Apr 22, 2005 10:00 am
We are getting strange errors after upgrading to 7.5.1 from 7.1.
When ever we open sequencers that are quite big (probably some 40 to 50 activities) and just try to do a couple of changes (can be anything just parameter changes or trigger changes) we get a weird error and the designer simply crashes. The same error is getting logged in windows system log. Few of the errors i copies and pasted below.
We are trying to see all the options. Contacted Ascential support. Looked into google and tried all the options. Nothing seems to work for us. It is really troubling us a lot. It is happening only in one particular project (but we have the sequencer jobs with so many activities only in this project).
Then we installed Windows Xp following some posts in google. Still we are getting the errors and the designer crashes (luckily for us it don't lock the jobs which are opened). But the error messages are a bit different. They are Dr. watson messages in application log of the windows system.
Anyone faced these problems earlier??
To my knowledge i can only think of few reasons for these.
1. We are not using the right Service Pack. (currently we use SP4 on windows 2000. is it okay?)
2. There is some virus causing this. (kind of weird but we got the similar errors a couple of years back using a different application - rational clearcase)
3. Installation problems (but i am not sure of this as this problem comes on all our clients)
4. Dll's are corrupted or not the right version(i checked for that and i don't think it is the reason)
If you guys can help me out in thinking from different directions it will be really nice.
Thanks,
Srikanth
When ever we open sequencers that are quite big (probably some 40 to 50 activities) and just try to do a couple of changes (can be anything just parameter changes or trigger changes) we get a weird error and the designer simply crashes. The same error is getting logged in windows system log. Few of the errors i copies and pasted below.
Code: Select all
"Application popup: DSDesign.exe - Application Error : The instruction at "0x77fcc7ae" referenced memory at "0x00390037". The memory could not be "written."
"Application popup: DSDesign.exe - Application Error : The exception unknown software exception (0xc0000017) occurred in the application at location 0x77fb14f4."
Application popup: DSDesign.exe - Application Error : The instruction at "0x6c3b5115" referenced memory at "0x00000004". The memory could not be "read".
Then we installed Windows Xp following some posts in google. Still we are getting the errors and the designer crashes (luckily for us it don't lock the jobs which are opened). But the error messages are a bit different. They are Dr. watson messages in application log of the windows system.
Code: Select all
The application, C:\Program Files\Ascential\DataStage\DSDesign.exe, generated an application error The error occurred on 04/21/2005 @ 15:37:43.109 The exception generated was c0000005 at address 7C93426F (ntdll!RtlInitializeContext)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Fault bucket 189458997.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Faulting application dsdesign.exe, version 7.5.1.18, faulting module ntdll.dll, version 5.1.2600.2180, fault address 0x0003426f.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
he application, C:\Program Files\Ascential\DataStage\DSDesign.exe, generated an application error The error occurred on 04/21/2005 @ 15:35:40.015 The exception generated was c0000005 at address 734493DC (MSVBVM60!_vbaStrVarCopy)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Faulting application dsdesign.exe, version 7.5.1.18, faulting module msvbvm60.dll, version 6.0.96.90, fault address 0x000293dc.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Anyone faced these problems earlier??
To my knowledge i can only think of few reasons for these.
1. We are not using the right Service Pack. (currently we use SP4 on windows 2000. is it okay?)
2. There is some virus causing this. (kind of weird but we got the similar errors a couple of years back using a different application - rational clearcase)
3. Installation problems (but i am not sure of this as this problem comes on all our clients)
4. Dll's are corrupted or not the right version(i checked for that and i don't think it is the reason)
If you guys can help me out in thinking from different directions it will be really nice.
Thanks,
Srikanth