Dynamics CRM 2015 On-Prem求助：回滚更新后无法修改记录所有者
Based on your issue description—being unable to modify record owners (even for new entities) where the owner reverts to the original user after saving, following an update 0.3 rollback with no new custom scripts/workflows/plugins added—here’s a targeted troubleshooting plan to resolve this:
Key Context
Since the problem started right after rolling back an update, the root cause is almost certainly tied to an incomplete rollback, system permission inconsistencies, or underlying system component disruption caused during the rollback process.
Step-by-Step Troubleshooting
1. Test with a System Administrator Account
First, rule out user-specific permission issues:
- Try assigning an owner using a system administrator account.
- If the admin can successfully complete the assignment, check that affected users have the Assign permission enabled for target entities in their security roles. Also confirm the intended owner has read/edit permissions for those entities.
- If the admin also faces the same issue, this confirms a system-wide problem, not user-level restrictions.
2. Dig into System Logs for Errors
Check critical logs to identify failure details:
- CRM Server Event Viewer: Navigate to Applications and Services Logs > Microsoft Dynamics CRM for error events linked to assignment operations, database access, or native plugin execution.
- CRM Plugin Trace Log: Even without custom plugins, system-native plugins handle owner assignment. Enable tracing via Settings > Administration > System Settings > Customization tab, attempt an assignment, then look for exceptions like permission failures, database deadlocks, or forced rollbacks in the trace logs.
3. Validate Update Rollback Completeness
Rollbacks can leave the system in an inconsistent state:
- Check the CRM update history (Settings > Administration > Updates) to confirm the update 0.3 rollback finished without warnings or partial failures.
- If the rollback had issues, consider reapplying update 0.3 (after taking a full system backup) and performing a fresh rollback.
- For advanced checks, compare core CRM database tables (e.g.,
PrincipalObjectAccess,SystemUser) against a backup taken before the initial update to spot inconsistencies.
4. Verify System-Level Owner Field Configuration
While you noted no customizations, the rollback might have altered system-wide field behavior:
- For a problematic entity, go to Settings > Customizations > Customize the System > Entities > [Entity] > Fields and check the Owner field. Ensure it’s not set to Read-Only at the system level.
- Since new entities are affected, rule out organization-wide assignment restrictions via Settings > Security > Security Policies (a rare edge case but worth confirming).
5. Check Database Integrity
Run integrity checks on your CRM database:
- On the SQL Server hosting your CRM organization database, execute the
DBCC CHECKDBcommand to rule out database corruption that could interfere with owner assignment transactions.
Fallback Option
If none of the above steps resolve the issue, restoring a full system backup taken before the update/rollback is a reliable last resort (assuming you have one available).
内容的提问来源于stack exchange，提问作者Joe
