Issue:
Any currently existing scheduled task that is using a delivery method, and is right clicked upon while selecting "Properties" receives an error indicating the delivery methods are deleted. However when reviewing the delivery methods themselves they do exist.
* The same error is re-created when creating a new task with a delivery method. But the customer can create a new task without issue if it does not use a delivery method.
Example Error:
Exception has been thrown by the target of an invocation.
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> LANDesk.ManagementSuite.SoftwareDistribution.Business.DeliveryMethodNotFoundException: This delivery method has been deleted.
at LANDesk.ManagementSuite.SoftwareDistribution.Business.DeliveryMethod. (String , Int32 )
at LANDesk.ManagementSuite.SoftwareDistribution.Business.DefaultDeliveryMethod.get_DefaultDM()
at LANDesk.ManagementSuite.SoftwareDistribution.WinUI.Controls.DeliveryMethodsControl.Initialize()
at LANDesk.ManagementSuite.SoftwareDistribution.WinUI.Controls.DeliveryMethodsControl..ctor()
at LANDesk.ManagementSuite.SoftwareDistribution.WinUI.TaskScheduler.ScheduledTaskFolder.DeliveryMethods.InitializeComponent()
at LANDesk.ManagementSuite.SoftwareDistribution.WinUI.TaskScheduler.ScheduledTaskFolder.DeliveryMethods..ctor()
--- End of inner exception stack trace ---
at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor, Boolean& bNeedSecurityCheck)
at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean fillCache)
at System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean skipVisibilityChecks, Boolean fillCache)
at System.Activator.CreateInstance(Type type, Boolean nonPublic)
at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
at System.Reflection.Assembly.CreateInstance(String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
at LANDesk.ManagementSuite.ldPropertySheet.ldPropertySheetCtrl.loadPanelObject(String classPath, Assembly currentAssembly)
at LANDesk.ManagementSuite.ldPropertySheet.ldPropertySheetCtrl.ParseXML(IEnumerable psList, TreeNode parent, Assembly currentAssembly, String assemblyName, Hashtable hshTab)
at LANDesk.ManagementSuite.ldPropertySheet.ldPropertySheetCtrl.LoadXMLFile(String sourceFile)
at LANDesk.ManagementSuite.ldPropertySheet.ldPropertySheetDialog.LoadXMLFile(String file)
at LANDesk.ManagementSuite.SoftwareDistribution.WinUI.TaskScheduler.ScheduledTaskPanelManager..ctor(TaskNode taskNode, String xmlFileName)
at LANDesk.ManagementSuite.SoftwareDistribution.WinUI.TaskScheduler.TaskNode.OnProperties()
Resolution:
Manually update the value on the SWD_DefaultDeliveryMethodSettings key in the dbo.KeyValue table of the associated database to represent that of an existing Delivery Method. The issue is caused when the default method (*In this case the SWD_DefaultDeliveryMethodSettings key) had been deleted.