Error 207: regular

Showing posts with label regular. Show all posts

Tuesday, March 27, 2012

Error 8965

I'm getting this error message ONLY SOMETIMES after a DBCC (I'd feel better
if it showed up on a regular basis). I haven't found much dealing with this
. The table is used to store small videos. Any useful suggestions (somethi
ng more than "restore from
a backup" or "call Microsoft") would be greatly appreciated.
I'm on Windows 2000 SP 4 and SQL 2000 SP 3.
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8965: [Microsoft]&#
91;ODBC SQL Server Driver][SQL Server]Table error: Object ID %. The text
, ntext, or image node at page (1:8544241), slot 0, text ID 17459904512 is r
eferenced by page (1:8544242), slot 0,
but was not seen in the scan.
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Obje
ct ID %. The text, ntext, or image node at page (1:8544243), slot 0, text ID
17459904512 is referenced by page (1:8544242), slot 0, but was not seen in
the scan.
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Obje
ct ID %. The text, ntext, or image node at page (1:8544244), slot 0, text ID
17459904512 is referenced by page (1:8544242), slot 0, but was not seen in
the scan.
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 a
llocation errors and 3 consistency errors in table 'Table_Name' (object ID %
).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 a
llocation errors and 3 consistency errors in database 'Database_Name'.
[Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data
_loss is the minimum repair level for the errors found by DBCC CHECKDB (Data
base_Name ).The error message is indicating a corruption in the table. The root cause
of the corruption is unknown at this stage and will require more
information.
One explanation as to why the error only appears sometimes and not always
is if you run the dbcc checkdb command with any of the repair options then
it's likely that the corruption is repaired and reappears sometime later
again.
HTH
Agnes Panosian
SQL Server Supportsql

Error 8965

I'm getting this error message ONLY SOMETIMES after a DBCC (I'd feel better if it showed up on a regular basis). I haven't found much dealing with this. The table is used to store small videos. Any useful suggestions (something more than "restore from
a backup" or "call Microsoft") would be greatly appreciated.
I'm on Windows 2000 SP 4 and SQL 2000 SP 3.
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8965: [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID %. The text, ntext, or image node at page (1:8544241), slot 0, text ID 17459904512 is referenced by page (1:8544242), slot 0,
but was not seen in the scan.
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID %. The text, ntext, or image node at page (1:8544243), slot 0, text ID 17459904512 is referenced by page (1:8544242), slot 0, but was not seen in the scan.
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID %. The text, ntext, or image node at page (1:8544244), slot 0, text ID 17459904512 is referenced by page (1:8544242), slot 0, but was not seen in the scan.
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 3 consistency errors in table 'Table_Name' (object ID %).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 3 consistency errors in database 'Database_Name'.
[Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (Database_Name ).
The error message is indicating a corruption in the table. The root cause
of the corruption is unknown at this stage and will require more
information.
One explanation as to why the error only appears sometimes and not always
is if you run the dbcc checkdb command with any of the repair options then
it's likely that the corruption is repaired and reappears sometime later
again.
HTH
Agnes Panosian
SQL Server Support

Error 8965

I'm getting this error message ONLY SOMETIMES after a DBCC (I'd feel better if it showed up on a regular basis). I haven't found much dealing with this. The table is used to store small videos. Any useful suggestions (something more than "restore from a backup" or "call Microsoft") would be greatly appreciated
I'm on Windows 2000 SP 4 and SQL 2000 SP 3
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8965: [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID %. The text, ntext, or image node at page (1:8544241), slot 0, text ID 17459904512 is referenced by page (1:8544242), slot 0, but was not seen in the scan
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID %. The text, ntext, or image node at page (1:8544243), slot 0, text ID 17459904512 is referenced by page (1:8544242), slot 0, but was not seen in the scan
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID %. The text, ntext, or image node at page (1:8544244), slot 0, text ID 17459904512 is referenced by page (1:8544242), slot 0, but was not seen in the scan
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 3 consistency errors in table 'Table_Name' (object ID %)
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 3 consistency errors in database 'Database_Name'
[Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (Database_Name )The error message is indicating a corruption in the table. The root cause
of the corruption is unknown at this stage and will require more
information.
One explanation as to why the error only appears sometimes and not always
is if you run the dbcc checkdb command with any of the repair options then
it's likely that the corruption is repaired and reappears sometime later
again.
HTH
Agnes Panosian
SQL Server Support

Error 87 from GetProxyAccount on line 604

Error 87 from GetProxyAccount on line 604
I am trying to set up a regular SQL login which is NOT a
sysadmin with the ability to run xp_cmdshell. It's not
the best idea, but I have no choice. I granted it
execute permissions on the proc and used
xp_sqlagent_proxy_account to point to a login which is a
local admin on the server. Whenever I try to execute
xp_cmdshell under that account, I get the error :
Msg 50001, Level 1, State 50001
xpsql.cpp: Error 87 from GetProxyAccount on line 604
A search of KB and a few of these newsgroups turned up
nothing. The version number of SQL Server is 08.00.0818
(sp3 + security update).Have you tried allowing execute rights for guest
permission for xp_cmdshell in the master db ?
Its a bit of a naughty one but will should work until you
get your users sorted out.
Peter
"I love deadlines. I like the whooshing sound they make as
they fly by."
Douglas Adams
>--Original Message--
>Error 87 from GetProxyAccount on line 604
>
>I am trying to set up a regular SQL login which is NOT a
>sysadmin with the ability to run xp_cmdshell. It's not
>the best idea, but I have no choice. I granted it
>execute permissions on the proc and used
>xp_sqlagent_proxy_account to point to a login which is a
>local admin on the server. Whenever I try to execute
>xp_cmdshell under that account, I get the error :
>Msg 50001, Level 1, State 50001
>xpsql.cpp: Error 87 from GetProxyAccount on line 604
>A search of KB and a few of these newsgroups turned up
>nothing. The version number of SQL Server is 08.00.0818
>(sp3 + security update).
>.
>|||Peter,
I gave it a shot and I still get the same error. Thanks
for the suggestion though.
Chris
>--Original Message--
>Have you tried allowing execute rights for guest
>permission for xp_cmdshell in the master db ?
>Its a bit of a naughty one but will should work until
you
>get your users sorted out.
>Peter
>"I love deadlines. I like the whooshing sound they make
as
>they fly by."
>Douglas Adams
>
>>--Original Message--
>>Error 87 from GetProxyAccount on line 604
>>
>>I am trying to set up a regular SQL login which is NOT
a
>>sysadmin with the ability to run xp_cmdshell. It's not
>>the best idea, but I have no choice. I granted it
>>execute permissions on the proc and used
>>xp_sqlagent_proxy_account to point to a login which is
a
>>local admin on the server. Whenever I try to execute
>>xp_cmdshell under that account, I get the error :
>>Msg 50001, Level 1, State 50001
>>xpsql.cpp: Error 87 from GetProxyAccount on line 604
>>A search of KB and a few of these newsgroups turned up
>>nothing. The version number of SQL Server is
08.00.0818
>>(sp3 + security update).
>>.
>.
>|||Did you specify a proxy account? (Do this in EM, right click Agent.)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Chris Clements" <chrisclements@.msn.com> wrote in message
news:3a0201c4a636$c892df90$a501280a@.phx.gbl...
> Error 87 from GetProxyAccount on line 604
>
> I am trying to set up a regular SQL login which is NOT a
> sysadmin with the ability to run xp_cmdshell. It's not
> the best idea, but I have no choice. I granted it
> execute permissions on the proc and used
> xp_sqlagent_proxy_account to point to a login which is a
> local admin on the server. Whenever I try to execute
> xp_cmdshell under that account, I get the error :
> Msg 50001, Level 1, State 50001
> xpsql.cpp: Error 87 from GetProxyAccount on line 604
> A search of KB and a few of these newsgroups turned up
> nothing. The version number of SQL Server is 08.00.0818
> (sp3 + security update).
>|||Yes, I did. I posted this under the security newsgroup
and got the pointer to uncheck the "Only users with
sysadmin" checkbox...duh. Once I did that, the error
message changed to :
xpsql.c: Error 1314 from CreateProcessAsUser on line 492
I found that one in the KB though and am working out the
details now. Thanks.
>--Original Message--
>Did you specify a proxy account? (Do this in EM, right
click Agent.)
>--
>Tibor Karaszi, SQL Server MVP
>http://www.karaszi.com/sqlserver/default.asp
>http://www.solidqualitylearning.com/
>
>"Chris Clements" <chrisclements@.msn.com> wrote in
message
>news:3a0201c4a636$c892df90$a501280a@.phx.gbl...
>> Error 87 from GetProxyAccount on line 604
>>
>> I am trying to set up a regular SQL login which is NOT
a
>> sysadmin with the ability to run xp_cmdshell. It's not
>> the best idea, but I have no choice. I granted it
>> execute permissions on the proc and used
>> xp_sqlagent_proxy_account to point to a login which is
a
>> local admin on the server. Whenever I try to execute
>> xp_cmdshell under that account, I get the error :
>> Msg 50001, Level 1, State 50001
>> xpsql.cpp: Error 87 from GetProxyAccount on line 604
>> A search of KB and a few of these newsgroups turned up
>> nothing. The version number of SQL Server is
08.00.0818
>> (sp3 + security update).
>
>.
>|||Yes, you need to make certain that the service account for Agent has appropriate permissions. You
can search Books Online for below string to find it as well:
"level token"
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<anonymous@.discussions.microsoft.com> wrote in message
news:0d1e01c4a647$bca734e0$a401280a@.phx.gbl...
> Yes, I did. I posted this under the security newsgroup
> and got the pointer to uncheck the "Only users with
> sysadmin" checkbox...duh. Once I did that, the error
> message changed to :
> xpsql.c: Error 1314 from CreateProcessAsUser on line 492
> I found that one in the KB though and am working out the
> details now. Thanks.
>
>>--Original Message--
>>Did you specify a proxy account? (Do this in EM, right
> click Agent.)
>>--
>>Tibor Karaszi, SQL Server MVP
>>http://www.karaszi.com/sqlserver/default.asp
>>http://www.solidqualitylearning.com/
>>
>>"Chris Clements" <chrisclements@.msn.com> wrote in
> message
>>news:3a0201c4a636$c892df90$a501280a@.phx.gbl...
>> Error 87 from GetProxyAccount on line 604
>>
>> I am trying to set up a regular SQL login which is NOT
> a
>> sysadmin with the ability to run xp_cmdshell. It's not
>> the best idea, but I have no choice. I granted it
>> execute permissions on the proc and used
>> xp_sqlagent_proxy_account to point to a login which is
> a
>> local admin on the server. Whenever I try to execute
>> xp_cmdshell under that account, I get the error :
>> Msg 50001, Level 1, State 50001
>> xpsql.cpp: Error 87 from GetProxyAccount on line 604
>> A search of KB and a few of these newsgroups turned up
>> nothing. The version number of SQL Server is
> 08.00.0818
>> (sp3 + security update).
>>
>>.

Tuesday, March 27, 2012

Error 8965

Error 8965

Error 8965

Error 87 from GetProxyAccount on line 604

Error 87 from GetProxyAccount on line 604

Error 207

Blog Archive

About Me