Discovery error "Could not redirect to Discovery status." - Support and Troubleshooting

Discovery error "Could not redirect to Discovery status." Issue Discovery error "Could not redirect to Discovery status."

Release All currently supported environments.

Cause UI Page discover_now calls DiscoveryAjax.discoverNow() and passes the discovery_schedule sys_id. DiscoveryAjax.discoverNow() should return a sys_id. If a sys_id is not returned, the message "Could not redirect to Discovery status" is displayed. DiscoveryAjax.discoverNow() calls script include Discovery.discoverNow(). If there is an error, whatever the error, the message is the same. Therefore, there could be different root causes to this error.

Resolution Get the root cause The first step in troubleshooting this error should be to get the correct root cause. For that:

Update function "discoverNow()" from script include "Discovery". Add a try/catch statement, as an example, the function would look like: discoverNow: function(scheduleGr) { try{ if (!this.isValidDiscoverySchedule(scheduleGr)) return "";

// trigger this discovery... var jobSysId = SncTriggerSynchronizer.executeNow(scheduleGr);

// Get the scheduler created discovery status, and update it with proper discover now description and source var status = new GlideRecord('discovery_status'); status.addQuery('scheduler_job', jobSysId); var timeoutSeconds = gs.getProperty('glide.discovery.discover_now_timeout', 10); // Searches for max of timeoutSeconds seconds. for (var attempts = 0; attempts status.query(); if (status.hasNext()) break; gs.sleep(250); } if (!status.next()) return null; status.setValue('description', 'Discover Now'); status.setValue('source', 'Discover_now_schedule'); status.update(); var datacenterType = new CloudResourceDiscoveryUtil().fetchDatacenterTypeFromSchedule(scheduleGr.getUniqueValue()); var usePatternDiscovery = gs.getProperty('sn_cmp.use_pattern_discovery.' + datacenterType, 'true'); if (usePatternDiscovery.equals('true') && !(datacenterType.equals('cmdb_ci_vcenter_datacenter'))) this._persistStatusToLDCs(status);

return status.sys_id; } catch (e){ gs.log(e); return null; } Reproduce the error. Review syslog for the error logged. Check if discovery_status was created The issue could be a timeout if the discovery_status was created, even though the error was returned. If that is the case:

Try increasing the value of system property glide.discovery.discover_now_timeout to 30. Error: invalid table name: cmp_discovery_ldc_config This error indicates that the "Cloud Management Platform application" plugin is not installed.

Create a case with support for the next steps to see if proper plugins can be installed/reinstalled to resolve the issue. Scripts not OOB Some scripts could have been updated and not out of box. Make sure following scripts are OOB:

/sys_script_include_list.do?sysparm_query=sys_idSTARTSWITHd22e7bdbc0a8016500a18e024bfc9aa3%5EORsys_idSTARTSWITHa6cdaf5bc0a802550004f460b6c04967%5EORsys_idSTARTSWITH092266f60ab30150007b0466d082578c%5EORsys_idSTARTSWITHd22e7bdbc0a8016500a18e024bfc9aa3%5EORsys_idSTARTSWITH092329440ab30150009e4c93176ef3d0%5EORsys_idSTARTSWITH6ae945a90b682300f198812f15673ab9