Solving a segment 11 violation is never easy.
The Galaxy error is from software Arbortext used several years ago to
program, debug and compile the Epic executable. As I recall, they are no
longer using it. Also, in the not to distant future, Epic 4.3.1 will no
longer be supported by PTC. Making a resolution of any future problems
even more difficult.
The obvious looking problem is that something in Server 2000 SP 4 or later
is causing Epic to crash. Basically a Segment 11 is Epics way of saving
the OS when Epic tries to do something the OS does not allow. What these
things are is fairly limitless.
If you have a maintenance agreement with PTC and have access to a later
version of Epic, you might find a test machine, install a later
(preferably the latest) version of Epic and see what happens. If it still
crashes, then I'd start looking at your code. But if it is something from
the older compiled files, then you may be okay.
Given the age of 4.3.1, even if you find the problem and it is in the Epic
code, I seriously doubt you will see a fix. You may get a work around or
you may be forced to upgrade Epic.
Sorry, not much help, but resolving a segment 11 takes time and patience
(amongst other things). If you have ever done any troubleshooting then
that will help. Just approach the problem logically. Add some debug code
to your scripts and see where you are just before you crash. Look at the
last run code, then run the next sequence. Try running a function at a
time from the command line. Then when you finally crash, really start
debugging the last script run. Of course, it could be a combination of
things already done just coming together.
Do not try to fix all the problems at one time. Work one issue at a time.
They may be related, but approach the segment 11 as one problem and the
Galaxy error as another.