Re: AWE in SQL Cluster

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

In order for new Windows level security permissions to be active (such as the
lock pages in memory right) the account must log out and back in. As this is
a service account, the services simply need to be restarted.
--
Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration /
Microsoft Office SharePoint Server 2007: Configuration)
MCITP (dbadmin, dbdev)


"Cgal" wrote:

The Microsoft documentation said to add the security account but I did
actually add both the account and the security group before I got the error.

Do you think that I need to reboot to aleviate the error message?

"Geoff N. Hiten" <SQLCraftsman@xxxxxxxxx> wrote in message
news:eBNxIPQrHHA.1508@xxxxxxxxxxxxxxxxxxxxxxx
Don't grant the privilege to the account. Grant it to the domain group
you designated when you installed SQL.

--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP




"Cgal" <cgallelli@xxxxxxxxxxxxxxxxx> wrote in message
news:uREFgcPrHHA.4324@xxxxxxxxxxxxxxxxxxxxxxx
I have a two node cluster with SQL Server 2005 that I am having difficulty
getting AWE to work. I have granted the "lock pages in memory" right to
the domain account that the SQL Server service is running under on both
nodes and run the following commands to setup the AWE memory.

sp_configure 'awe enabled', 1
go
reconfigure with override
go
sp_configure 'max server memory','6144'
go
reconfigure with override
go

I get the following error message when these statements complete:

Msg 5845, Level 16, State 1, Line 1

Address Windowing Extensions (AWE) requires the 'lock pages in memory'
privilege which is not currently present in the access token of the
process.










.

Relevant Pages

  • Re: Script for User rights assignment
    ... > details of the security settings for an account ie log on as a ... lock pages in memory etc etc. ...
    (microsoft.public.windows.server.scripting)
  • Lock pages in memory
    ... We're have a process using AWE, hence requiring the priviledge to lock pages ... not just AWE allocated memory. ... My understanding is this just sets the security privilege, ...
    (microsoft.public.win32.programmer.kernel)
  • AWE in SQL Cluster
    ... I have a two node cluster with SQL Server 2005 that I am having difficulty ... and run the following commands to setup the AWE memory. ... Address Windowing Extensions requires the 'lock pages in memory' ...
    (microsoft.public.sqlserver.clustering)
  • Re: SQL 2005
    ... lock pages in memory is required for service account. ... If you want SQL Server to be able to address memory though AWE, ...
    (microsoft.public.sqlserver.setup)
  • Re: Cannot get AWE to work in SQL Server 2000 SP3
    ... AWE & Lock pages will reserve that memory so nothing other than SQL Server can touch it anyway. ...
    (microsoft.public.sqlserver.setup)