Using HPC Pack 2016 (v5.1.6124) SubmitJob to 2008R2 Headnode fails RRS feed

  • Question

  • Hello,

    When using HPC Pack 5.1.6124 to submit a job to a 2008R2 headnode I get the error copied below. The code is working when submitting jobs to headnodes with versions 2012, 2012R2 or 2016 . The error seems to suggest that the first parameter to SubmitJob should be ISchedulerStore whereas it is documented as ISchedulerJob. When using 2012R2 client utilities the code would successfully submit to 2008R2 headnodes.

    Have I missed something obvious?

    Kind regards,


      Message=Object of type 'Microsoft.Hpc.Scheduler.Properties.StoreProperty[][]' cannot be converted to type 'Microsoft.Hpc.Scheduler.Properties.StoreProperty[]'.
       at Microsoft.Hpc.Scheduler.Store.StoreServer.HandleException(Exception e, Boolean asyncReconnect)
       at Microsoft.Hpc.Scheduler.Store.StoreServer.Task_AddTasksToJob(Int32 jobId, List`1& taskIdList, List`1 taskPropsList)
       at Microsoft.Hpc.Scheduler.Store.JobEx.CreateTasks(List`1 taskPropertyList)
       at Microsoft.Hpc.Scheduler.SchedulerJob.CreateAddedTasks(Int32 rootGrpId, Dictionary`2 taskGroupIdMapping)
       at Microsoft.Hpc.Scheduler.SchedulerJob.CreateJob()
       at Microsoft.Hpc.Scheduler.SchedulerJob.Submit(ISchedulerStore store, String username, String password)

    Thursday, July 26, 2018 3:01 PM

All replies

  • Hi Liam,

      HPC Pack 2008 R2 is out of mainstream support, thus for the new SDK to support HPC Pack 2008 R2 is not in our scope. Could you tell us why you still need to support HPC Pack 2008 R2?

      At this stage, if you application still need to work with a few HPC pack 2008 R2 Cluster, you could stick to SDK of HPC Pack 2012 R2 which shall work with the 4 versions of Cluster (2008 R2, 2012, 2012 R2, 2016 Update 1)

      If you have strong requirement on 2016 SDK to support 2008 R2, please share us through hpcpack@microsoft.com, we can have an evaluation.

    Qiufang Shi

    Friday, July 27, 2018 3:16 AM
  • Hello Qiufang Shi,

    Thank you for such a quick response. We just try to match the Microsoft support, including the extended support. So if our clients are still using 2008R2 we want to allow them to continue doing so. By default it makes sense for us to use the latest SDK however from your message I understand that we have to use 2012R2 if we want to support 2008R2.

    I don't have a strong use case for 2016 SDK to support 2008R2 as long as 2012R2 remains compatible with future versions of HPC until support for 2008R2 ends.

    Thanks again for your help.

    Kind regards,


    Friday, July 27, 2018 9:13 AM
  • Thanks for your understanding. Let us know if you have any issues.

    Qiufang Shi

    Monday, July 30, 2018 3:30 AM