Update set not possible to change state to Complete

[FotinaG]

Hello everyone,

Did anyone faced an issue to Complete update set? After plugin installations, I got an error "Error Message

Scan cannot proceed because required properties are not configured. Please set all mandatory properties before running the scan. Activate now"

When I go to "Activate now" fields are grey out and I amunable to active the Scan Engine properties after the proceeding via the documentation

My instance version is Yokohama.

I repaired few plugins which could cause it, but i didnt help, update sets are still not possible to complete.

Please let me know if anyone had similar experience.

Thank you in advance,

Tina

[Ankur Bawiskar · Accepted solution]

@FotinaG 

which plugin?

looks like something new in Yokohama is stopping this

check these links

Configure update set scanning properties 

Scan Engine 

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[Mardi · Accepted solution]

Hi Fotina , do you have the "Impact" app installed, if yes, this could be due to the "Best Practise Engine" being enabled as part of the Impact app which merged from Bravium labs which ServiceNow recently acquired. It looks as if its greyed out but try and see if you can add the check on the "Activate Scan Engine"

[Sandesh Powar]

Hey @FotinaG ,

This sounds like you've activated a security scanning plugin (likely Security Center or Vulnerability Response) that's now blocking your update set commits because the scan engine isn't properly configured.

Here's how to fix it:

Option 1: Configure the Scan Engine (Recommended)

1. Navigate to Vulnerability > Administration > Properties
2. Look for properties like:
   • Scanner IP/Hostname
   • Scanner credentials
   • Connection settings
3. If fields are greyed out, you might need the security_admin role
4. Once configured, try committing your update set again

Option 2: Disable the Validation (Quick Fix)

1. Go to System Policy > Events > Event Registry
2. Search for events related to "scan" or "vulnerability"
3. Temporarily deactivate the event that's triggering this validation
4. Commit your update set
5. Re-enable the event and configure properly later

Option 3: Check Business Rules

1. Navigate to System Definition > Business Rules
2. Filter for Active = true and search for "scan" or "vulnerability"
3. Look for any business rule that's blocking update set commits
4. Temporarily deactivate it, commit your update set, then reactivate

Pro Tip: Since this started after plugin installation, check which plugins you installed recently. You might need to roll back or properly configure them before proceeding.

If you're still stuck, let me know which specific plugins you installed and I can give you more targeted guidance.

---

Hope this helps! If this resolves your issue, please mark it as the accepted answer so others facing the same problem can find the solution quickly.

Best regards!
Sandesh

[Mardi · Accepted solution]

Hi Fotina , do you have the "Impact" app installed, if yes, this could be due to the "Best Practise Engine" being enabled as part of the Impact app which merged from Bravium labs which ServiceNow recently acquired. It looks as if its greyed out but try and see if you can add the check on the "Activate Scan Engine"

[FotinaG]

Hello Mardi, thank you for your reply.

After i checked the "Activate Scan Engine".It worked, I could complete US. But first I had to unlock grey out fields with script include:

gs.setProperty('glide.update_set.check_enforcement', 'false');

gs.setProperty('sn_update_set.validation.enabled', 'false');

Thank you and have a nice day!

[Steve29 · Accepted solution]

Hi

We have just encountered this exact same issue after upgrading the Impact plugin. The way we resolved it was to follow the Configuration of the plugin

i.e.
Add user to the Impact App Admin group
Enable 'Can Read' Application Access on the 'sys_update_version' table

However this alone will not make the Scan Engine Properties editable - they will remain read-only. To edit them the user seems to need to logout and reauthenticate for the permissions to take affect - only then will the properties page become editable.

We hope this helps anyone with the same issue

[FotinaG]

Hello, Thank you, @Steve29 Steve! And do you know how to switch off this error as it appears after Impact as well.Because we dont need short description for items