KNOWN ISSUE: CreateJobScheduleByName fails when trying to schedule a Deployment Solution job

Article:TECH28058  |  Created: 2007-03-28  |  Updated: 2007-04-02  |  Article URL
NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.
Article Type
Technical Solution


The function "CreateJobScheduleByName", using the C# development environment, fails when I passed the properly formed XML to schedule a job to run at a future date. The following error is displayed:

Creating the schedule by name...
An exception occoured
System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: There is no row at position 0. ---> Altiris.ASDK.ASDKException: There is no row at position 0.


ASDK 1.3
Notification Server 6.0 SP3
Deployment Solution 6.8


The cause is unclear at this moment but it would seem to be a problem with parsing the XML passed to the function.


It appears that the documentation showing how to correctly form the XML for the schedule is incorrect. The following type of syntax should be used:
 string stringXML =
 @"<ScheduleAttributes xmlns=''>
  <start_time>4/4/2007 5:24:21 PM</start_time>
 Console.WriteLine("Creating the schedule...");
 // Get the JobID.
 int[] jobID = jobManagement.GetJobIDs("DIR Command (Windows)");
 // The appropriate computer name should be substituted in <computerName>.
 string scheduleInfo = computerManagement.GetSchedulesByAttribute("<computerName>", 6);

With this approach, the parsing of the schedule seems to be correctly intact.
The documentation issues have been entered into the tracking system to get them changed for the next release of the ASDK.

NOTE: CreateJobSchedule must be used rather than CreateJobSchedulByName due to DS authentication issues (see KB 33965).

Supplemental Materials

ValueLB 58181
DescriptionLogged in Littlebuggy (Altiris - Lindon, Plymouth) database

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices