Internal Error during Cube Processing

Hi,

for almost 3 Months my cubes got processed without errors.

Since last night, I get an error saying that (freely translated from german):

"Internal error: Unexpected error (File 'pffilestore.cpp', Row 3311, PFFileStore::HandleDataPageFault-Function)"

Nothing else.

Google has nothing to say to that.

Anybody gaining the same error or even a hint?

Thanks.

Are you running out of disk space by any chance?|||

Hi,

monitored this already. No Problem, more than 0.5TB left on HD space.

Thanks.

|||

I am also receiving the 3311 Internal Error message when trying to process my cube.

Cube processing was working fine for months, then at the end of April / beginning of May I started getting the following Internal Error: file 'pffilestore.cpp', line 3267, function 'PFFileStore::HandleDataPageFault'

I installed SQL Server 2005 SP2 this week, and now I am getting the file 'pffilestore.cpp', line 3311, function 'PFFileStore::HandleDataPageFault' error.

In the processing options, I am specifying to "ConvertToUnknown" and "Ignore Errors".

Any help or suggestions are appreciated. Thanks.

|||

You will need to contact Microsoft support (tech support # 1-888-677-9444) to get the hotfix to either bring you to build 2223 if you are using SQL 2005 SP1 or build 3166 if you are using SQL 2005 SP2. If this hotfix does not resolve your issue, because it did not fix the issue for my MDX query that I was running, there is still an open bug SQL BU Defect Tracking #524029.

Here is a link to the knowledge base article for your issue (possibly): http://support.microsoft.com/default.aspx/kb/932610?sd=dell

You might be encountering the open bug though.

|||

I got the same thing today and searched msdn.

MS released 3157 build and it is fixed in that build.

http://support.microsoft.com/kb/936305/en-us .

You can find 932610.

James B. Lim

sql

Intermittent field display

This is either a bug, or I am crazy.

I have developed a report that pulls its data from an SSAS cube. The report is grouped on Fields!FacilityName. On each "page" of the report, I have information for the displayed facility.

At the top of each page in my report I have a textbox whose value is =Fields!FacilityName. Further down on the report I have another text box whose value is set exactly the same. When I preview the report, I always have a value in the upper box, but only sometimes have a value in the lower box. If I change the value in the lower box to just a text string, it will always display, but when I put in the actual field reference it does not. It always doesn't display for the same facility names. Remember, the upper textbox on the form always displays 100% of the time.

I have a Dundas chart in the middle of the page on the report between these textboxes, but another field that pulls parameters and even a matrix all render correctly below that chart.

They both have the same parent according to the properties. I have even copied and pasted the working textbox further down the screen, with no improvement. When I changed the value of the textbox to "=cstr(len(Fields!FacilityName))", on the pages when it wants to be blank, it reads 0, and on other pages it shows a larger number. But the other textbox on the screen will always properly show the FacilityName.

I have also tried changing the name of the textbox, settings output to YES instead of Auto. If I slide the non-working textbox up to the top of the page and the working textbox down to the bottom area of the page, the bevavior switches.

Does anybody know of rendering issues with textboxes showing the same infomation?

Are you running at least SSRS2005 SP1 (on the server and for BI Dev.Studio)?

-- Robert

|||My server is running Microsoft SQL Server Reporting Services Version 9.00.2047.00, and I am using VS 2005 with the most recent service pack on my development PC. Both exibit the behavior I describe.
Could it be something odd in the XML of the report that I just cannot see in the IDE?
|||We are running 9.00.2047.00 on the server, and my VS 2005 is up to date. Maybe there is something buried in the XML of the RDL that I just cannot see in the IDE that is causing the problem.|||I also have a ticket in with Dundas since when I remove the chart off the report, the textbox renders correctly. Perhaps the chart is breaking the recordset in some way.