ARTICLES

This is the error message text: "Error opening file". To resolve this problem, you should install
the Cumulative update package 3 for SQL Server 2005 service pack 2. You can download this update
at here:
http://support.microsoft.com/kb/939537/LN/

2. When you process the index for a partition in a cube, you receive the
error message: "Internal error: An unexpected error occurred (file '
pffilestore.cpp', line 3311, function 'PFFileStore::HandleDataPageFault')".

This problem occurs when the data is stored in a single 65-kilobyte segment of a single partition
and at least one measure that is stored in the single 65-kilobyte segment contains many digits
after the decimal point. To resolve this problem, you should install the Cumulative update
package 3 for SQL Server 2005 service pack 2. You can download this update at here:
http://support.microsoft.com/kb/939537/LN/

3. When you query data from a SQL Server 2005 Analysis Services database by
using the HTTP protocol, you may receive the "Xml Parsing failed" error.

This is SQL Server 2005 bug. This bug was fixed in SQL Server 2005 service pack 1. To resolve
this problem, install the latest SQL Server service pack.

4. When you run an MDX query against a semiadditive measure in SQL Server 2005
Analysis Services, the following error occurs: "An internal error has occurred".

This problem occurs when the "IsAggregable" attribute of the time dimension is set to False.
To work around this problem, you can set the "IsAggregable" attribute of the time dimension
to True. To resolve this problem, install the latest SQL Server service pack.

5. When you run an MDX query by using the ADOMD.NET data provider the following
error message may occur: "Input string was not in a correct format".

This problem occurs when you set the format setting in the Regional and Language Options of the
client computer to German. To work around this problem, you can set the format setting in the
Regional and Language Options of the client computer to English. To resolve this problem, you
should install the Cumulative update package 2 for SQL Server 2005 service pack 2. You can
download this update at here:
http://support.microsoft.com/kb/936305/LN/

6. When you run an MDX query in SQL Server 2005 Analysis Services, the following
error may occur: "Dimension attribute was not found".

This problem occurs when the MDX query requests a dimension property, the dimension property
is either an attribute or an intrinsic property and the MDX query returns a rowset. To resolve
this problem, install the latest SQL Server service pack.

7. When you run a MDX query that contains calculated members in SQL Server 2005
Analysis Services, you may receive the following error message: "Internal
error: An unexpected exception occured".

This is SQL Server 2005 bug. To resolve this problem, you should install the Cumulative update
package 5 for SQL Server 2005 service pack 2. You can download this update at here:
http://support.microsoft.com/kb/943656/LN/

8. You may receive the following error message: "File system error: The record ID
is incorrect. Physical file: Logical file:" when you run an MDX query that uses
the TopCount function.

This is SQL Server 2005 bug. To resolve this problem, you should install the Cumulative update
package 7 for SQL Server 2005 service pack 2. You can download this update at here:
http://support.microsoft.com/kb/949095/LN/

9. You may receive the following error message: "System.OutOfMemoryException" when
you try to connect to SQL Server 2005 Analysis Services from Object Explorer.

This problem occurs when the database on the server that is running SQL Server 2005 Analysis
Services has many cubes, partitions, aggregations, or dimensions. This bug was fixed in SQL
Server 2005 service pack 2. To resolve this problem, install the latest SQL Server service pack.

10. The error occurs when you process a cube that has a relationship between
two tables in a data source view that contains more than four keys in
SQL Server 2005 Analysis Services.

This is SQL Server 2005 bug. This bug was fixed in SQL Server 2005 service pack 2. To work
around this problem, you should use less than four keys in a relationship in a Data Source
View. To resolve this problem, install the latest SQL Server service pack.

11. When you try to synchronize a database again in SQL Server 2005 Analysis
     Services, you may receive the following error message: "Processing for the
      database will be disabled because an error occurred while loading the
     '<DatabaseName>' database cryptography key".

This problem occurs when SQL Server not detect any changes between the source server and the
target server. To work around this problem, you can delete the database on the target server
and then synchronize the database to the target server again. To resolve this problem, you should
install the Cumulative update package 9 for SQL Server 2005 service pack 2. You can download
this update at here:
http://support.microsoft.com/kb/953752/LN/

12. The Analysis Services service may stop unexpectedly and Event ID 22 is logged
in the Application log when you process an object in a database.

This problem occurs when Analysis Services service tries to delete a file during the final phase
of the processing operation but this file is locked by other application, for example, antivirus
software or backup software. To work around this problem, avoid run any antivirus or backup
software during process an object in a database.

13. When proactive caching is enabled in SQL Server 2005 Analysis Services,
the many query notifications are sent to the data warehouse and during
this period, you cannot connect to the service.

This is SQL Server 2005 bug. This bug was fixed in SQL Server 2005 service pack 2. To work
around this problem, you can set a different refresh interval for each partition. To resolve
this problem, install the latest SQL Server service pack.

14. When you query a dimension that contains a parent/child hierarchy some
cells return the NULL value instead of returning the actual value.

This is SQL Server 2005 bug. This bug was fixed in SQL Server 2005 service pack 2. To resolve
this problem, install the latest SQL Server service pack.