Schedule Job Error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
7 hours ago
The schedule Job for the Salesforce integration is failing with a error "No match found" in samp-sw-publisher.How do we fix this error ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
6 hours ago
Hi @Devika
There is a OOB flow running at backend when scheduled job is running. Check your request payload , response or exact error over there (Flow context).
If you are unable to debug, involve Servicenow Support post raising a case (Hi ticket).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
6 hours ago
Hi @Devika
Issue
When running Software Asset Management reconciliation on all or any specific publisher, this will create the Reconciliation Result record (RRxxxxx) and may immediately show the status as Failed. System logs trace the errors as below:
SAM:ReconciliationEngine: undefined: no thrown error
Error: No Match found for a4dcccc20b3022002d6c650d37673ab7 in samp_sw_publisher
SAM:ReconciliationEngine: Error: No Match found for a4dcccc20b3022002d6c650d37673ab7 in samp_sw_publisher: no thrown error
Cause
Once running the reconciliation for all/specific publisher listed in the drop down of the publisher field, the reconciliation engine will look for that publisher in the table samp_sw_publisher. If the record does not exist on this table, then the ReconciliationEngine will throw the error and stop processing. The missing record may have been deleted or the scheduled job that pulls the data from the source content service may have failed.
Resolution
Option #1 if this issue is not occurring in any of your sub-prod instances:
- Access your unaffected sub-prod instance
- Go to samp_sw_publisher list view and look for the sys_id as in the error "SAM:ReconciliationEngine: Error: No Match found for a4dcccc20b3022002d6c650d37673ab7 in samp_sw_publisher"
- Export this record as XML using "Export XML" and download it.
- Logon your affected instance and import that XML using the "Import XML" UI Action.
Option #2:
- Contact ServiceNow Technical Support to inspect the weekly jobs being run to pull the source data from content services. If these are interrupted or failed, SAMP Software Content Library or related tables may be incomplete.
Best, Dennis
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
5 hours ago
Hello @dreinhardt
Do we have any alternate solution rather than reproducing this in unaffected instance .
How do we exactly check the issue with CDS schedule jobs ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
Hi @Devika , as mentioned by the KB - raise a case with SN support.
Option #2:
- Contact ServiceNow Technical Support to inspect the weekly jobs being run to pull the source data from content services. If these are interrupted or failed, SAMP Software Content Library or related tables may be incomplete.
