I am deploying a brand new Custom Object and all associated Custom Fields from one Dev environment to another Dev environment. I'm receiving the "Invalid parameter value" error on one of my custom profiles during the validation for deployment.
I've read this StackExchange post suggesting that I need to create the Profile manually in my receiving org first (do my own clone) prior to validating/deploying: Invalid parameter type error while deploying custom profile
However, the profile in question already exists in the receiving org and the sending org.
I also know that Salesforce had a Known Issue regarding validate/deploy of profiles with "View All Data" settings, but this was resolved in Winter '16 based on their Known Issue: https://success.salesforce.com/issues_view?id=a1p30000000T4OvAAK
Due to the generic nature of the error, I am unsure exactly where to begin in debugging it farther. As I am deploying a brand new object, I don't really want to resort to excluding my profile from the ChangeSet and needing to go manually fix all profile CRUD and field level security in the receiving org.
It may be worth noting that the originating org is on Summer '16, and the receiving org has been upgraded to the Winter '17 preview.
Question: Does the difference in Salesforce releases between orgs have anything to do with this problem? Is there anything else that I can do (other than excluding my profile(s)) to resolve this problem without engaging Salesforce support?