'proxyav' service-group cannot be deleted with error, "% Cannot delete the service-group specified, it is in use."

Products

• Advanced Secure Gateway Software - ASG
• ProxySG Software - SGOS

Issue/Introduction

proxyav service-group cannot be deleted with error "% Cannot delete the service-group specified, it is in use." even though there is no policy rule using the AV service-group.

Resolution

When a ProxyAV ICAP Server is added to Malware Scanning, ProxySG automatically adds proxyav service-group along with proxyav1 ICAP server (proxyav2 will be added if proxyav1 does exist elready, proxyav3 if proxyav1 and proxyav2 exists and so on)

 

If Malware Scanning is enabled and if there is an attempt to delete proxyav1 server or proxyav service-group, the attempt will fail with the following error.

Deleting proxyav1 [under Configuration tab > Content Analysis > ICAP > ICAP Services tab] fails with the following error.

 

        "Service proxyav1 cannot be deleted. It is referenced by a service group"

 

If there is an attempt to delete proxyav Service Group (Configuration tab > Content Analysis > Service Groups), it would fail with the following error.

 

        "% Cannot delete the service-group specified, it is in use."

 

 

Because the service-group and ICAP Server created by Malware Scanning cannot be deleted without disabliing Malware Scanning, in order to delete proxyav1 ICAP Server and/or proxyav service-group, follow the steps below.

1. Configuration tab > Threat Protection > Malware Scanning > select Disable malware scanning > Apply button
2. Configuration tab > Content Analysis > Service Groups > select proxyav service-group and Delete > Apply button
   • If proxyav service-group is Deleted, confirm if AV Server under Malware Scanning is also removed.
3. Configuration tab > Content Analysis > ICAP > ICAP Services tab > select proxyav1 and Delete > Apply button

If the above does not work, open up a SysInfo and search through it for the name of the ICAP Server (proxyav1). This will show where else the object is referenced. If the object is not referenced by any policy, then the ProxySG has this object stuck in memory. The only solution for this is to reboot the proxy and attempt the above again.