I have spend some time to figure out a little tricky problem caused by my syncscopeconfig: i had defined a column for sync which is not existent in the target database. This was a simple typo in the colum name. Unfortunatly SyncSvcUtil.exe did not complain
about it at all. Instead it silently ignored the problem. Cogegen for server and isclient and also provisioning worked without any problems. Only the misspelled column was not part of the generated scope entity.
Simplifed example:
<SyncTable Name="MyTable" IncludeAllColumns="false" FilterClause="....">
<SyncColumns>
<SyncColumn Name="NonExistentColum" IsNullable="false" SqlType="int" />