Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.


Symptoms

Database synchronization fails to create a view that has a dependency on another view that does not exist in the database. This can happen when the dependency between the two views is created using static code rather than metadata. The database synchronization does not know the dependency exists, so it cannot sync the two views in the incorrect order. If the view with the dependency is synced first, you will see the following error message:
"System.InvalidOperationException: Database execution failed: Invalid object name ''." This is because the dependent view does not exist in the database yet.

↑ Back to the top


Resolution

The changes in the hotfix make sure this issue is resolved within the database synchronization module. If the error message listed in the title is encountered, the view that fails to sync will be added to a list of views to retry synchronizing later. The database synchronization module will continue to sync all other views. When the view that fails originally is re-synchronized, the view that it is dependent on will now exist in the database. The view that fails previously will now be added successfully.

↑ Back to the top


More information

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained here in is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

↑ Back to the top


Article Info
Article ID : 4132560
Revision : 1
Created on : 4/13/2018
Published on : 4/13/2018
Exists online : False
Views : 199