Unable to complete "In progress" update set post upgrade, error message was showing up

[Gayathri Adoni]

 

Hi Team,

Has anyone encountered similar issue of seeing the error message on update sets which is in progress. Attaching the screenshot for reference.

When tried to click on Activate now, it redirects to scan engine properties page, where activate scan engine field is read-only.

Any useful response would be helpful.

 

 

Regards,

G

[KanteS]

Hi ,

To resolve:

1. Go to System Definition > Tables and open sys_update_version
2. Under the Application Access tab , Enable Can read and Enable Allow access to this table from all application scopes
3. Save the record andNavigate back to Scan Engine Properties , Activate Scan Engine field should now editable without getting error.

If the issue still exists, additional checks include:

1. Verify required roles 
2. Check for custom ACL or cross-scope access restrictions
3. Repair the related Impact/Scan Engine plugin that might be issue after any clone or upgrade
4. Review System Logs for permission or plugin-related errors
5. Clear cache and re-login

If this helps, please give a like and mark it as a solution

Thank you

[Gayathri Adoni]

Hi I tried repair plugin, it did not work.

I can see below log, but what action should I take
rePublishPoliciesAfterUpgrade: Could not locate any upgrade history for plugin=com.glide.instance_scan

[21121A3359]

Hai 

Yes, this issue is usually related to Proactive Code Check / Scan Engine configuration rather than the Update Set itself.

The message:

Scan cannot proceed because required properties are not configured

typically appears when the Scan Engine plugin/features are enabled but mandatory scan properties are not properly initialized.

A few things you can check:

1. Verify whether the following plugins are active:

• Static Code Analyzer

• Proactive Code Checker

• Quality Clouds integration (if applicable)

1. Navigate to:

sys_properties.list

and search for scan/code-check related properties such as:

• sn_code_scan.*

• glide.code.*

• scan.engine.*

1. The “Activate scan engine” field becomes read-only when:

• The feature is controlled by plugin activation

• Required roles are missing

• Instance/license restrictions exist

• The scan engine is managed automatically in newer releases

1. Try checking:

System Diagnostics → Plugins

and confirm the related scan plugins are fully activated.

1. Sometimes this issue also occurs after upgrades/clones where scan properties are partially migrated.

2. If you do not intend to use Proactive Code Check, you can usually ignore the warning safely, as it does not block normal Update Set functionality.

3. Clearing cache and reloading the form may also help:

cache.do

If the issue persists, check system logs for:

• Property access errors

• Plugin activation issues

• Licensing warnings

If you find the exact missing property causing the scan initialization failure, please share it here — it would help others facing the same issue.

If this helps, please mark it as Helpful.

[Gayathri Adoni · Accepted solution]

Impact plugin (sn_impact_cust) also needs to be up to date along with scan engine plugin, once we update it, update set issue will be gone.

To modify scan engine propertie -- > sn_se.scan_engine_admin is required on the user to be able to amend the scan engine properties.