# \[APM\] - Error: failed to reset strict operations; disconnecting  from mcpd

**URL:** <https://community.f5.com/t/apm-error-failed-to-reset-strict-operations-disconnecting-from-mcpd/75170>\
**Category:** Technical Forums\
**Tags:** upgrade, application-delivery, apm\
**Created:** [September 19, 2024, 2:56pm UTC](https://community.f5.com/t/apm-error-failed-to-reset-strict-operations-disconnecting-from-mcpd/75170 "2024-09-19T14:56:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Blue\_whale](https://avatars.discourse-cdn.com/v4/letter/b/76d3ee/32.png) [@Blue\_whale](https://community.f5.com/u/Blue_whale)\
**Post date:** [September 19, 2024, 2:56pm UTC](https://community.f5.com/t/apm-error-failed-to-reset-strict-operations-disconnecting-from-mcpd/75170/1 "2024-09-19T14:56:50Z")

</div>

Hello Experts ,

When we try to verify the sys config with the command&nbsp; **"load sys config verify**" , we are getting beow error message followed with the services restart …[Bug ID 997793 (f5.com)](https://cdn.f5.com/product/bugtracker/ID997793.html) , We tried to remove the old **epsec-package** file&nbsp; and restarted , but no luck .

Can anyone please advise on this ?

Validating configuration…  
&nbsp; /config/bigip\_base.conf  
&nbsp; /config/bigip\_user.conf  
&nbsp; /config/bigip.conf  
&nbsp; /config/bigip\_script.conf  
Error: failed to reset strict operations; disconnecting &nbsp;from mcpd. &nbsp;Will reconnect on next command.  
The connection to mcpd has been lost, try again.

---

<div class="post-metadata">

**Author:** ![Lucas\_Thompson](https://d1p9zq3aats0t8.cloudfront.net/user_avatar/community.f5.com/lucas_thompson/32/19403_2.png) [@Lucas\_Thompson](https://community.f5.com/u/Lucas_Thompson)\
**Post date:** [September 19, 2024, 9:55pm UTC](https://community.f5.com/t/apm-error-failed-to-reset-strict-operations-disconnecting-from-mcpd/75170/2 "2024-09-19T21:55:30Z")

</div>

Do the workaround first (stop the watchdog) so MCP and TMM don’t get restarted by the watchdog while they’re busy processing the EPSEC files.

You can use the “bigstart status” command to make sure everything has started OK.

After it starts, then modify your configuration to remove all epsec-package except the latest one, save the config (save sys config), then restart.