I suspect they are actually 2 different scenarios, but with regard to the code sample added by Andrew, this is because it can't figure out (in advance) what it is going to do with regards to default values (by default, data is treated as optional at the receiver). There are 3 ways of fixing this:
1: add an enum with value 0 (since 0 is always the CLI default value for zeros), for example
public enum SiteType
{
Error = 0,
...
2: tell it which value to use by default:
[ProtoMember(10), DefaultValue(SiteType.Partition)]
public SiteType Type { get; set; }
3: tell the engine that it really doesn't need to worry about it, i.e. that it is going to have a value:
[ProtoMember(10, IsRequired = true)]
public SiteType Type { get; set; }