Skip to main content

AdvancedSchedule generates error when using monthDays for new schedule

If I want to deploy a monthly schedule on for example the last day of the month I encounter an error message when I used the REST API or the ARM template.

The body of the REST API for creating schedules I used look likes this:

{
  "name": "demoSchedule",
  "properties": {
    "startTime": "2022-05-07T22:00:00+02:00",
    "interval": 1,
    "frequency": "Month",
    "advancedSchedule": {
      "weekDays": [],
      "monthDays": [ -1 ],
      "monthlyOccurrences": []
    }
  }
}

When I execute this REST call I receive the following error message:

{
  "code": "BadRequest",
  "message": "Argument requestScheduleData with value Orchestrator.Schedules.DataAccess.Models.ScheduleAllData is not valid. Error message: The input    value is not valid for Monthly Schedule Type"
}

After spending a lot of time of trial & error I learned that when I update an existing schedule the action can be completed successfully. So if I first post the following body to the REST API the schedule will be created successfully.

{
  "name": "demoSchedule",
  "properties": {
    "startTime": "2022-05-07T22:00:00+02:00",
    "interval": 1,
    "frequency": "Week",
    "advancedSchedule": {
      "weekDays": [
        "Friday"
      ],
      "monthDays": [],
      "monthlyOccurrences": []
    }
  }
}

In the second step I will sent the body of the call that fails and the schedule will be updated successfully. I tested apiVersion 2015-10-31 and 2020-01-13-preview and both will fail if you want to create the new schedule with one call.

Comments

Popular posts from this blog

CS8357: The specified version string contains wildcards, which are not compatible with determinism.

Today I was busy with creating a WCF service solution in Visual Studio Enterprise 2017 (15.9.2). In this solution I use a few C# class libraries based on .NET 4.7.2. When I compiled the solution I got this error message: Error CS8357: The specified version string contains wildcards, which are not compatible with determinism. Either remove wildcards from the version string, or disable determinism for this compilation The error message is linking to my AssemblyInfo.cs file of the Class library projects. In all the projects of this solution I use the wildcard notation for generating build and revision numbers. // Version information for an assembly consists of the following four values: // // Major Version // Minor Version // Build Number // Revision // // You can specify all the values or you can default the Build and Revision Numbers // by using the '*' as shown below: // [assembly: AssemblyVersion("1.0.*")] [assembly: AssemblyVersion("1.0.

Fixing HTTP Error 401.2 unauthorized on local IIS

Sometimes the Windows Authentication got broken on IIS servers so you cannot log in locally on the server. In that case you get the dreadfully error message HTTP Error 401.2 - Unauthorized You are not authorized to view this page due to invalid authentication headers. To fix this issue you can repair the Windows Authentication feature with the following PowerShell commands: Remove-WindowsFeature Web-Windows-Auth Add-WindowsFeature Web-Windows-Auth

Azure DevOps YAML based CD pipeline with multiple artifacts

In my post called " Switch from Azure DevOps release pipeline to YAML based CI/CD pipeline " I explained how to implement a combined CI/CD pipeline based on YAML templates. Because most of the deployments in my daily work are consuming multiple artifacts I had to do some additional R&D to find a solution for those releases in Azure DevOps. Base structure In the first post about the transition to YAML CI/CD pipelines I introduced the base structure. The templates I want to reuse are added to the yaml-template folders in the root of my GIT repo. For the CD pipelines which lack a CI phase I introduce a new folder called yaml-releases which will contain the YAML files for releases which are based on multiple artifacts. The folder structure within my GIT repo is thus: yaml-releases releaseArea myMultipleArtifactsRelease azure-pipelines.yml cd-job.yml yaml-templates jobs ... templates ...