In the event viewer, I am getting an error "17122 : Initdata: Warning: Could
not set working size to 470281KB.
My sql is configured to have min = 128 and max RAM = 480281 in the server
properties
sheet(fixed memory configurarion).
What is SQL trying to set here and whjy?
Thanks
SalamElias,
I am afraid that I don't really know what is happening, but I see that 823
is a Windows I/O error. When it happens it usually is followed by another
error. One KB article on this is:
http://support.microsoft.com/default...b;en-us;274310
Do you have "set working set size" set to 1 instead of 0? If so, you should
have the min and max server memory set the same.
FWIW,
Russell Fields
"SalamElias" <eliassal@.online.nospam> wrote in message
news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> In the event viewer, I am getting an error "17122 : Initdata: Warning:
Could
> not set working size to 470281KB.
> My sql is configured to have min = 128 and max RAM = 480281 in the server
> properties
> sheet(fixed memory configurarion).
> What is SQL trying to set here and whjy?
> Thanks
|||I ran sp_Configure, Ihave the folowing figues :
sp_configure
max server memory (MB)42147483647470470
min server memory (MB)02147483647256256
set working set size0111
When I the server RAM proprty sheet, Dynamically configure SQL Server
memoery with the min and max values indicated above as well as the "Reserve
physical memory for SQL Server " is checked.
So what should I do to stilluse these min max values and not set them both
with the same value
Thanks
Do you mean that I should have min = max = 470
"Russell Fields" wrote:
> SalamElias,
> I am afraid that I don't really know what is happening, but I see that 823
> is a Windows I/O error. When it happens it usually is followed by another
> error. One KB article on this is:
> http://support.microsoft.com/default...b;en-us;274310
> Do you have "set working set size" set to 1 instead of 0? If so, you should
> have the min and max server memory set the same.
> FWIW,
> Russell Fields
> "SalamElias" <eliassal@.online.nospam> wrote in message
> news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> Could
>
>
Showing posts with label warning. Show all posts
Showing posts with label warning. Show all posts
Monday, March 26, 2012
Error 823, Severity: 24
In the event viewer, I am getting an error "17122 : Initdata: Warning: Could
not set working size to 470281KB.
My sql is configured to have min = 128 and max RAM = 480281 in the server
properties
sheet(fixed memory configurarion).
What is SQL trying to set here and whjy?
ThanksSalamElias,
I am afraid that I don't really know what is happening, but I see that 823
is a Windows I/O error. When it happens it usually is followed by another
error. One KB article on this is:
http://support.microsoft.com/default.aspx?scid=kb;en-us;274310
Do you have "set working set size" set to 1 instead of 0? If so, you should
have the min and max server memory set the same.
FWIW,
Russell Fields
"SalamElias" <eliassal@.online.nospam> wrote in message
news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> In the event viewer, I am getting an error "17122 : Initdata: Warning:
Could
> not set working size to 470281KB.
> My sql is configured to have min = 128 and max RAM = 480281 in the server
> properties
> sheet(fixed memory configurarion).
> What is SQL trying to set here and whjy?
> Thanks
not set working size to 470281KB.
My sql is configured to have min = 128 and max RAM = 480281 in the server
properties
sheet(fixed memory configurarion).
What is SQL trying to set here and whjy?
ThanksSalamElias,
I am afraid that I don't really know what is happening, but I see that 823
is a Windows I/O error. When it happens it usually is followed by another
error. One KB article on this is:
http://support.microsoft.com/default.aspx?scid=kb;en-us;274310
Do you have "set working set size" set to 1 instead of 0? If so, you should
have the min and max server memory set the same.
FWIW,
Russell Fields
"SalamElias" <eliassal@.online.nospam> wrote in message
news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> In the event viewer, I am getting an error "17122 : Initdata: Warning:
Could
> not set working size to 470281KB.
> My sql is configured to have min = 128 and max RAM = 480281 in the server
> properties
> sheet(fixed memory configurarion).
> What is SQL trying to set here and whjy?
> Thanks
Error 823, Severity: 24
In the event viewer, I am getting an error "17122 : Initdata: Warning: Could
not set working size to 470281KB.
My sql is configured to have min = 128 and max RAM = 480281 in the server
properties
sheet(fixed memory configurarion).
What is SQL trying to set here and whjy?
ThanksSalamElias,
I am afraid that I don't really know what is happening, but I see that 823
is a Windows I/O error. When it happens it usually is followed by another
error. One KB article on this is:
http://support.microsoft.com/defaul...kb;en-us;274310
Do you have "set working set size" set to 1 instead of 0? If so, you should
have the min and max server memory set the same.
FWIW,
Russell Fields
"SalamElias" <eliassal@.online.nospam> wrote in message
news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> In the event viewer, I am getting an error "17122 : Initdata: Warning:
Could
> not set working size to 470281KB.
> My sql is configured to have min = 128 and max RAM = 480281 in the server
> properties
> sheet(fixed memory configurarion).
> What is SQL trying to set here and whjy?
> Thanks|||I ran sp_Configure, Ihave the folowing figues :
sp_configure
max server memory (MB) 4 2147483647 470 470
min server memory (MB) 0 2147483647 256 256
set working set size 0 1 1 1
When I the server RAM proprty sheet, Dynamically configure SQL Server
memoery with the min and max values indicated above as well as the "Reserve
physical memory for SQL Server " is checked.
So what should I do to stilluse these min max values and not set them both
with the same value
Thanks
Do you mean that I should have min = max = 470
"Russell Fields" wrote:
> SalamElias,
> I am afraid that I don't really know what is happening, but I see that 823
> is a Windows I/O error. When it happens it usually is followed by another
> error. One KB article on this is:
> http://support.microsoft.com/defaul...kb;en-us;274310
> Do you have "set working set size" set to 1 instead of 0? If so, you shou
ld
> have the min and max server memory set the same.
> FWIW,
> Russell Fields
> "SalamElias" <eliassal@.online.nospam> wrote in message
> news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> Could
>
>sql
not set working size to 470281KB.
My sql is configured to have min = 128 and max RAM = 480281 in the server
properties
sheet(fixed memory configurarion).
What is SQL trying to set here and whjy?
ThanksSalamElias,
I am afraid that I don't really know what is happening, but I see that 823
is a Windows I/O error. When it happens it usually is followed by another
error. One KB article on this is:
http://support.microsoft.com/defaul...kb;en-us;274310
Do you have "set working set size" set to 1 instead of 0? If so, you should
have the min and max server memory set the same.
FWIW,
Russell Fields
"SalamElias" <eliassal@.online.nospam> wrote in message
news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> In the event viewer, I am getting an error "17122 : Initdata: Warning:
Could
> not set working size to 470281KB.
> My sql is configured to have min = 128 and max RAM = 480281 in the server
> properties
> sheet(fixed memory configurarion).
> What is SQL trying to set here and whjy?
> Thanks|||I ran sp_Configure, Ihave the folowing figues :
sp_configure
max server memory (MB) 4 2147483647 470 470
min server memory (MB) 0 2147483647 256 256
set working set size 0 1 1 1
When I the server RAM proprty sheet, Dynamically configure SQL Server
memoery with the min and max values indicated above as well as the "Reserve
physical memory for SQL Server " is checked.
So what should I do to stilluse these min max values and not set them both
with the same value
Thanks
Do you mean that I should have min = max = 470
"Russell Fields" wrote:
> SalamElias,
> I am afraid that I don't really know what is happening, but I see that 823
> is a Windows I/O error. When it happens it usually is followed by another
> error. One KB article on this is:
> http://support.microsoft.com/defaul...kb;en-us;274310
> Do you have "set working set size" set to 1 instead of 0? If so, you shou
ld
> have the min and max server memory set the same.
> FWIW,
> Russell Fields
> "SalamElias" <eliassal@.online.nospam> wrote in message
> news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> Could
>
>sql
Sunday, March 11, 2012
Error 56
This morning, within the space of just a few minutes, we got a WHOLE lot of
these errors:
Event Type: Warning
Event Source: mraid35x
Event Category: None
Event ID: 56
Date: 1/27/2005
Time: 7:06:27 AM
User: N/A
Computer: SQL
Description:
The driver failed to allocate memory.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 10 00 01 00 66 00 .....f.
0008: 00 00 00 00 38 00 04 80 ...8..?
0010: 10 00 00 00 9a 00 00 c0 ...?..À
0018: 00 00 00 00 00 00 00 00 ......
0020: 00 00 00 00 00 00 00 00 ......
0028: 53 63 50 44 e0 01 00 00 ScPDà...
0030: 6c 69 74 75 b4 06 00 00 litu´...
I can't find any information regarding this error. We're running SQL on a
Windows 2003 server.
Thank you for your attention
mHello
Well, the first thing we are going to want to do is run chkdsk /f /r on the
server
to hopefully clear up the NTFS and FTDISK errors on the drive.
This will require a server reboot and could take over an hour to complete.
Next, we need you to delete and recreate your pagefile.sys. To do this,
1) When the Chkdsk.exe utility has completed, set the paging file size to 0.
a. Click Start, point to Settings, click Control Panel, and then
double-click
System. Click the Performance tab, click Change, and then point to the
partition
containing the Pagefile.sys file.
b. In the Initial Size (MB): box, type "0" (without the quotation marks).
c. In the Maximum Size (MB): box, type "0" (without the quotation marks).
d. Click Set, click OK, click Close, and then click Yes when you are
prompted to
restart the computer.
2) After the computer has restarted, reset the Pagefile.sys file to the
correct
size.
a. Click Start, point to Settings, click Control Panel, and then
double-click
System. Click the Performance tab, click Change, and then point to the
partition
containing the Pagefile.sys file.
b. In the Initial Size (MB): box, type a value equal to the amount of
random
access memory (in megabytes) in your computer plus 11.
c. In the Maximum Size (MB): box, type a value equal to or less than the
amount of
disk space available (in megabytes) on the specified partition minus 1.
d. Click Set, click OK, click Close, and then click Yes when you are
prompted to
restart the computer.
Hopefully this will correct the NTFS, FTDISK, and errors with your Promise
Controller.
If not, we will need to continue investigating further and review your next
memory.dmp file.
Let me know when you have completed the above actions.
Best Regards,
Regev Avivi (Mcse)
http://www.regevnet.com
<-- Please reply to the NewsGroup only -->
these errors:
Event Type: Warning
Event Source: mraid35x
Event Category: None
Event ID: 56
Date: 1/27/2005
Time: 7:06:27 AM
User: N/A
Computer: SQL
Description:
The driver failed to allocate memory.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 10 00 01 00 66 00 .....f.
0008: 00 00 00 00 38 00 04 80 ...8..?
0010: 10 00 00 00 9a 00 00 c0 ...?..À
0018: 00 00 00 00 00 00 00 00 ......
0020: 00 00 00 00 00 00 00 00 ......
0028: 53 63 50 44 e0 01 00 00 ScPDà...
0030: 6c 69 74 75 b4 06 00 00 litu´...
I can't find any information regarding this error. We're running SQL on a
Windows 2003 server.
Thank you for your attention
mHello
Well, the first thing we are going to want to do is run chkdsk /f /r on the
server
to hopefully clear up the NTFS and FTDISK errors on the drive.
This will require a server reboot and could take over an hour to complete.
Next, we need you to delete and recreate your pagefile.sys. To do this,
1) When the Chkdsk.exe utility has completed, set the paging file size to 0.
a. Click Start, point to Settings, click Control Panel, and then
double-click
System. Click the Performance tab, click Change, and then point to the
partition
containing the Pagefile.sys file.
b. In the Initial Size (MB): box, type "0" (without the quotation marks).
c. In the Maximum Size (MB): box, type "0" (without the quotation marks).
d. Click Set, click OK, click Close, and then click Yes when you are
prompted to
restart the computer.
2) After the computer has restarted, reset the Pagefile.sys file to the
correct
size.
a. Click Start, point to Settings, click Control Panel, and then
double-click
System. Click the Performance tab, click Change, and then point to the
partition
containing the Pagefile.sys file.
b. In the Initial Size (MB): box, type a value equal to the amount of
random
access memory (in megabytes) in your computer plus 11.
c. In the Maximum Size (MB): box, type a value equal to or less than the
amount of
disk space available (in megabytes) on the specified partition minus 1.
d. Click Set, click OK, click Close, and then click Yes when you are
prompted to
restart the computer.
Hopefully this will correct the NTFS, FTDISK, and errors with your Promise
Controller.
If not, we will need to continue investigating further and review your next
memory.dmp file.
Let me know when you have completed the above actions.
Best Regards,
Regev Avivi (Mcse)
http://www.regevnet.com
<-- Please reply to the NewsGroup only -->
Subscribe to:
Posts (Atom)