Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Network Configuration Manager (NCM) > NCM job error: There was an error while trying to serialize parameter http://schemas.solarwinds.com/2013/Ncm:job

NCM job error: There was an error while trying to serialize parameter http://schemas.solarwinds.com/2013/Ncm:job

Updated February 15, 2017

Overview

When running an NCM job, the following error prompts: 

There was an error while trying to serialize parameter http://schemas.solarwinds.com/2013/Ncm:job. The InnerException message was 'Enum value '0' is invalid for type 'SolarWinds.NCM.Contracts.InformationService.NCMJobSchedule+eTriggerMonths' and cannot be serialized. Ensure that the necessary enum values are present and are marked with EnumMemberAttribute attribute if the type has DataContractAttribute attribute.'. Please see InnerException for more details. ---> System.ServiceModel.CommunicationException: There was an error while trying to serialize parameter http://schemas.solarwinds.com/2013/Ncm:job. The InnerException message was 'Enum value '0' is invalid for type 'SolarWinds.NCM.Contracts.InformationService.NCMJobSchedule+eTriggerMonths' and cannot be serialized

 

Environment

NCM version 7.6 RC, but may be present in other releases

 

Cause 

At this time it was reproduced by modifying an job schedule.

NCM Development took this procedure to reproduce the error:

1.    Edit Job (Database maintenance for example).
2.    Set job schedule to monthly and select .all months.
3.    Press Finish.
4.    Edit job again and set schedule to weekly, select several days of week.
5.    Press Finish.

This occurs when running the job after the error has been reproduced.

Resolution

At this time, the job needs to be recreated as a workaround. Development plans are to fix this in future releases.

 

 

Last modified

Tags

Classifications

Public