kastanek
Well Known Member
Dear List.
Here's a doozie for you guys that I just can't seem to get my head around.
We have a user that is trying to run a particular UBE (R04571) locally.
When she submits the report it launches on her Windows2000 Fat client and
immediately gets the pop-up error "UBE R04751 -- ZJDE0001 has caused an
exception. Your system may become unstable." and then the system
proceeds to become unstable. We have to use TASK MANAGER to end the
process and when we exit OneWorld the activConsole.exe program has to be
ended as well before OneWorld can be re-launched.
The SAME user using the SAME user ID and the SAME job parameters including
the same selected data CAN run this job from another Fat Client machine.
All if the Fat Clients have the same Full package build on them and all of
the same Update packages. I tried deleting Global Tables - no good; I
tried reinstalling the client (full and all update packages) - no good. I
was going to try reinstalling the Data Base connection engine (Client
Access Express in this case) but she can run other UBE's just fine locally
on her machine... just not this one UBE.
I would have suggested to rebuild the whole machine from the OS up but
another incident similar to this one was just reported to me for a custom
UBE. It runs fine locally on other users fat clients but will not run
locally on this other person's machine. He however can run it himself on
other users machines.
So the user profile does not seem to be an issue, the UBE runs on most
machines, the environment does not seem to matter since we get the same
result in both PY and DV. It seems to be something unique to the machine
and a different UBE is uniquely messing up on another machine.
Anyone have any thoughts?
Please help.
Regards,
Gerald
Here's a doozie for you guys that I just can't seem to get my head around.
We have a user that is trying to run a particular UBE (R04571) locally.
When she submits the report it launches on her Windows2000 Fat client and
immediately gets the pop-up error "UBE R04751 -- ZJDE0001 has caused an
exception. Your system may become unstable." and then the system
proceeds to become unstable. We have to use TASK MANAGER to end the
process and when we exit OneWorld the activConsole.exe program has to be
ended as well before OneWorld can be re-launched.
The SAME user using the SAME user ID and the SAME job parameters including
the same selected data CAN run this job from another Fat Client machine.
All if the Fat Clients have the same Full package build on them and all of
the same Update packages. I tried deleting Global Tables - no good; I
tried reinstalling the client (full and all update packages) - no good. I
was going to try reinstalling the Data Base connection engine (Client
Access Express in this case) but she can run other UBE's just fine locally
on her machine... just not this one UBE.
I would have suggested to rebuild the whole machine from the OS up but
another incident similar to this one was just reported to me for a custom
UBE. It runs fine locally on other users fat clients but will not run
locally on this other person's machine. He however can run it himself on
other users machines.
So the user profile does not seem to be an issue, the UBE runs on most
machines, the environment does not seem to matter since we get the same
result in both PY and DV. It seems to be something unique to the machine
and a different UBE is uniquely messing up on another machine.
Anyone have any thoughts?
Please help.
Regards,
Gerald