EQAVS1010E Communication required by Service Entry Point function dropped.

[glenrock-oz]

Type: Bug

I am trying to debug via SEP. The entry point is added ok. But in VSCode I get error "EQAVS1010E Communication required by Service Entry Point function dropped".
In the DebugService_log.txt file on the IBM it shows:
SSLException thrown when reading SEP daemon protocol message

After setting the SEP the console shows:
To client: {"type":"event","seq":8,"event":"terminated"}
From client: disconnect({"restart":false,"terminateDebuggee":false})

To client: {"type":"response","seq":0,"request_seq":2,"success":true,"command":"launch"}
To client: {"type":"response","seq":0,"request_seq":5,"success":false,"command":"configurationDone","body":{"error":{"id":"8999","format":"java.lang.NullPointerException\n\tat com.ibm.debug.pdt.daas.internal.dap.DAPSession.getVersionJSON(DAPSession.java:439)\n\tat com.ibm.debug.pdt.daas.internal.dap.events.DAPEvent.getEvent(DAPEvent.java:117)\n\tat com.ibm.debug.pdt.daas.internal.dap.requests.DAPConfigurationDoneRequest.generateEvents(DAPConfigurationDoneRequest.java:123)\n\tat com.ibm.debug.pdt.daas.internal.dap.requests.DAPRequest.process(DAPRequest.java:139)\n\tat com.ibm.debug.pdt.daas.internal.dap.requests.DAPRequest.process(DAPRequest.java:97)\n\tat com.ibm.debug.pdt.daas.internal.dap.DAPRequestProcessor$1.run(DAPRequestProcessor.java:119)\n\tat org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)\n"}}}

The certificate is self-signed but debug via batch/attach to a job are working fine.

I can connect via openssl to port 8005.
When I run the program in a terminal window - the job does pause waiting for the debug job.

Hopefully it's just a config error.

Thanks for your help.

Extension version: 2.18.3
VS Code version: Code 1.113.0 (cfbea10c5ffb233ea9177d34726e6056e89913dc, 2026-03-24T15:07:18+01:00)
OS version: Windows_NT x64 10.0.26100
Modes:

System Info

Item	Value
CPUs	12th Gen Intel(R) Core(TM) i7-1255U (12 x 2611)
GPU Status	2d_canvas: enabled GPU0: VENDOR= 0x8086, DEVICE=0x4628 [Intel(R) UHD Graphics], DRIVER_VENDOR=Intel, DRIVER_VERSION=32.0.101.6556 ACTIVE GPU1: VENDOR= 0x1414, DEVICE=0x008c [Microsoft Basic Render Driver], DRIVER_VERSION=10.0.26100.7309 Machine model name: Machine model version: direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off trees_in_viz: disabled_off video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off
Load (avg)	undefined
Memory (System)	15.69GB (1.51GB free)
Process Argv	--crash-reporter-id 9de8d6a5-c491-4275-a38b-80fba556a421
Screen Reader	no
VM	0%

A/B Experiments

vsliv368:30146709
pythonvspyt551cf:31249601
binariesv615:30325510
nativeloc1:31344060
dwcopilot:31170013
dwoutputs:31242946
copilot_t_ci:31333650
e5gg6876:31282496
pythonrdcb7:31342333
6518g693:31463988
aj953862:31281341
4f60g487:31327383
63221493:31336333
envsactivate1:31464700
cloudbuttont:31379625
3efgi100_wstrepl:31403338
839jf696:31457053
use-responses-api:31390855
ddidt:31399633
je187915:31401257
ec5jj548:31422691
cp_cls_t_966_ss:31454198
4je02754:31466945
find_all_ref_in_bg_f:31469307
c3h7c220:31478652
ge8j1254_inline_auto_hint_haiku:31431912
38bie571_auto:31478677
cp_cls_c_1081:31454833
conptydll_false:31485576
ia-use-proxy-models-svc:31452481
e9c30283:31461165
test_control1:31471004
control_6dc23131:31467998
idci7584:31464702
nes-ftch-ctrl:31485414
showingstats:31481873
534a6447_copy:31478748
hg17d649:31458077
nes-extended-on:31455476
chat:31457767
8hig5102:31480529
67jbj424:31486320
bg_compact_c:31481651
t-some:31486549
cpptoolsoff-v2:31475362
db0gd219:31481871
client_tst_t:31484207
po_split_t:31486092
ddid_c:31478207
getcmakediagnosticsoff:31487008
ahei0758:31485062

[mkwan01]

@glenrock-oz Please attach the contents of the following trace files from the host:

-- /QIBM/UserData/IBMIDEBUGSERVICE/startDebugService_workspace/startDebugServiceNavigator.log
-- /QIBM/UserData/IBMiDebugService/startDebugService_workspace/QDBGSRV/.metadata/.log

[glenrock-oz]

Thanks for your help - please find attached the 2 log files.

…

Message ID: ***@***.*** .com>

[glenrock-oz]

@mkwan01 Have you been able to review the logs yet? Thanks

[mkwan01]

@glenrock-oz I am not able to see the log files. Please try to paste the contents of the log files in this issue again. Please also try to paste the complete trace from the VSCode debug console here (remove the password before pasting). Thanks.

[glenrock-oz]

Log files are attached here - thanks

dot.log

startDebugServiceNavigator (1).log

[mkwan01]

1. Are you able to use SEP debug on the same host before? It it works before and fails recently, please check whether you have any recent changes that may have an impact.
2. Please restart debug service and try again, and see if the behavior is different.
3. Does your profile password contain any special characters (e.g. single or double quotes, slash, etc.)?
4. Is your VSCode client and/or the host on a different language other than English?
5. If it still fails after the checks above, please attach the full DAP trace from VSCode debug console. Please remove the password in the trace content before pasting it here.
   @glenrock-oz

[mkwan01]

@glenrock-oz Please also try to set SEP on a different program and see if the behavior is different.

[glenrock-oz]

1. I have never been able to use SEP debug - I have tried on 2 different hosts.
2. Restarting the debug service doesn't help - this problem has been ongoing for some time - since version 2.x of the debugger
3. Password has a trailing @ - otherwise just mixed case can a number
4. VSCode and IBM servers are english
   I will capture the DAP trace now and attach.

[glenrock-oz]

debuglog.txt
Is this the correct log you are needing? thanks

[mkwan01]

@glenrock-oz The debuglog.txt file that you attached was captured before you set the SEP. It did not contain the trace when setting the SEP. When setting a SEP, we should see a log like the following in the Debug Console:
From client: launch({"type":"IBMiDebug","request":"launch","subType":"sep","action":"set","name":"Service Entry Point", ...}

[mkwan01]

Please use the following steps to capture the right DAP trace from the Debug Console:

1. Enable debug trace
2. After connecting to the host, clear the logs from the Debug Console. The logs before the SEP set action are not useful.
3. Set a SEP
4. Capture the new trace statements from the Debug Console and attach to this issue

[mkwan01]

I also noticed that you have two breakpoints on iASP files. Please try to clear these breakpoints before setting the SEP and see whether it has any impact to the behavior.

[glenrock-oz]

I have tried using a srvpgm not in the iASP but the error looks the same to me. Attached is the new log.

debug2.txt

[mkwan01]

@glenrock-oz Please tell us the host debug service version number (version in package.json file) and the client side IBM i Debug extension version number. Here are the latest versions:

• IBM i Debug Service (v3.0.3)
• IBM i Debug extension (v3.0.3)