Select the product you need help with
FIX: "An unexpected error occurred" error in the PFMemoryHolder::RegisterMemoryHolder function when you run an MDX query in SQL Server 2012Article ID: 2699163 - View products that this article applies to. 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. On This PageSymptomsWhen you run a Multidimensional Expressions (MDX) query in an instance of Microsoft SQL Server 2012 Analysis Services (SSAS 2012), the query might fail, and you receive the following error message: Internal error: An unexpected error occurred (file 'pfiallocator.cpp', line 804, function 'PFMemoryHolder::RegisterMemoryHolder'). Execution complete Notes
CauseThis issue occurs because the SSAS 2012 Storage Engine tries to read a .det file that contains the metadata for the database when you run the query. However, because a path in the metadata is NULL, this causes the issue that is described in the "Symptoms" section. ResolutionCumulative update informationSQL Server 2012The fix for this issue was first released in Cumulative Update 2 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:2703275 Note 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:
(http://support.microsoft.com/kb/2703275/
)
Cumulative update package 2 for SQL Server 20122692828
(http://support.microsoft.com/kb/2692828/
)
The SQL Server 2012 builds that were released after SQL Server 2012 was releasedWorkaroundTo work around this issue, change the MDX query to not use an arbitrary shape set. StatusMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. PropertiesArticle ID: 2699163 - Last Review: November 22, 2012 - Revision: 2.2 Applies to
|


Back to the top








