Microsoft distributes Microsoft SQL Server 2012 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release.
Symptoms
Consider the following scenario. You use Analysis Management Objects (AMO) to connectto an instance of Microsoft SQL Server 2012 Analysis Services, and the client AMO library (Microsoft.AnalysisServices.dll) is provided from one of the following:
-
SQL Server 2008 R2
-
SQL Server 2008
-
SQL Server 2005
In this scenario, the connection fails. Additionally, you receive the following error message:
Exception Message: Deserialization failed: Requested value '<ServerEdition>' was not found. (type XmlSerializationException)Exception Stack Trace: at Microsoft.AnalysisServices.DesignXmlReader.ReadRoot(Type type)at Microsoft.AnalysisServices.DesignXmlReader.DeserializeComponent(IDesignerSerializationManager manager, XmlReader reader, Type root)at Microsoft.AnalysisServices.AnalysisServicesClient.Discover(IMajorObject obj, ObjectExpansion expansion)at Microsoft.AnalysisServices.Server.Refresh(IMajorObject obj, ObjectExpansion expansion)at Microsoft.AnalysisServices.Server.Connect(String connectionString, String sessionId)Inner Exception Details:Exception Message: Requested value '<ServerEdition>' was not found. (type ArgumentException)Exception Stack Trace: at System.Enum.TryParseEnum(Type enumType, String value, Boolean ignoreCase, EnumResult& parseResult)at System.Enum.Parse(Type enumType, String value, Boolean ignoreCase)at Microsoft.AnalysisServices.DesignXmlReader.ReadPrimitive(Type type, XmlAttributes attributes)at Microsoft.AnalysisServices.DesignXmlReader.ReadStructContent(Object obj, StructMapping mapping)at Microsoft.AnalysisServices.DesignXmlReader.ReadObjectContent(Object value, Type type, TypeMapping mapping)at Microsoft.AnalysisServices.DesignXmlReader.ReadRoot(Type type)
Note The placeholder <ServerEdition> in the error message represents one of the following requested values:
-
EnterpriseCore64
-
EnterpriseCore
-
BusinessIntelligence64
-
BusinessIntelligence
For more information about Analysis Services Server Edition enumeration, visit the following Microsoft Developer Network (MSDN) website:
General information about Analysis Services ServerEdition enumeration
Cause
This issue occurs because SQL Server 2012 returns a new version code. This behavior causes AMO that is provided from SQL Server 2008 R2, SQL Server 2008, or SQL Server 2005 cannot be recognized.Note Cumulative update package 1 changes the approach in how edition values are returned from the server to the client. When the client AMO library is provided from SQL Server 2008 R2, from SQL Server 2008, or from SQL Server 2005, the AMO client perceives the Analysis Services server editions for compatibility as shown in the following table.
|
Analysis Services server edition |
Compatibility |
|---|---|
|
EnterpriseCore64 |
Enterprise64 |
|
EnterpriseCore |
Enterprise |
|
BusinessIntelligence64 |
Enterprise64 |
|
BusinessIntelligence |
Enterprise |
Resolution
Cumulative update information
SQL Server 2012
The fix for this issue was first released in Cumulative Update 1 for SQL Server 2012. For more information about how to obtain this cumulative update package for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
2679368 Cumulative update package 1 for SQL Server 2012Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2692828 The SQL Server 2012 builds that were released after SQL Server 2012 was releasedNote Cumulative update package 1 is a server-side update for the msmdsrv.dll and the msmdlocal.dll SQL Server 2012 Analysis Services files. The client library does not have to be updated to reflect the update.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problemsFor more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 Naming schema for Microsoft SQL Server software update packagesFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
