Re: SEP Internal Error

Hi Xuan,

It happens when the program is invoked though it *does* find the source.
After restarting the server jobs (Adam's suggestion) it doesn't give me the
error anymore but it doesn't always invoke the SEP either. Note I am
debugging a request coming in through Apache and this program is three
levels deep into the call stack. The only way I can consistently get it to
work is if I restart the Apache instance, so there may be other things
besides that error involved with why SEP isn't always working consistently.

Just curious, why won't remove and then re-add work vs. requiring a
refresh. It would seem to me that anything the refresh does should also be
done on a remove/add??

Aaron Bartell
http://mowyourlawn.com

On Thu, Oct 16, 2008 at 2:00 PM, Xuan Chen <xuanchen@xxxxxxxxxx> wrote:

From the stack trace, it seems the problem was related to locating source

when a debug session started up. It should not have anything to do with
your setting SEP or refreshing it.
When did this error come up? During the setting of SEP, or when a debug
session started up because of the SEP? Are you using iSeries project by
any chance?

If you recompile a program, you need to use Refresh button to refresh the
SEP. Remove and re-add will not work.
One way to make sure the SEP server for you is cleaned up is click on the
triangle in the Service Entry Point view, and choose one of the "Clear
Service Entry Points" menu.

Thanks,

Xuan Chen, Problem Determination Tools for iSeries
(905) 413-3769 T/L 313-3769
xuanchen@xxxxxxxxxx