The fix also applies to Microsoft SQL Server 2014 Analysis Services (SSAS 2014).
Symptoms
Consider the following scenario:
-
You restart a server that is running Microsoft SQL Server 2012 Analysis Services (SSAS 2012) or SQL Server 2014 Analysis Services (SSAS 2014) and then load a database by using DISCOVER_XML_METADATA Rowset or Microsoft SQL Server Management Studio.
-
At the same time, you execute and commit another transaction. For example, you create an Analysis Services trace object.
In this scenario, the database load is canceled, and you receive the following error message in the trace:
The operation was cancelled because of locking conflicts. An error occurred when loading the Kit. An error occurred when loading the Model. The operation was cancelled because of locking conflicts.
An error occurred when loading VertiPaq data for the table '' in the database 'database_name'. Database object is corrupt and cannot be queried. Delete this database from server, restore it from backup or create/process it. An error occurred when loading the Model.
Or, you may receive the following error message:
The table with Name of 'ReplReships' does not exist.
An error occurred when loading the Model.
(Microsoft.AnalysisServices)
Or, after SSAS starts, you do not see all the tabular model databases loaded into the server.
Resolution
This problem was first fixed in the following cumulative update for SQL Server:
Cumulative Update 1 for SQL Server 2014 /en-us/help/2931693
Cumulative Update 7 for SQL Server 2012 SP1 /en-us/help/2894115
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
See the terminology that Microsoft uses to describe software updates.
