Monday, March 26, 2012
Error 823, Severity: 24
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
>
>
Error 823, Severity: 24
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
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 605, SEVERITY 21
I found error in the SERVER(subscriber in merge replication) windows event
viewer the error is regarding a particular database(out of 15).
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 6/23/2005
Time: 12:32:26 AM
User: N/A
Computer: DTDPMS
Description:
Error: 605, Severity: 21, State: 1
Attempt to fetch logical page (1:98036) in database 'CERES' belongs to
object 'PatientAlerts', not to object 'chargepostingprocs'.
Data:
0000: 5d 02 00 00 15 00 00 00 ]......
0008: 07 00 00 00 44 00 54 00 ...D.T.
0010: 44 00 50 00 4d 00 53 00 D.P.M.S.
0018: 00 00 06 00 00 00 43 00 .....C.
0020: 45 00 52 00 45 00 53 00 E.R.E.S.
0028: 00 00 ..
can u help me.
What is the reason for this message?
How can I resolve this?
Thanks,
Sourahttp://www.mssqlcity.com/FAQ/Trouble/er605.htm
--
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"SouRa" <SouRa@.discussions.microsoft.com> schrieb im Newsbeitrag
news:3A2EC9C8-06D3-4BC7-85BF-22A732A35B6C@.microsoft.com...
> Hi,
> I found error in the SERVER(subscriber in merge replication) windows event
> viewer the error is regarding a particular database(out of 15).
>
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 6/23/2005
> Time: 12:32:26 AM
> User: N/A
> Computer: DTDPMS
> Description:
> Error: 605, Severity: 21, State: 1
> Attempt to fetch logical page (1:98036) in database 'CERES' belongs to
> object 'PatientAlerts', not to object 'chargepostingprocs'.
> Data:
> 0000: 5d 02 00 00 15 00 00 00 ]......
> 0008: 07 00 00 00 44 00 54 00 ...D.T.
> 0010: 44 00 50 00 4d 00 53 00 D.P.M.S.
> 0018: 00 00 06 00 00 00 43 00 .....C.
> 0020: 45 00 52 00 45 00 53 00 E.R.E.S.
> 0028: 00 00 ..
> can u help me.
> What is the reason for this message?
> How can I resolve this?
> Thanks,
> Soura
>|||The first thing should be to check the db integrity using "dbcc checkdb".
AMB
"SouRa" wrote:
> Hi,
> I found error in the SERVER(subscriber in merge replication) windows event
> viewer the error is regarding a particular database(out of 15).
>
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 6/23/2005
> Time: 12:32:26 AM
> User: N/A
> Computer: DTDPMS
> Description:
> Error: 605, Severity: 21, State: 1
> Attempt to fetch logical page (1:98036) in database 'CERES' belongs to
> object 'PatientAlerts', not to object 'chargepostingprocs'.
> Data:
> 0000: 5d 02 00 00 15 00 00 00 ]......
> 0008: 07 00 00 00 44 00 54 00 ...D.T.
> 0010: 44 00 50 00 4d 00 53 00 D.P.M.S.
> 0018: 00 00 06 00 00 00 43 00 .....C.
> 0020: 45 00 52 00 45 00 53 00 E.R.E.S.
> 0028: 00 00 ..
> can u help me.
> What is the reason for this message?
> How can I resolve this?
> Thanks,
> Soura
>|||http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"SouRa" <SouRa@.discussions.microsoft.com> wrote in message
news:3A2EC9C8-06D3-4BC7-85BF-22A732A35B6C@.microsoft.com...
> Hi,
> I found error in the SERVER(subscriber in merge replication) windows event
> viewer the error is regarding a particular database(out of 15).
>
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 6/23/2005
> Time: 12:32:26 AM
> User: N/A
> Computer: DTDPMS
> Description:
> Error: 605, Severity: 21, State: 1
> Attempt to fetch logical page (1:98036) in database 'CERES' belongs to
> object 'PatientAlerts', not to object 'chargepostingprocs'.
> Data:
> 0000: 5d 02 00 00 15 00 00 00 ]......
> 0008: 07 00 00 00 44 00 54 00 ...D.T.
> 0010: 44 00 50 00 4d 00 53 00 D.P.M.S.
> 0018: 00 00 06 00 00 00 43 00 .....C.
> 0020: 45 00 52 00 45 00 53 00 E.R.E.S.
> 0028: 00 00 ..
> can u help me.
> What is the reason for this message?
> How can I resolve this?
> Thanks,
> Soura
>
Error 5172
Hi,
I have a SQL Server 2000 running in a Windows 2003 Server. I restarted the server but SQL didn't startup, showing in the event viewer Error: 5172, Severity: 16, State: 15
Can anybody help me?
Thanks in advance,
Octavio Vargas
octavio.vargas@.macimex.com
The error text for error 5172 is along the lines of:
"The Header For File '.....ldf'' is not a valid database file header."
So it sounds like one of the system databases is corrupt - possibly the master database, particularly as SQL Server can't start. The lack of an error message in the text you quoted suggests that SQL Server can't access the master.dbo.sysmessages table.
If you have a recent backup of your master database then try restoring it - otherwise you may have to rebuild it.
Have a look at these links for more info:
http://msdn2.microsoft.com/en-us/library/aa173515(SQL.80).aspx
http://msdn2.microsoft.com/en-us/library/aa213831(SQL.80).aspx
Once it has been rebuilt you should re-apply any service packs and hotfixes then re-install any custom objects that you have that reside in the master database.
Chris
|||Error 5172 is "The header for file '%ls' is not a valid database file header. The %ls property is incorrect.".
This indicates that you probably could well have a corrupt database. The full message should tell you which database and what property it is objecting to.
Also
What were the messages around this message in the log?|||Thanks Chris,
I don't have a backup of my master database, only for my user databases.
If i rebuild the master database, can i lose all my DTS and jobs?
|||In the log appears the next message:
Stack overflow - Dump not possible
I have SP1 in Windows 2003 server and SP4 in SQL Server 2000
|||I still think that the first error you provided is the biggest clue to the source of the error.
Chris
|||The jobs and DTS packages are stored in the msdb database, however they will be lost when you rebuild the master database as msdb is also rebuilt.
On this basis I would take copies of the msdb mdf and ldf files before you attempt to rebuild the master database. Once the rebuild has been completed and SP4 has been applied, stop the SQL Server service, rename the newly created msdb data and log files, copy the old (previously copied) files to the same folder then restart SQL Server. This *might* work, however if it doesn't then you'll need to re-instate the newly created data and log files.
Note that DTS packages are stored in msdb.dbo.sysdtspackages so you could actually attach the old msdb files (under a different database name) then use the Import/Export wizard to copy the data into the new msdb database.
Once you've been through the rebuild process I would recommend that, going forward, you take backups of the master and msdb databases on a regular basis.
Chris
|||I was more interested in the lines before which will tell us what database it was trying to start up when it threw the error. Error messages are much easier to interpret in context.
Microsoft are not charging you by the line here so it is useful to put up at least a few messages either side of the one and if there is a fatal error/stop message it is useful to run to that (as you know that you have all the messages up to the failure. You can clear the IP addresses and server names from the messages if that is sensitive, but the existance and meat of the messages is useful in helping with your problem.
|||In the event viewer it only shows the number error, but in the message log it looks like it was trying to open the master database.|||In that case, then, it seems like your master database is corrupt.
Chris