Re: SEP debug not working (PC upgraded? to vista)

When I am trying to debug a program I can find those jobs, They show
nothing in the joblog other than they started. If I use my laptop (still
running XP) even over a VPN connection I can use SEP to debug. I think
this may be a vista specific issue. I'll ask the network guys is port 3825
is blocked somehow on vista, but the local PC's firewall is off.
Also your description of what is happening is perfect I set the SEP, debug
starts up, if i click on any action, step or just the arrow to run the
program, Nothing happens and I get those pop ups. It sounds like Vista is
not handling the connection properly, maybe when we get RDi, Though that
may be a while.



From:
Xuan Chen <xuanchen@xxxxxxxxxx>
To:
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
Date:
06/25/2008 07:54 PM
Subject:
Re: [WDSCI-L] SEP debug not working (PC upgraded? to vista)



It seems to me a debug server problem.

So you could set a SEP, and then your debug session comes up (switching to

debug perspective, and have process listed, etc)? But then you got a
debugger error saying no response?

Could you please check if any job name QB5SERVER or QB5PHSRV in your
system? If yes, what is the job log of those jobs.
And please also see any job log with those names even you did not see any
active jobs.

Thanks,

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





"Bob P. Roche" <BRoche@xxxxxxxxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
06/25/2008 04:30 PM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
cc

Subject
[WDSCI-L] SEP debug not working (PC upgraded? to vista)






I usually debug my CGI programs using SEP. After upgrading to Vista
Business, All functions in WDSC that i use work except debugging. I
continually get a popup stating. No response from debug engine, Continue
to wait for engine to respond?

Has anyone seen this. Upgrading WDSC from 7.0.0.4 to 7.0.0.6 did not help.