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?
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

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

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

Error 644 Severity level 21

Hi,
I got the following error message for one of our databases:
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 3/25/2005
Time: 9:18:53 AM
User: XXXXXXXX\Administrator
Computer: XXXXXX
Description:
Error: 644, Severity: 21, State: 3
Could not find the index entry for RID '16c42dc515100' in index page
(1:1725), index ID 0, database 'XXXXXXXXX_XXXXX_XXX_MSCRM'.
I looked up the error in Books Online and it told me to run DBCC CHECKDB to
see the extent of the damage. It gave me the following result:
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'XXXXXXXXX_XXXXX_XXX_MSCRM', index
'sysobjects.ncsysobjects2' (ID 1) (index ID 3). Extra or invalid key for the
keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:155:91) with values (parent_obj = 1237579447 and id =
365243844) points to the data row identified by ().
DBCC results for 'XXXXXXXXX_XXXXX_XXX_MSCRM'.
DBCC results for 'sysobjects'.
There are 2315 rows in 49 pages for object 'sysobjects'.
CHECKDB found 0 allocation errors and 1 consistency errors in table
'sysobjects' (object ID 1).
These don't seem to match. Should they?
The next thing that Books Online says to do is to run DBCC CHECKDB with the
REPAIR_REBUILD clause to fix the damage. Is this still an appropriate
course of action given that the error reported by checkdb doesn't seem to be
the one from the event log?
One of the other dba's here said that there may be a better way to rebuild
the index than to run the repair_rebuild on the entire database. I just
wanted to double check and get some other opinions/feedback before I
continued. Any help would really be appreciated. Thank you
-John
Hi
You have corruption.
Do a full backup of the database, then run the DBCC. There is probably more
than one problem so the DBCC finds the other one first.
At the same time, look for your backups because if the corruption is bad
enough, you need to restore to you last good backup.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"John Rosenlof" <greyseal96@.hotmail.com> wrote in message
news:O#0LBPYMFHA.3296@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I got the following error message for one of our databases:
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 3/25/2005
> Time: 9:18:53 AM
> User: XXXXXXXX\Administrator
> Computer: XXXXXX
> Description:
> Error: 644, Severity: 21, State: 3
> Could not find the index entry for RID '16c42dc515100' in index page
> (1:1725), index ID 0, database 'XXXXXXXXX_XXXXX_XXX_MSCRM'.
> I looked up the error in Books Online and it told me to run DBCC CHECKDB
to
> see the extent of the damage. It gave me the following result:
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'XXXXXXXXX_XXXXX_XXX_MSCRM', index
> 'sysobjects.ncsysobjects2' (ID 1) (index ID 3). Extra or invalid key for
the
> keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:155:91) with values (parent_obj = 1237579447 and id =
> 365243844) points to the data row identified by ().
> DBCC results for 'XXXXXXXXX_XXXXX_XXX_MSCRM'.
> DBCC results for 'sysobjects'.
> There are 2315 rows in 49 pages for object 'sysobjects'.
> CHECKDB found 0 allocation errors and 1 consistency errors in table
> 'sysobjects' (object ID 1).
> These don't seem to match. Should they?
> The next thing that Books Online says to do is to run DBCC CHECKDB with
the
> REPAIR_REBUILD clause to fix the damage. Is this still an appropriate
> course of action given that the error reported by checkdb doesn't seem to
be
> the one from the event log?
> One of the other dba's here said that there may be a better way to rebuild
> the index than to run the repair_rebuild on the entire database. I just
> wanted to double check and get some other opinions/feedback before I
> continued. Any help would really be appreciated. Thank you
> -John
>

Error 644 Severity level 21

Hi,
I got the following error message for one of our databases:
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 3/25/2005
Time: 9:18:53 AM
User: XXXXXXXX\Administrator
Computer: XXXXXX
Description:
Error: 644, Severity: 21, State: 3
Could not find the index entry for RID '16c42dc515100' in index page
(1:1725), index ID 0, database 'XXXXXXXXX_XXXXX_XXX_MSCRM'.
I looked up the error in Books Online and it told me to run DBCC CHECKDB to
see the extent of the damage. It gave me the following result:
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'XXXXXXXXX_XXXXX_XXX_MSCRM', index
'sysobjects.ncsysobjects2' (ID 1) (index ID 3). Extra or invalid key for the
keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:155:91) with values (parent_obj = 1237579447 and id =
365243844) points to the data row identified by ().
DBCC results for 'XXXXXXXXX_XXXXX_XXX_MSCRM'.
DBCC results for 'sysobjects'.
There are 2315 rows in 49 pages for object 'sysobjects'.
CHECKDB found 0 allocation errors and 1 consistency errors in table
'sysobjects' (object ID 1).
These don't seem to match. Should they?
The next thing that Books Online says to do is to run DBCC CHECKDB with the
REPAIR_REBUILD clause to fix the damage. Is this still an appropriate
course of action given that the error reported by checkdb doesn't seem to be
the one from the event log?
One of the other dba's here said that there may be a better way to rebuild
the index than to run the repair_rebuild on the entire database. I just
wanted to double check and get some other opinions/feedback before I
continued. Any help would really be appreciated. Thank you
-JohnHi
You have corruption.
Do a full backup of the database, then run the DBCC. There is probably more
than one problem so the DBCC finds the other one first.
At the same time, look for your backups because if the corruption is bad
enough, you need to restore to you last good backup.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"John Rosenlof" <greyseal96@.hotmail.com> wrote in message
news:O#0LBPYMFHA.3296@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I got the following error message for one of our databases:
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 3/25/2005
> Time: 9:18:53 AM
> User: XXXXXXXX\Administrator
> Computer: XXXXXX
> Description:
> Error: 644, Severity: 21, State: 3
> Could not find the index entry for RID '16c42dc515100' in index page
> (1:1725), index ID 0, database 'XXXXXXXXX_XXXXX_XXX_MSCRM'.
> I looked up the error in Books Online and it told me to run DBCC CHECKDB
to
> see the extent of the damage. It gave me the following result:
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'XXXXXXXXX_XXXXX_XXX_MSCRM', index
> 'sysobjects.ncsysobjects2' (ID 1) (index ID 3). Extra or invalid key for
the
> keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:155:91) with values (parent_obj = 1237579447 and id =
> 365243844) points to the data row identified by ().
> DBCC results for 'XXXXXXXXX_XXXXX_XXX_MSCRM'.
> DBCC results for 'sysobjects'.
> There are 2315 rows in 49 pages for object 'sysobjects'.
> CHECKDB found 0 allocation errors and 1 consistency errors in table
> 'sysobjects' (object ID 1).
> These don't seem to match. Should they?
> The next thing that Books Online says to do is to run DBCC CHECKDB with
the
> REPAIR_REBUILD clause to fix the damage. Is this still an appropriate
> course of action given that the error reported by checkdb doesn't seem to
be
> the one from the event log?
> One of the other dba's here said that there may be a better way to rebuild
> the index than to run the repair_rebuild on the entire database. I just
> wanted to double check and get some other opinions/feedback before I
> continued. Any help would really be appreciated. Thank you
> -John
>

Error 644 Severity level 21

Hi,
I got the following error message for one of our databases:
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 3/25/2005
Time: 9:18:53 AM
User: XXXXXXXX\Administrator
Computer: XXXXXX
Description:
Error: 644, Severity: 21, State: 3
Could not find the index entry for RID '16c42dc515100' in index page
(1:1725), index ID 0, database 'XXXXXXXXX_XXXXX_XXX_MSCRM'.
I looked up the error in Books Online and it told me to run DBCC CHECKDB to
see the extent of the damage. It gave me the following result:
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'XXXXXXXXX_XXXXX_XXX_MSCRM', index
'sysobjects.ncsysobjects2' (ID 1) (index ID 3). Extra or invalid key for the
keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:155:91) with values (parent_obj = 1237579447 and id = 365243844) points to the data row identified by ().
DBCC results for 'XXXXXXXXX_XXXXX_XXX_MSCRM'.
DBCC results for 'sysobjects'.
There are 2315 rows in 49 pages for object 'sysobjects'.
CHECKDB found 0 allocation errors and 1 consistency errors in table
'sysobjects' (object ID 1).
These don't seem to match. Should they?
The next thing that Books Online says to do is to run DBCC CHECKDB with the
REPAIR_REBUILD clause to fix the damage. Is this still an appropriate
course of action given that the error reported by checkdb doesn't seem to be
the one from the event log?
One of the other dba's here said that there may be a better way to rebuild
the index than to run the repair_rebuild on the entire database. I just
wanted to double check and get some other opinions/feedback before I
continued. Any help would really be appreciated. Thank you
-JohnHi
You have corruption.
Do a full backup of the database, then run the DBCC. There is probably more
than one problem so the DBCC finds the other one first.
At the same time, look for your backups because if the corruption is bad
enough, you need to restore to you last good backup.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"John Rosenlof" <greyseal96@.hotmail.com> wrote in message
news:O#0LBPYMFHA.3296@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I got the following error message for one of our databases:
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 3/25/2005
> Time: 9:18:53 AM
> User: XXXXXXXX\Administrator
> Computer: XXXXXX
> Description:
> Error: 644, Severity: 21, State: 3
> Could not find the index entry for RID '16c42dc515100' in index page
> (1:1725), index ID 0, database 'XXXXXXXXX_XXXXX_XXX_MSCRM'.
> I looked up the error in Books Online and it told me to run DBCC CHECKDB
to
> see the extent of the damage. It gave me the following result:
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'XXXXXXXXX_XXXXX_XXX_MSCRM', index
> 'sysobjects.ncsysobjects2' (ID 1) (index ID 3). Extra or invalid key for
the
> keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:155:91) with values (parent_obj = 1237579447 and id => 365243844) points to the data row identified by ().
> DBCC results for 'XXXXXXXXX_XXXXX_XXX_MSCRM'.
> DBCC results for 'sysobjects'.
> There are 2315 rows in 49 pages for object 'sysobjects'.
> CHECKDB found 0 allocation errors and 1 consistency errors in table
> 'sysobjects' (object ID 1).
> These don't seem to match. Should they?
> The next thing that Books Online says to do is to run DBCC CHECKDB with
the
> REPAIR_REBUILD clause to fix the damage. Is this still an appropriate
> course of action given that the error reported by checkdb doesn't seem to
be
> the one from the event log?
> One of the other dba's here said that there may be a better way to rebuild
> the index than to run the repair_rebuild on the entire database. I just
> wanted to double check and get some other opinions/feedback before I
> continued. Any help would really be appreciated. Thank you
> -John
>

ERROR 605, SEVERITY 21

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,
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 605, SEVERITY 21

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,
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/in..._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 605, SEVERITY 21

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.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/inf...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 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 -->

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

Error 208 Event ID 17052

Here is a weird one:
Using EM 2000 to connect to a 7.0 SQL Server. As soon as
I click on Management, I receive an error in my SQL Log
and Event Viewer for Error 208, Event ID 17052 stating
Invalid Object Name 'msdb.dbo.log_shipping_provider'
I do not have log shipping configured on any of my
servers. Has anyone ran into this'
Thanks!Here is some more interesting info:
This only happens when using EM 2000, if I use the 7.0 EM
it does not cause the error. Anyone connecting with EM
2000 can make the error occur. Any thoughts'
>--Original Message--
>Here is a weird one:
>Using EM 2000 to connect to a 7.0 SQL Server. As soon as
>I click on Management, I receive an error in my SQL Log
>and Event Viewer for Error 208, Event ID 17052 stating
>Invalid Object Name 'msdb.dbo.log_shipping_provider'
>I do not have log shipping configured on any of my
>servers. Has anyone ran into this'
>Thanks!
>.
>|||Hi,
This error is generally caused if the object ownership is
not properly referenced when accessing that object. You
have to use the fully qualified name i.e
dbname.ObjectOwner.ObjectName.
It seems to me that the owner of
the 'log_shipping_provider' table in the msdb is NOT dbo.
You might want to take a look the ownership of this table.
Also, it is possible that the user connecting SQL Server 7
EM is connecting with the ID that owns that table!
Suppose the above table is owned id 'test'. You could be
trying to connected with 'sa' and the connection will
fail. But if you connect with 'test', it will work fine.
Take a look. hth
DeeJay
>--Original Message--
>Here is some more interesting info:
>This only happens when using EM 2000, if I use the 7.0 EM
>it does not cause the error. Anyone connecting with EM
>2000 can make the error occur. Any thoughts'
>>--Original Message--
>>Here is a weird one:
>>Using EM 2000 to connect to a 7.0 SQL Server. As soon
as
>>I click on Management, I receive an error in my SQL Log
>>and Event Viewer for Error 208, Event ID 17052 stating
>>Invalid Object Name 'msdb.dbo.log_shipping_provider'
>>I do not have log shipping configured on any of my
>>servers. Has anyone ran into this'
>>Thanks!
>>.
>.
>|||The log shipping tables do not exist in 7.0
So ownership wasn't the prob.
>--Original Message--
>Hi,
>This error is generally caused if the object ownership is
>not properly referenced when accessing that object. You
>have to use the fully qualified name i.e
>dbname.ObjectOwner.ObjectName.
>It seems to me that the owner of
>the 'log_shipping_provider' table in the msdb is NOT dbo.
>You might want to take a look the ownership of this table.
>Also, it is possible that the user connecting SQL Server
7
>EM is connecting with the ID that owns that table!
>Suppose the above table is owned id 'test'. You could be
>trying to connected with 'sa' and the connection will
>fail. But if you connect with 'test', it will work fine.
>Take a look. hth
>DeeJay
>
>>--Original Message--
>>Here is some more interesting info:
>>This only happens when using EM 2000, if I use the 7.0
EM
>>it does not cause the error. Anyone connecting with EM
>>2000 can make the error occur. Any thoughts'
>>--Original Message--
>>Here is a weird one:
>>Using EM 2000 to connect to a 7.0 SQL Server. As soon
>as
>>I click on Management, I receive an error in my SQL Log
>>and Event Viewer for Error 208, Event ID 17052 stating
>>Invalid Object Name 'msdb.dbo.log_shipping_provider'
>>I do not have log shipping configured on any of my
>>servers. Has anyone ran into this'
>>Thanks!
>>.
>>.
>.
>|||Silly me ... I knew that!
Are you connecting through just the client Tools (from
your workstation) or from a machine where SQL Server
2000/7 is installed?
Eventhough, log shipping is not configured, this table
could still, somehow, exist. You might want to take look
at the msdb database.
I have not found anything else for this error.
hth
DeeJay
>--Original Message--
>The log shipping tables do not exist in 7.0
>So ownership wasn't the prob.
>>--Original Message--
>>Hi,
>>This error is generally caused if the object ownership
is
>>not properly referenced when accessing that object. You
>>have to use the fully qualified name i.e
>>dbname.ObjectOwner.ObjectName.
>>It seems to me that the owner of
>>the 'log_shipping_provider' table in the msdb is NOT
dbo.
>>You might want to take a look the ownership of this
table.
>>Also, it is possible that the user connecting SQL Server
>7
>>EM is connecting with the ID that owns that table!
>>Suppose the above table is owned id 'test'. You could be
>>trying to connected with 'sa' and the connection will
>>fail. But if you connect with 'test', it will work fine.
>>Take a look. hth
>>DeeJay
>>
>>--Original Message--
>>Here is some more interesting info:
>>This only happens when using EM 2000, if I use the 7.0
>EM
>>it does not cause the error. Anyone connecting with EM
>>2000 can make the error occur. Any thoughts'
>>--Original Message--
>>Here is a weird one:
>>Using EM 2000 to connect to a 7.0 SQL Server. As soon
>>as
>>I click on Management, I receive an error in my SQL
Log
>>and Event Viewer for Error 208, Event ID 17052 stating
>>Invalid Object Name 'msdb.dbo.log_shipping_provider'
>>I do not have log shipping configured on any of my
>>servers. Has anyone ran into this'
>>Thanks!
>>.
>>.
>>.
>.
>|||I'm just connecting through the client tools. I've
checked msdb and haven't found anything that remotely
looks like the log shipping tables.
This is weird!
>--Original Message--
>Silly me ... I knew that!
>Are you connecting through just the client Tools (from
>your workstation) or from a machine where SQL Server
>2000/7 is installed?
>Eventhough, log shipping is not configured, this table
>could still, somehow, exist. You might want to take look
>at the msdb database.
>I have not found anything else for this error.
>hth
>DeeJay
>
>>--Original Message--
>>The log shipping tables do not exist in 7.0
>>So ownership wasn't the prob.
>>--Original Message--
>>Hi,
>>This error is generally caused if the object ownership
>is
>>not properly referenced when accessing that object. You
>>have to use the fully qualified name i.e
>>dbname.ObjectOwner.ObjectName.
>>It seems to me that the owner of
>>the 'log_shipping_provider' table in the msdb is NOT
>dbo.
>>You might want to take a look the ownership of this
>table.
>>Also, it is possible that the user connecting SQL
Server
>>7
>>EM is connecting with the ID that owns that table!
>>Suppose the above table is owned id 'test'. You could
be
>>trying to connected with 'sa' and the connection will
>>fail. But if you connect with 'test', it will work fine.
>>Take a look. hth
>>DeeJay
>>
>>--Original Message--
>>Here is some more interesting info:
>>This only happens when using EM 2000, if I use the 7.0
>>EM
>>it does not cause the error. Anyone connecting with
EM
>>2000 can make the error occur. Any thoughts'
>>--Original Message--
>>Here is a weird one:
>>Using EM 2000 to connect to a 7.0 SQL Server. As
soon
>>as
>>I click on Management, I receive an error in my SQL
>Log
>>and Event Viewer for Error 208, Event ID 17052
stating
>>Invalid Object Name 'msdb.dbo.log_shipping_provider'
>>I do not have log shipping configured on any of my
>>servers. Has anyone ran into this'
>>Thanks!
>>.
>>.
>>.
>>.
>.
>|||Hum...this one got me.
The only documentation for error 208 is for what we have
already talked about
>--Original Message--
>I'm just connecting through the client tools. I've
>checked msdb and haven't found anything that remotely
>looks like the log shipping tables.
>This is weird!
>>--Original Message--
>>Silly me ... I knew that!
>>Are you connecting through just the client Tools (from
>>your workstation) or from a machine where SQL Server
>>2000/7 is installed?
>>Eventhough, log shipping is not configured, this table
>>could still, somehow, exist. You might want to take look
>>at the msdb database.
>>I have not found anything else for this error.
>>hth
>>DeeJay
>>
>>--Original Message--
>>The log shipping tables do not exist in 7.0
>>So ownership wasn't the prob.
>>--Original Message--
>>Hi,
>>This error is generally caused if the object ownership
>>is
>>not properly referenced when accessing that object.
You
>>have to use the fully qualified name i.e
>>dbname.ObjectOwner.ObjectName.
>>It seems to me that the owner of
>>the 'log_shipping_provider' table in the msdb is NOT
>>dbo.
>>You might want to take a look the ownership of this
>>table.
>>Also, it is possible that the user connecting SQL
>Server
>>7
>>EM is connecting with the ID that owns that table!
>>Suppose the above table is owned id 'test'. You could
>be
>>trying to connected with 'sa' and the connection will
>>fail. But if you connect with 'test', it will work
fine.
>>Take a look. hth
>>DeeJay
>>
>>--Original Message--
>>Here is some more interesting info:
>>This only happens when using EM 2000, if I use the
7.0
>>EM
>>it does not cause the error. Anyone connecting with
>EM
>>2000 can make the error occur. Any thoughts'
>>--Original Message--
>>Here is a weird one:
>>Using EM 2000 to connect to a 7.0 SQL Server. As
>soon
>>as
>>I click on Management, I receive an error in my SQL
>>Log
>>and Event Viewer for Error 208, Event ID 17052
>stating
>>Invalid Object Name 'msdb.dbo.log_shipping_provider'
>>I do not have log shipping configured on any of my
>>servers. Has anyone ran into this'
>>Thanks!
>>.
>>.
>>.
>>.
>>.
>.
>

Error 208

Hi,
every morning about 06.03 AM in DB PROBA there is the follow error:
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 6/1/2006
Time: 6:03:22 AM
User: N/A
Description:
name database: PROVA
Error: 208, Severity: 16, State: 0
Invalid object name '#tmp'.
Someone can help me to understand the reason of the error...
Thanks a lotLuca (artematico@.yahoo.it) writes:
> every morning about 06.03 AM in DB PROBA there is the follow error:
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 6/1/2006
> Time: 6:03:22 AM
> User: N/A
> Description:
> name database: PROVA
> Error: 208, Severity: 16, State: 0
> Invalid object name '#tmp'.
> Someone can help me to understand the reason of the error...
I would check for scheduled jobs running at this time.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||I assume that this is a scheduled job
The job is looking for a temporary table #tmp, this object does not
exists, it either got dropped, is out of scope or got never created
Open up QA and run this
select * from #tmp
you will see this error message
Server: Msg 208, Level 16, State 1, Line 1
Invalid object name '#tmp'.
Take a look at the code and try to figure out if it's the object is
misspelled by mistake #tmp instead of #temp
Denis the SQL Menace
http://sqlservercode.blogspot.com/
Luca wrote:
> Hi,
> every morning about 06.03 AM in DB PROBA there is the follow error:
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 6/1/2006
> Time: 6:03:22 AM
> User: N/A
> Description:
> name database: PROVA
> Error: 208, Severity: 16, State: 0
> Invalid object name '#tmp'.
> Someone can help me to understand the reason of the error...
> Thanks a lot|||SQL Menace ha scritto:

> I assume that this is a scheduled job
> The job is looking for a temporary table #tmp, this object does not
> exists, it either got dropped, is out of scope or got never created
> Open up QA and run this
> select * from #tmp
> you will see this error message
> Server: Msg 208, Level 16, State 1, Line 1
> Invalid object name '#tmp'.
> Take a look at the code and try to figure out if it's the object is
> misspelled by mistake #tmp instead of #temp
I run this
select * from '#tmp
but there is the same error:
Server: Msg 208, Level 16, State 1, Line 1
Invalid object name '#temp'.
> Denis the SQL Menace
> http://sqlservercode.blogspot.com/
>
> Luca wrote:|||Yes you will get that error since the temp table does not exist for
your connection
Whatever code runs at that time, open it up and look where #tmp is
referenced
Denis the SQL Menace
http://sqlservercode.blogspot.com/
Luca wrote:
> SQL Menace ha scritto:
>
> I run this
> select * from '#tmp
> but there is the same error:
> Server: Msg 208, Level 16, State 1, Line 1
> Invalid object name '#temp'.
>|||SQL Menace ha scritto:

> Yes you will get that error since the temp table does not exist for
> your connection
> Whatever code runs at that time, open it up and look where #tmp is
> referenced
The code runs at 06.00 AM, how can I look where #tmp is referenced?
>
> Denis the SQL Menace
> http://sqlservercode.blogspot.com/
>
> Luca wrote:|||Enterprise Manager-->management-->SQL server Agent-->Jobs
You will see a bunch of icons in blue (succes) or Red (failed)
One of the red ones is the one that uses #tmp (you can also scroll to
the right and look at the next run date column, that will have the date
and time there)
The double click on the job, click on the steps tab and double click
step1 (it will be blue)
If the code looks like this EXECUTE master.dbo.xp_sqlmaint N'-PlanID
2C6BA936-F50A-42F9-AFA5-B88BC0251AF3 -Rpt "d:\MSSQL\LOG\DB Maintenance
Plan10.txt" -DelTxtRpt 1WEEKS -WriteHistory -RebldIdx 10
-RmUnusedSpace 50 10 ' then it is s maintainance plan and maybe you ran
out of space on your hard disk and the object could not be created
Delete stuff you don't need or move some tables to another
filegroup/hard drive (if you have multiple drives)
Or put tempdb on it's own hardrive and the LOG files also on their own
hard drive
Denis the SQL Menace
http://sqlservercode.blogspot.com/
Luca wrote:
> SQL Menace ha scritto:
>
> The code runs at 06.00 AM, how can I look where #tmp is referenced?
>|||SQL Menace ha scritto:

> Enterprise Manager-->management-->SQL server Agent-->Jobs
> You will see a bunch of icons in blue (succes) or Red (failed)
> One of the red ones is the one that uses #tmp (you can also scroll to
> the right and look at the next run date column, that will have the date
> and time there)
There isn't any red icons, they are all blu
> The double click on the job, click on the steps tab and double click
> step1 (it will be blue)
> If the code looks like this EXECUTE master.dbo.xp_sqlmaint N'-PlanID
> 2C6BA936-F50A-42F9-AFA5-B88BC0251AF3 -Rpt "d:\MSSQL\LOG\DB Maintenance
> Plan10.txt" -DelTxtRpt 1WEEKS -WriteHistory -RebldIdx 10
> -RmUnusedSpace 50 10 ' then it is s maintainance plan and maybe you ran
> out of space on your hard disk and the object could not be created
> Delete stuff you don't need or move some tables to another
> filegroup/hard drive (if you have multiple drives)
> Or put tempdb on it's own hardrive and the LOG files also on their own
> hard drive
>
> Denis the SQL Menace
> http://sqlservercode.blogspot.com/
> Luca wrote:|||Luca (artematico@.yahoo.it) writes:
> There isn't any red icons, they are all blu
You may have to inspect the job history. The job could be set up so
that it continues with the next step even on error. Or it runs a second
time, and this time it's successful.
In any case, as long everything else appears to be working normally on
your sever, it may not be worth the effort to track this down.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx