Wednesday, February 15, 2012

ERROR: SQLSERVERAGENT COULD NOT BE STARTED(ERROR CREATING A NEW SESSION)

I keep on getting this msg on a active/passive win2003 cluster environment
with SQL 2005
ERROR: SQLSERVERAGENT COULD NOT BE STARTED (ERROR CREATING A NEW SESSION)
(sqagtres) online thread: error 435 brining Resource online.
(sqagtres) online Thread: ResUtilsStartResouceService failed (status 435)
Thank you in avance
>>> On 12/4/2006 at 10:16 AM, in message
<esNUSh8FHHA.3616@.TK2MSFTNGP06.phx.gbl>, Peter<Vik> wrote:
> ERROR: SQLSERVERAGENT COULD NOT BE STARTED (ERROR CREATING A NEW
> SESSION)
> (sqagtres) online thread: error 435 brining Resource online.
> (sqagtres) online Thread: ResUtilsStartResouceService failed (status
> 435)
If you are using AWE, you need to give the agent user (in Windows) the
lock pages in memory permission.
|||Thank you for your quick response, but what's AWE and which lock pages?
"Joel Maslak" <jmasla@.state.wy.us> wrote in message
news:4573F823.BB84.007F.0@.state.wy.us...
> <esNUSh8FHHA.3616@.TK2MSFTNGP06.phx.gbl>, Peter<Vik> wrote:
> If you are using AWE, you need to give the agent user (in Windows) the
> lock pages in memory permission.
|||>>> On 12/4/2006 at 10:41 AM, in message
<OtdTgv8FHHA.3468@.TK2MSFTNGP04.phx.gbl>, Peter<Vik> wrote:
> Thank you for your quick response, but what's AWE and which lock
> pages?
You probably aren't using AWE if you don't know about it. You have to
provide /PAE as a boot command-line option, and it only applies to 32
bit OS, 32 bit SQL, and > 2GB of memory allocated to SQL.

No comments:

Post a Comment