Showing posts with label ctp. Show all posts
Showing posts with label ctp. Show all posts

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.

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

Wednesday, March 21, 2012

permissions not 'sticking' with Yukon June CTP?

Hi,
I'm trying to assing permissions using the MS SQL Management studio on the
Yukon June CTP, but every time i assign permissions and press 'OK' and go
back to the permissions screen, it is gone. I am new to MSSQL -- do i need
to run a FLUSH PRIVELEGES or some equivalent command?
Thanks,
StephenStephen wrote:
> Hi,
> I'm trying to assing permissions using the MS SQL Management studio
> on the Yukon June CTP, but every time i assign permissions and press
> 'OK' and go back to the permissions screen, it is gone. I am new to
> MSSQL -- do i need to run a FLUSH PRIVELEGES or some equivalent
> command?
> Thanks,
> Stephen
Please post SQL Server 2005 issues in the 2005 newsgroups. These
newsgroups are currently for versions other than 2005.
http://www.microsoft.com/technet/community/newsgroups/server/sql.mspx
--
David Gugick
Quest Software
www.imceda.com
www.quest.comsql

permissions not 'sticking' with Yukon June CTP?

Hi,
I'm trying to assing permissions using the MS SQL Management studio on the
Yukon June CTP, but every time i assign permissions and press 'OK' and go
back to the permissions screen, it is gone. I am new to MSSQL -- do i need
to run a FLUSH PRIVELEGES or some equivalent command?
Thanks,
Stephen
Stephen wrote:
> Hi,
> I'm trying to assing permissions using the MS SQL Management studio
> on the Yukon June CTP, but every time i assign permissions and press
> 'OK' and go back to the permissions screen, it is gone. I am new to
> MSSQL -- do i need to run a FLUSH PRIVELEGES or some equivalent
> command?
> Thanks,
> Stephen
Please post SQL Server 2005 issues in the 2005 newsgroups. These
newsgroups are currently for versions other than 2005.
http://www.microsoft.com/technet/com...erver/sql.mspx
David Gugick
Quest Software
www.imceda.com
www.quest.com

permissions not 'sticking' with Yukon June CTP?

Hi,
I'm trying to assing permissions using the MS SQL Management studio on the
Yukon June CTP, but every time i assign permissions and press 'OK' and go
back to the permissions screen, it is gone. I am new to MSSQL -- do i need
to run a FLUSH PRIVELEGES or some equivalent command?
Thanks,
StephenStephen wrote:
> Hi,
> I'm trying to assing permissions using the MS SQL Management studio
> on the Yukon June CTP, but every time i assign permissions and press
> 'OK' and go back to the permissions screen, it is gone. I am new to
> MSSQL -- do i need to run a FLUSH PRIVELEGES or some equivalent
> command?
> Thanks,
> Stephen
Please post SQL Server 2005 issues in the 2005 newsgroups. These
newsgroups are currently for versions other than 2005.
http://www.microsoft.com/technet/co...server/sql.mspx
David Gugick
Quest Software
www.imceda.com
www.quest.com

Monday, March 12, 2012

Permissions error while upgrading to SP2 CTP...

Hi Folks,

I have a request from one of our researchers to upgrade to CTP SP2. I am getting the error message:

MSP Error: 29506 SQL Server Setup failed to modify security permissions on file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\ for user Administrator. To proceed, verify that the account and domain running SQL Server Setup exist, that the account running SQL Server Setup has administrator privileges, and that exists on the destination drive.

I added server\administrators - full control to the permissions of \Data\, but it still does not work.

Has anyone else ran into this, and how do I fix it?

Thanks,

Alainna

Error 29506. SQL Server Setup failed to modify security permissions on file E:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\ for user administrator.

The problem is that there exists a file in this Data directory that the user running SP1 does not have permissions to modify. The workaround is to figure out which file this is (typically a user created DB or some backup program files) and to temporarily assign permission to that file(s). You can revert back to the intended permissions after running SP1.

Thanks,
Sam Lester (MSFT)

|||Sam,

Thank you, that worked. I have no idea why I didn't check the files before posting, but thank you!

- Alainna