Can't start SQLServerAgent

All of sudden, getting a Dr. Waston error with illegal
instruction on boot up.
If I tried to start it from the Services menu, get "Could
not start the SQLServerAgent service on \\server_name
Error 1067: The process terminated unexpectedly"
Do I need to reload the software... I have not found any
help in the Knowledge baseTake a closer look at the Dr Watson log to see if the SQLAgent service is
generating the Dr Watson error.
Stop any unnessary services on the machine. Leave the following running:
- Alerter
- Computer Browser
- Event Log
- License Logging Service
- Messenger
- Net Logon
- NTLM Security Support Provider
- Network Connectors
- Plug and Play
- Remote Procedure Call (RPC) Locator
- Remote Procedure Call (RPC) Service
- Server
- Spooler
- TCP/IP NetBIOS Helper
- Time Service
- Workstation
Review the NT application & System logs for hardware failure errors.
Test to see if you can start SQL Server from a command prompt.
If the problem persists and you're on the latest service pack, sp3, then
you should open up a support case.
If the Dr Watson is being caused by a bug in our product you will not be
charged for the incident.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Can't start SQLServerAgent

All of sudden, getting a Dr. Waston error with illegal
instruction on boot up.
If I tried to start it from the Services menu, get "Could
not start the SQLServerAgent service on \\server_name
Error 1067: The process terminated unexpectedly"
Do I need to reload the software... I have not found any
help in the Knowledge base| All of sudden, getting a Dr. Waston error with illegal
| instruction on boot up.
|
| If I tried to start it from the Services menu, get "Could
| not start the SQLServerAgent service on \\server_name
| Error 1067: The process terminated unexpectedly"
|
| Do I need to reload the software... I have not found any
| help in the Knowledge base
--
Folks,
If you can't find references of a SQL exception, please log a case with
Microsoft product support. There is a chance that this a bug so the case
shouldn't cost you.
Hope this helps,
--
Eric Cárdenas
SQL Server support|||Eric,
Thanks for the response... How do I log a case with
Microsoft product support?|||| Eric,
|
| Thanks for the response... How do I log a case with
| Microsoft product support?
|
--
Go to http://support.microsoft.com to get the contact number of Microsoft
product support for your country of residence.
Hope this helps,
--
Eric Cárdenas
SQL Server support

cant see more than 3gb mem

We are running SQL server 2000 on Windows 2003 on a Compaq MLxxx. I
have /pae and /3gb switch in the boot.ini and 'awe enabled' in sql
server. However the target server memorry is only 2725808 and sql
server goes to a max to 2.7 GB. I have played with the 'max memory'
parameter but it dosent help. Any idea what am I missing ?How much physical memory is on the machine?
Rand
This posting is provided "as is" with no warranties and confers no rights.|||I have 8GB of RAM. Here is the output of @.@.version
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: )
>--Original Message--
>How much physical memory is on the machine?
>Rand
>This posting is provided "as is" with no warranties and
confers no rights.
>.
>|||The problem was the service account didnt have previlage "
lock pages in memory "
Details http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/adminsql/ad_1_server_1fnd.asp
>--Original Message--
>I have 8GB of RAM. Here is the output of @.@.version
>Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Enterprise Edition on Windows NT 5.2 (Build 3790: )
>>--Original Message--
>>How much physical memory is on the machine?
>>Rand
>>This posting is provided "as is" with no warranties and
>confers no rights.
>>.
>.
>

cant see more than 3gb mem

We are running SQL server 2000 on Windows 2003 on a Compaq MLxxx. I
have /pae and /3gb switch in the boot.ini and 'awe enabled' in sql
server. However the target server memorry is only 2725808 and sql
server goes to a max to 2.7 GB. I have played with the 'max memory'
parameter but it dosent help. Any idea what am I missing ?How much physical memory is on the machine?
Rand
This posting is provided "as is" with no warranties and confers no rights.|||I have 8GB of RAM. Here is the output of @.@.version
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: )

>--Original Message--
>How much physical memory is on the machine?
>Rand
>This posting is provided "as is" with no warranties and
confers no rights.
>.
>|||The problem was the service account didnt have previlage "
lock pages in memory "
Details http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/adminsql/ad_1_server_1fnd.asp

>--Original Message--
>I have 8GB of RAM. Here is the output of @.@.version
>Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Enterprise Edition on Windows NT 5.2 (Build 3790: )
>
>confers no rights.
>.
>sql

Can't get SQL Server 2000 to use more than 2GB of RAM

Hi,

I have configured my SQL Server to use AWE and the /3GB switch in the boot.ini. Also the SQLService account has the "lock pages in memory" user rights. Yet SQL Server and Windows together do not want to utilize more than 2GB of memory, while 4GB is available. Some details below:

4 GB memory (2 GB available)
Windows 2000 Server Enterprise (SP3)
SQL Server 2000 Enterprise (SP4)

In the SQL Server log I can read "Address Windowing Extensions enabled" and "Warning: unable to allocate 'min server memory' of 2560MB"

Does anyone know what I am missing here? Thanks in advance.

Erik.

Hi Erik,

To my knowledge if you only have 4GB of memory or less you should only put in the /3GB switch and not turn AWE on. Maybe try turning AWE off.

Also, what is are the minimum and maximum memory settings on your server? You can view this in Enterprise Manager by right clicking on the server, selecting "Properties" and then viewing the "Memory" tab in the window that appears (sorry if you already knew that).

Also, is the server configured to dynamically manage memory or did you set it so that a fixed memory size is used?

Hope that helps a little bit or sheds a little light on things for future investigation, but sorry if it didn't.
|||Could you post the results of DBCC MEMORYSTATUS ?|||

Eric C. wrote:

Could you post the results of DBCC MEMORYSTATUS ?

Buffer Distribution Buffers
--
Stolen 8500
Free 1353
Procedures 13625
Inram 32521
Dirty 1085
Kept 0
I/O 1
Latched 376
Other 141211

Buffer Counts Buffers
--
Commited 198672
Target 198672
Hashed 175197
InternalReservation 448
ExternalReservation 14006
Min Free 1016
Visible 198672

Procedure Cache Value
--
TotalProcs 1638
TotalPages 13625
InUsePages 8525

Dynamic Memory Manager Buffers
--
Stolen 16978
OS Reserved 1096
OS Committed 1074
OS In Use 1054
General 3094
QueryPlan 13983
Optimizer 0
Utilities 18
Connection 686

Global Memory Objects Buffers
--
Resource 1307
Locks 147
XDES 64
SQLCache 172
Replication 2
LockBytes 2
ServerGlobal 24

Query Memory Objects Value
--
Grants 9
Waiting 0
Available (Buffers) 74325
Maximum (Buffers) 93475

Optimization Queue Value
--
Optimizing 0
Waiting 0
Available 32
Maximum 32

|||I don't think you need AWE unless you're accessing over 4GB of memory. Also you may want to check your virtual memory settings in Windows 2000 Server. If it is dynamically allocating Virtual Memory, do a defrag to see if more than one block of Unmovable bytes exists. If you have fragmented Virtual Memory space, it can cause strange memory errors. If you see fragmentation, try changing the setting to a fixed amount so that it will recreate the VM space in a single block.|||

This was a bug in SP4. Go to http://www.microsoft.com/downloads/details.aspx?FamilyID=7C407047-3F1F-48B8-9E4C-DC32875E1961&displaylang=en

|||

You can use AWE if the amount of physical memory on the machine exceeds the amount of virtual memory. On 32 bit systems there is 2GB of private address space. Since 4GB > 2GB you can enable AWE and set max server memory up to 3.5 GB, depending on the other applications and requirements on the system.

Eric is correct, you need to download the update to sql sp4 at the link provided.