17122 :initdata: Warning: Could not set working set size to 519104 KB.

17122 :initdata: Warning: Could not set working set size to 519104 KB.

Post by Adam » Sat, 08 Jan 2000 04:00:00



Hi,

Every time I start sql server the event viewer I get the above message.

I think this means that it's trying to allocate 512 Megs or RAM but is
unable to.  Am I correct?

I have set SQL server to use 256 megs or RAM and to reserve physical memory
for it.

The BOL is really poor when it comes to covering details of error messages.
What use is it to repeat the text of the error message?  Tell my WHY it's
happening and what to do to fix it... not just the text of the message.

Any insight is appreciated.

 
 
 

17122 :initdata: Warning: Could not set working set size to 519104 KB.

Post by Neil Pik » Sun, 09 Jan 2000 04:00:00


Adam - 6.5 or 7.0?  Please post your sp_configure output.  Remember that in SQL
6.5 the memory value is NOT equal to 1MB...

Quote:> Every time I start sql server the event viewer I get the above message.

> I think this means that it's trying to allocate 512 Megs or RAM but is
> unable to.  Am I correct?

> I have set SQL server to use 256 megs or RAM and to reserve physical memory
> for it.

> The BOL is really poor when it comes to covering details of error messages.
> What use is it to repeat the text of the error message?  Tell my WHY it's
> happening and what to do to fix it... not just the text of the message.

> Any insight is appreciated.

 Neil Pike MVP/MCSE.  Protech Computing Ltd
 (Please reply only to newsgroups)
 SQL FAQ (406 entries) see

 or www.ntfaq.com/sql.html (+ ntfaq download)
 or http://www.sql-server.co.uk

 
 
 

17122 :initdata: Warning: Could not set working set size to 519104 KB.

Post by Adam » Sat, 22 Jan 2000 04:00:00


Hi Neil,

Sorry for the delay in my response. I've been fighting with this server for a while and then I keep getting pulled away to other issues.  Here is the contents of the sp_configure (also attached).  It is SQL 7.0 SP1.

name                                minimum     maximum     config_value run_value  
----------------------------------- ----------- ----------- ------------ -----------
affinity mask                       0           2147483647  0            0
allow updates                       0           1           0            0
cost threshold for parallelism      0           32767       5            5
cursor threshold                    -1          2147483647  -1           -1
default language                    0           9999        0            0
default sortorder id                0           255         52           52
extended memory size (MB)           0           2147483647  0            0
fill factor (%)                     0           100         0            0
index create memory (KB)            704         1600000     0            0
language in cache                   3           100         3            3
language neutral full-text          0           1           0            0
lightweight pooling                 0           1           0            0
locks                               5000        2147483647  0            0
max async IO                        1           255         32           32
max degree of parallelism           0           32          0            0
max server memory (MB)              4           2147483647  255          255
max text repl size (B)              0           2147483647  65536        65536
max worker threads                  10          1024        255          255
media retention                     0           365         0            0
min memory per query (KB)           512         2147483647  1024         1024
min server memory (MB)              0           2147483647  255          255
nested triggers                     0           1           1            1
network packet size (B)             512         65535       4096         4096
open objects                        0           2147483647  0            0
priority boost                      0           1           0            0
query governor cost limit           0           2147483647  0            0
query wait (s)                      -1          2147483647  -1           -1
recovery interval (min)             0           32767       0            0
remote access                       0           1           1            1
remote login timeout (s)            0           2147483647  5            5
remote proc trans                   0           1           0            0
remote query timeout (s)            0           2147483647  0            0
resource timeout (s)                5           2147483647  10           10
scan for startup procs              0           1           0            0
set working set size                0           1           1            1
show advanced options               0           1           1            1
spin counter                        1           2147483647  10000        10000
time slice (ms)                     50          1000        100          100
two digit year cutoff               1753        9999        2049         2049
Unicode comparison style            0           2147483647  196609       196609
Unicode locale id                   0           2147483647  1033         1033
user connections                    0           32767       64           64
user options                        0           4095        0            0

I'm not sure why it's trying to allocate 512 when I have it set to 255 (and 'reserve physical memory').

Thank you so much for any insight!

"Neil Pike" <100577....@compuserve.com> wrote in message news:VA.00003ad4.08b3f1ae@compuserve.com...
> Adam - 6.5 or 7.0?  Please post your sp_configure output.  Remember that in SQL
> 6.5 the memory value is NOT equal to 1MB...

> > Every time I start sql server the event viewer I get the above message.

> > I think this means that it's trying to allocate 512 Megs or RAM but is
> > unable to.  Am I correct?

> > I have set SQL server to use 256 megs or RAM and to reserve physical memory
> > for it.

> > The BOL is really poor when it comes to covering details of error messages.
> > What use is it to repeat the text of the error message?  Tell my WHY it's
> > happening and what to do to fix it... not just the text of the message.

> > Any insight is appreciated.

>  Neil Pike MVP/MCSE.  Protech Computing Ltd
>  (Please reply only to newsgroups)
>  SQL FAQ (406 entries) see
>  sqlfaq.zip in lib 7 (SQL Public) @ http://go.compuserve.com/sqlserver
>  or www.ntfaq.com/sql.html (+ ntfaq download)
>  or http://www.sql-server.co.uk

  sp_configure.txt
3K Download
 
 
 

17122 :initdata: Warning: Could not set working set size to 519104 KB.

Post by Neil Pik » Sun, 23 Jan 2000 04:00:00


Adam - looks fine to me.  Don't know why this is coming up.  Why not take the
working set option off?

 Neil Pike MVP/MCSE.  Protech Computing Ltd
 (Please reply only to newsgroups)
 SQL FAQ (412 entries) see

http://forumsb.compuserve.com/vlforums/UK/default.asp?SRV=MSDevApps
 or www.ntfaq.com/sql.html (+ ntfaq download)
 or http://www.sql-server.co.uk

 
 
 

17122 :initdata: Warning: Could not set working set size to 519104 KB.

Post by Adam » Fri, 28 Jan 2000 04:00:00


Yeah, I know.  Weird, eh?

I'll try that thanks...


> Adam - looks fine to me.  Don't know why this is coming up.  Why not take
the
> working set option off?

>  Neil Pike MVP/MCSE.  Protech Computing Ltd
>  (Please reply only to newsgroups)
>  SQL FAQ (412 entries) see

> http://forumsb.compuserve.com/vlforums/UK/default.asp?SRV=MSDevApps
>  or www.ntfaq.com/sql.html (+ ntfaq download)
>  or http://www.sql-server.co.uk

 
 
 

17122 :initdata: Warning: Could not set working set size to 519104 KB.

Post by Abdul Gil » Wed, 29 Mar 2000 04:00:00


What is the total physical RAM on the box?  Is it possible that the RAM
allocated to SQL Server is equal to or greater than the total RAM?

Abdul Gill

 
 
 

1. error 17122 : initdata: Warning: Could not set working set size to 519104 KB.

All,

I am receiving error 17122.  I am probably going to reconfigure the server
to dynamically allocate memory, but can somebody answer the following
question?  Why is SQL Server attempting to set the working set size to
519104KB, when the configuration is as follows (basically, fixed memory at
350MB)?

SQL Server 7.0 SP2
512MB

Set working set size = 1
Min Server Memory = 350MB
Max Server Memory = 350MB

I have searched everywhere, and I have check the SP3 fixlist, and have
failed to find an explanation.  Any help would be appreciated.

Thanks,
Gerard

2. Click event and ENTEr

3. Eventlog Mesg 17122 : initdata: Warning: Could not set working set size to 519104 KB

4. Unique Index

5. Error 17122 : initdata: Warning: Could not set working set size to 1038848 KB.

6. Help wanted optimising a query

7. initdata: Warning: Could not set working set size to 1038848 KB.

8. Self Paced SQL Tutorial

9. initdata error 17122 & PAGE_FAULT

10. SQL Error Could not set working set size to ... KB

11. Setting Working Set Size on SQL 7 under Windows 2000

12. UPDATE / Multiple SET not working - fields being set to NULL

13. Setting not Null field to ""(empty string) does not work with CRecordset