# No response trace labels HAPC request

**URL:** <https://forum.sierrawireless.com/t/no-response-trace-labels-hapc-request/5286>\
**Category:** Development tools\
**Created:** [October 7, 2011, 5:37pm UTC](https://forum.sierrawireless.com/t/no-response-trace-labels-hapc-request/5286 "2011-10-07T17:37:31Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![awneil](https://avatars.discourse-cdn.com/v4/letter/a/49beb7/32.png) [@awneil](https://forum.sierrawireless.com/u/awneil)\
**Post date:** [October 7, 2011, 5:37pm UTC](https://forum.sierrawireless.com/t/no-response-trace-labels-hapc-request/5286/1 "2011-10-07T17:37:31Z")

</div>

When I press the ‘Remote traces configuration’ button, nothing happens!

A message appears above the Traces listing:

> [@Developer Studio Build Version 1.2.0.201012171243-R6026](#):
>
> Impossible to retrieve the trace labels (no response trace labels HAPC request)

So what does that mean? And how do I fix it??

The Traces list is still updating with new traces;  
the Console view is still showing messages from the unit, but not responding to AT commands;  
the Status view appears to be hung.

---

<div class="post-metadata">

**Author:** ![awneil](https://avatars.discourse-cdn.com/v4/letter/a/49beb7/32.png) [@awneil](https://forum.sierrawireless.com/u/awneil)\
**Post date:** [October 7, 2011, 5:40pm UTC](https://forum.sierrawireless.com/t/no-response-trace-labels-hapc-request/5286/2 "2011-10-07T17:40:31Z")

</div>

Closing & re-opening the port (in the ‘Devices’ view) seems to have kicked it back into order…

Firmware: R7.44

---

<div class="post-metadata">

**Author:** ![daav](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/daav/32/2767_2.png) [@daav](https://forum.sierrawireless.com/u/daav)\
**Post date:** [October 10, 2011, 6:24am UTC](https://forum.sierrawireless.com/t/no-response-trace-labels-hapc-request/5286/3 "2011-10-10T06:24:23Z")

</div>

DS sends a set of requests to the module to initialize the views (AT commands for the status view, or requests to get the trace elements labels (“ADL”, “HLH”, or “LLH” labels for the traces are dynamically retrieved), etc…)  
Sometimes a request may not answer, and indeed closing/reopening the port fixes the issue.  
Please note that we’re precisely working at adding more reliability to this aspect, making DS control that all is fine, and retry by itself if it’s not.