Friday, March 30, 2012

pfpagealloc error

I am running Sql Server 2005 SP 2 CTP and keep getting an error which says Internal Error pfpagealloc.cpp file is corrupt. This did not happen with SP1 and is very speradic. I get the problem when using both excel and the visual studio browser to manipulate an anylsis services database. I can then try again and everything works. I also get the same problem sometimes with my overnight rebuild of the cube.

Paul

Please, please. If you can catch the repro schenario, create a report with http://connect.microsoft.com/sql.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

We just applied SP 2 CTP and we are periodically getting the same error.

However, if we run the same MDX query immediately, we do not encounter it again. We can then run many other MDX queries without incident, but eventually we will generate the error again.

Error message is below:

Executing the query ...

Internal error: An unexpected error occurred (file 'pfpagealloc.cpp', line 428, function 'PFPageAllocator::PFPageAllocator').

Internal error: An unexpected error occurred (file 'pfpagealloc.cpp', line 428, function 'PFPageAllocator::PFPageAllocator').

Internal error: An unexpected error occurred (file 'pfpagealloc.cpp', line 428, function 'PFPageAllocator::PFPageAllocator').

Internal error: An unexpected error occurred (file 'pfpagealloc.cpp', line 428, function 'PFPageAllocator::PFPageAllocator').

Internal error: An unexpected error occurred (file 'pfpagealloc.cpp', line 428, function 'PFPageAllocator::PFPageAllocator').

Execution complete

|||

Please report this with http://connect.microsoft.com/sql.

This looks like a memory pressure problem. See if you get enoght memory for Analysis Server.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

This is exactly the issue I was getting and I did try to log my problem with connect. Unfortunately they obviously needed log files to be able to trace the problem and as unfortunately the system was live I had to go back to sp1.

Please let me know if you have any luck with a resolution I will contine to check on connect site.

sql

No comments:

Post a Comment