Error about Report builder

I login in my server do report with report builder , when i run report , the error is:

The permissions granted to user 'ADSYSTEC-CZW\users11' are insufficient for performing this operation.

1. The server and my machine are not the same computer,My machine name is adsystec-czw.

2. The reports web site's Authentication is Integrated Windows Authentication.

3. I use the given user(users11) login in belongs to the user groups.

thanks for helps!

Since you are saying you get the error when running the report, I am assuming you have no problem launching Report Builder, viewing Models, and creating and saving a Report to the server. Have you tried running your report directly from the server, after saving it there?

It sounds like your problem may be that the datasource your report uses is not set up correctly. If the data you are trying to retrieve is on a different server than your Report Server, you may need to check the "Use Windows credentials" checkbox in (ie. edit your Datasource in Report Manager).

|||I login in the server's report builder with the URL http://adsystec-czw/reportserver/reportbuilder/reportbuilder.application If I use the server's administrators to login in the server's report server, That error doesn't exist.

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).
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[vbcol=seagreen]
>news:3a0201c4a636$c892df90$a501280a@.phx.gbl...
a[vbcol=seagreen]
a[vbcol=seagreen]
08.00.0818
>
>.
>
|||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...[vbcol=seagreen]
> 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.
>
> click Agent.)
> message
> a
> a
> 08.00.0818

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).
>>
>>.

Error 823

I am attempting to add a windows login to be able to access a database. Whe
n
I try to do this I receive the following error.
Error 823: I/O Error (bad page id) detected during read at offset
0x00000000ae6000 in file e:\program files\microsoft sql
server\mssql\master.mdf
I also receive the following when I run dbcc checkdb on the master database
Server: Msg 8928, Level 16, State 6, Line 1
Object ID 0, index ID 0: Page (1:1331) could not be processed. See other
errors for details.
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:1395). The PageId in the
page header = (0:0).
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 2, index ID 255: Page (1:1332) could not be processed. See other
errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 6, index ID 0: Page (1:1395) could not be processed. See other
errors for details.
Server: Msg 2575, Level 16, State 1, Line 1
IAM page (1:1331) is pointed to by the next pointer of IAM page (0:0) object
ID 40 index ID 2 but was not detected in the scan.
Server: Msg 7965, Level 16, State 1, Line 1
Table error: Could not check object ID 40, index ID 2 due to invalid
allocation (IAM) page(s).
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:1331) in database ID 1 is allocated in the SGAM (1:3) and PFS (1:1),
but was not allocated in any IAM. PFS flags 'IAM_PG MIXED_EXT ALLOCATED
0_PCT_FULL'.
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 3407872, index ID 512, page ID (1:1331). The PageId
in the page header = (1:3126).
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:1330) in database ID 1 is allocated in the SGAM (1:3) and PFS (1:1),
but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED
0_PCT_FULL'.
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 1111693545, index ID 0, page ID (1:1332). The PageId
in the page header = (0:0).
DBCC results for 'master'.
CHECKDB found 1 allocation errors and 1 consistency errors not associated
with any single object.
DBCC results for 'sysobjects'.
There are 1278 rows in 23 pages for object 'sysobjects'.
DBCC results for 'sysindexes'.
There are 103 rows in 4 pages for object 'sysindexes'.
CHECKDB found 0 allocation errors and 1 consistency errors in table
'sysindexes' (object ID 2).
DBCC results for 'syscolumns'.
There are 4958 rows in 94 pages for object 'syscolumns'.
DBCC results for 'systypes'.
There are 26 rows in 1 pages for object 'systypes'.
DBCC results for 'syscomments'.
There are 2232 rows in 1213 pages for object 'syscomments'.
CHECKDB found 0 allocation errors and 1 consistency errors in table
'syscomments' (object ID 6).
DBCC results for 'sysfiles1'.
There are 2 rows in 1 pages for object 'sysfiles1'.
DBCC results for 'syspermissions'.
There are 789 rows in 4 pages for object 'syspermissions'.
DBCC results for 'sysusers'.
There are 16 rows in 1 pages for object 'sysusers'.
DBCC results for 'sysproperties'.
There are 0 rows in 0 pages for object 'sysproperties'.
DBCC results for 'sysdepends'.
There are 5445 rows in 31 pages for object 'sysdepends'.
DBCC results for 'sysreferences'.
There are 0 rows in 0 pages for object 'sysreferences'.
DBCC results for 'sysfulltextcatalogs'.
There are 0 rows in 0 pages for object 'sysfulltextcatalogs'.
DBCC results for 'sysfulltextnotify'.
There are 0 rows in 0 pages for object 'sysfulltextnotify'.
DBCC results for 'sysdatabases'.
There are 14 rows in 1 pages for object 'sysdatabases'.
DBCC results for 'sysxlogins'.
There are 46 rows in 1 pages for object 'sysxlogins'.
DBCC results for 'sysdevices'.
There are 6 rows in 1 pages for object 'sysdevices'.
DBCC results for 'sysmessages'.
There are 3883 rows in 166 pages for object 'sysmessages'.
DBCC results for 'sysconfigures'.
There are 38 rows in 1 pages for object 'sysconfigures'.
DBCC results for 'sysservers'.
There are 3 rows in 1 pages for object 'sysservers'.
CHECKDB found 1 allocation errors and 1 consistency errors in table
'sysservers' (object ID 40).
DBCC results for 'syslanguages'.
There are 33 rows in 3 pages for object 'syslanguages'.
DBCC results for 'syscharsets'.
There are 114 rows in 33 pages for object 'syscharsets'.
DBCC results for 'sysaltfiles'.
There are 28 rows in 6 pages for object 'sysaltfiles'.
DBCC results for 'sysfilegroups'.
There are 1 rows in 1 pages for object 'sysfilegroups'.
CHECKDB found 1 allocation errors and 1 consistency errors in table '(Object
ID 3407872)' (object ID 3407872).
DBCC results for 'spt_monitor'.
There are 1 rows in 1 pages for object 'spt_monitor'.
DBCC results for 'spt_values'.
There are 730 rows in 7 pages for object 'spt_values'.
DBCC results for 'spt_fallback_db'.
There are 0 rows in 0 pages for object 'spt_fallback_db'.
DBCC results for 'spt_fallback_dev'.
There are 0 rows in 0 pages for object 'spt_fallback_dev'.
DBCC results for 'spt_fallback_usg'.
There are 0 rows in 0 pages for object 'spt_fallback_usg'.
CHECKDB found 1 allocation errors and 0 consistency errors in table '(Object
ID 538976288)' (object ID 538976288).
DBCC results for 'spt_provider_types'.
There are 25 rows in 1 pages for object 'spt_provider_types'.
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object
ID 1111693545)' (object ID 1111693545).
DBCC results for 'spt_datatype_info_ext'.
There are 10 rows in 1 pages for object 'spt_datatype_info_ext'.
DBCC results for 'MSreplication_options'.
There are 2 rows in 1 pages for object 'MSreplication_options'.
DBCC results for 'spt_datatype_info'.
There are 36 rows in 1 pages for object 'spt_datatype_info'.
DBCC results for 'spt_server_info'.
There are 29 rows in 1 pages for object 'spt_server_info'.
CHECKDB found 4 allocation errors and 6 consistency errors in database
'master'.
repair_allow_data_loss is the minimum repair level for the errors found by
DBCC CHECKDB (master ).
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
How can I correct these errors?Before fixing it, you should check your hardware and look
for issues with your disk subsystem. Check the event logs on
the server and look for any other system errors that may
have occurred around the same time.
After fixing any hardware issues, then you would need to
restore the last known good backup of the master database.
-Sue
On Wed, 29 Mar 2006 10:08:01 -0800, rleamey
<rleamey@.discussions.microsoft.com> wrote:

>I am attempting to add a windows login to be able to access a database. Wh
en
>I try to do this I receive the following error.
>Error 823: I/O Error (bad page id) detected during read at offset
>0x00000000ae6000 in file e:\program files\microsoft sql
>server\mssql\master.mdf
>I also receive the following when I run dbcc checkdb on the master database
>Server: Msg 8928, Level 16, State 6, Line 1
>Object ID 0, index ID 0: Page (1:1331) could not be processed. See other
>errors for details.
>Server: Msg 8909, Level 16, State 1, Line 1
>Table error: Object ID 0, index ID 0, page ID (1:1395). The PageId in the
>page header = (0:0).
>Server: Msg 8928, Level 16, State 1, Line 1
>Object ID 2, index ID 255: Page (1:1332) could not be processed. See other
>errors for details.
>Server: Msg 8928, Level 16, State 1, Line 1
>Object ID 6, index ID 0: Page (1:1395) could not be processed. See other
>errors for details.
>Server: Msg 2575, Level 16, State 1, Line 1
>IAM page (1:1331) is pointed to by the next pointer of IAM page (0:0) objec
t
>ID 40 index ID 2 but was not detected in the scan.
>Server: Msg 7965, Level 16, State 1, Line 1
>Table error: Could not check object ID 40, index ID 2 due to invalid
>allocation (IAM) page(s).
>Server: Msg 8906, Level 16, State 1, Line 1
>Page (1:1331) in database ID 1 is allocated in the SGAM (1:3) and PFS (1:1)
,
>but was not allocated in any IAM. PFS flags 'IAM_PG MIXED_EXT ALLOCATED
>0_PCT_FULL'.
>Server: Msg 8909, Level 16, State 1, Line 1
>Table error: Object ID 3407872, index ID 512, page ID (1:1331). The PageId
>in the page header = (1:3126).
>Server: Msg 8906, Level 16, State 1, Line 1
>Page (1:1330) in database ID 1 is allocated in the SGAM (1:3) and PFS (1:1)
,
>but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED
>0_PCT_FULL'.
>Server: Msg 8909, Level 16, State 1, Line 1
>Table error: Object ID 1111693545, index ID 0, page ID (1:1332). The PageId
>in the page header = (0:0).
>DBCC results for 'master'.
>CHECKDB found 1 allocation errors and 1 consistency errors not associated
>with any single object.
>DBCC results for 'sysobjects'.
>There are 1278 rows in 23 pages for object 'sysobjects'.
>DBCC results for 'sysindexes'.
>There are 103 rows in 4 pages for object 'sysindexes'.
>CHECKDB found 0 allocation errors and 1 consistency errors in table
>'sysindexes' (object ID 2).
>DBCC results for 'syscolumns'.
>There are 4958 rows in 94 pages for object 'syscolumns'.
>DBCC results for 'systypes'.
>There are 26 rows in 1 pages for object 'systypes'.
>DBCC results for 'syscomments'.
>There are 2232 rows in 1213 pages for object 'syscomments'.
>CHECKDB found 0 allocation errors and 1 consistency errors in table
>'syscomments' (object ID 6).
>DBCC results for 'sysfiles1'.
>There are 2 rows in 1 pages for object 'sysfiles1'.
>DBCC results for 'syspermissions'.
>There are 789 rows in 4 pages for object 'syspermissions'.
>DBCC results for 'sysusers'.
>There are 16 rows in 1 pages for object 'sysusers'.
>DBCC results for 'sysproperties'.
>There are 0 rows in 0 pages for object 'sysproperties'.
>DBCC results for 'sysdepends'.
>There are 5445 rows in 31 pages for object 'sysdepends'.
>DBCC results for 'sysreferences'.
>There are 0 rows in 0 pages for object 'sysreferences'.
>DBCC results for 'sysfulltextcatalogs'.
>There are 0 rows in 0 pages for object 'sysfulltextcatalogs'.
>DBCC results for 'sysfulltextnotify'.
>There are 0 rows in 0 pages for object 'sysfulltextnotify'.
>DBCC results for 'sysdatabases'.
>There are 14 rows in 1 pages for object 'sysdatabases'.
>DBCC results for 'sysxlogins'.
>There are 46 rows in 1 pages for object 'sysxlogins'.
>DBCC results for 'sysdevices'.
>There are 6 rows in 1 pages for object 'sysdevices'.
>DBCC results for 'sysmessages'.
>There are 3883 rows in 166 pages for object 'sysmessages'.
>DBCC results for 'sysconfigures'.
>There are 38 rows in 1 pages for object 'sysconfigures'.
>DBCC results for 'sysservers'.
>There are 3 rows in 1 pages for object 'sysservers'.
>CHECKDB found 1 allocation errors and 1 consistency errors in table
>'sysservers' (object ID 40).
>DBCC results for 'syslanguages'.
>There are 33 rows in 3 pages for object 'syslanguages'.
>DBCC results for 'syscharsets'.
>There are 114 rows in 33 pages for object 'syscharsets'.
>DBCC results for 'sysaltfiles'.
>There are 28 rows in 6 pages for object 'sysaltfiles'.
>DBCC results for 'sysfilegroups'.
>There are 1 rows in 1 pages for object 'sysfilegroups'.
>CHECKDB found 1 allocation errors and 1 consistency errors in table '(Objec
t
>ID 3407872)' (object ID 3407872).
>DBCC results for 'spt_monitor'.
>There are 1 rows in 1 pages for object 'spt_monitor'.
>DBCC results for 'spt_values'.
>There are 730 rows in 7 pages for object 'spt_values'.
>DBCC results for 'spt_fallback_db'.
>There are 0 rows in 0 pages for object 'spt_fallback_db'.
>DBCC results for 'spt_fallback_dev'.
>There are 0 rows in 0 pages for object 'spt_fallback_dev'.
>DBCC results for 'spt_fallback_usg'.
>There are 0 rows in 0 pages for object 'spt_fallback_usg'.
>CHECKDB found 1 allocation errors and 0 consistency errors in table '(Objec
t
>ID 538976288)' (object ID 538976288).
>DBCC results for 'spt_provider_types'.
>There are 25 rows in 1 pages for object 'spt_provider_types'.
>CHECKDB found 0 allocation errors and 1 consistency errors in table '(Objec
t
>ID 1111693545)' (object ID 1111693545).
>DBCC results for 'spt_datatype_info_ext'.
>There are 10 rows in 1 pages for object 'spt_datatype_info_ext'.
>DBCC results for 'MSreplication_options'.
>There are 2 rows in 1 pages for object 'MSreplication_options'.
>DBCC results for 'spt_datatype_info'.
>There are 36 rows in 1 pages for object 'spt_datatype_info'.
>DBCC results for 'spt_server_info'.
>There are 29 rows in 1 pages for object 'spt_server_info'.
>CHECKDB found 4 allocation errors and 6 consistency errors in database
>'master'.
>repair_allow_data_loss is the minimum repair level for the errors found by
>DBCC CHECKDB (master ).
>DBCC execution completed. If DBCC printed error messages, contact your
>system administrator.
>How can I correct these errors?|||Would there be anyway to fix it if we did not have a good copy of the backup
?
"Sue Hoegemeier" wrote:

> Before fixing it, you should check your hardware and look
> for issues with your disk subsystem. Check the event logs on
> the server and look for any other system errors that may
> have occurred around the same time.
> After fixing any hardware issues, then you would need to
> restore the last known good backup of the master database.
> -Sue
> On Wed, 29 Mar 2006 10:08:01 -0800, rleamey
> <rleamey@.discussions.microsoft.com> wrote:
>
>|||Restoring is the best option. If that's not an option, you
can rebuild master using the rebuildm.exe
You can find more information on how to do this in the books
online topic: Rebuilding the master Database
-Sue
On Thu, 30 Mar 2006 05:09:02 -0800, rleamey
<rleamey@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Would there be anyway to fix it if we did not have a good copy of the backu
p?
>"Sue Hoegemeier" wrote:
>

Error 2571 - not permission to run DBCC TRACEON

Hi,
I am trying to connect to SQL Server 2005 via Excel/ODBC. (ODBC Test IS
successfull) and get the following error after entering Login ID and Password:
Connection failed:
SQLState: '37000'
SQL Server Error: 2571
.....does not have permission to run DBCC TRACEON
Security setup on SQL Server seems to be fine (I can connect to SQL Server
from Reporting Services on same Login/Password).
Any idears?
Best regards,
Soren
To run DBCC Traceon you requires membership in the sysadmin fixed
server role.
Regards
Amish
|||That did it! Thanks !!!
"amish" wrote:

> To run DBCC Traceon you requires membership in the sysadmin fixed
> server role.
>
> Regards
> Amish
>
|||I had the same problem, but there are multiple users who use that
spreadsheet using Windows authentication. I did not want any of them to
be sysadmins. They only had SLECT permissions to certain tables. In my
case, deleting the Application name (from the SQL Server Login dialog)
fixed it. You need to click the Options button on the dialog to see
this. The application name seems to be an issue if it has certain
characters (like =AE in Microsoft=AE Query). Depending on the MS Office
version, the default value may be Microsoft=AE Query/MS Office XP/?.
You can also programmatically change the connection string (and even
the command text if necessary). Here is a sample.
'ChangeConnection
Sub ChangeConnection()
Dim sh As Worksheet
Dim qt As QueryTable
Dim sConnection As String
For Each sh In ActiveWorkbook.Sheets
For Each qt In sh.QueryTables
'Show current connectionstring
MsgBox ("Tab: " & sh.Name & vbCr & " Current Connection: "
& vbCr & qt.Connection)
'Show current query
MsgBox ("Tab: " & sh.Name & vbCr & "Current Query: " & vbCr
& qt.CommandText)
'Change Connection
qt.Connection =3D "ODBC;DRIVER=3DSQL
Server;SERVER=3Dmyserver;DATABASE=3DmyDB;Trusted_C onnection=3DYes;APP=3DExc=
el_TopCustomers;"
'Change Qry text (the owner for instance)
qt.CommandText =3D Replace(qt.CommandText, "DB.dbo.",
"DB.Me")
qt.SavePassword =3D False
'Show new connectionstring
MsgBox ("Tab: " & sh.Name & vbCr & "Connection: " & vbCr &
qt.Connection)
'Show new query
MsgBox ("Tab: " & sh.Name & vbCr & "Query: " & vbCr &
qt.CommandText)
Next qt
Next sh
End Sub
|||I have the exact same problem using Excel 97/MS-Query8. I tried your
suggestion, it did not work. I am still getting the error.
Ade
"preddy" wrote:

> I had the same problem, but there are multiple users who use that
> spreadsheet using Windows authentication. I did not want any of them to
> be sysadmins. They only had SLECT permissions to certain tables. In my
> case, deleting the Application name (from the SQL Server Login dialog)
> fixed it. You need to click the Options button on the dialog to see
> this. The application name seems to be an issue if it has certain
> characters (like ? in Microsoft? Query). Depending on the MS Office
> version, the default value may be Microsoft? Query/MS Office XP/?.
> You can also programmatically change the connection string (and even
> the command text if necessary). Here is a sample.
> 'ChangeConnection
> Sub ChangeConnection()
> Dim sh As Worksheet
> Dim qt As QueryTable
> Dim sConnection As String
> For Each sh In ActiveWorkbook.Sheets
> For Each qt In sh.QueryTables
> 'Show current connectionstring
> MsgBox ("Tab: " & sh.Name & vbCr & " Current Connection: "
> & vbCr & qt.Connection)
> 'Show current query
> MsgBox ("Tab: " & sh.Name & vbCr & "Current Query: " & vbCr
> & qt.CommandText)
> 'Change Connection
> qt.Connection = "ODBC;DRIVER=SQL
> Server;SERVER=myserver;DATABASE=myDB;Trusted_Conne ction=Yes;APP=Excel_TopCustomers;"
> 'Change Qry text (the owner for instance)
> qt.CommandText = Replace(qt.CommandText, "DB.dbo.",
> "DB.Me")
> qt.SavePassword = False
> 'Show new connectionstring
> MsgBox ("Tab: " & sh.Name & vbCr & "Connection: " & vbCr &
> qt.Connection)
> 'Show new query
> MsgBox ("Tab: " & sh.Name & vbCr & "Query: " & vbCr &
> qt.CommandText)
> Next qt
> Next sh
> End Sub
>
|||Sorry my mistake, it does work. You have to replace the string "Microsoft?
Query" with something else.
Ade
"Ade" wrote:
[vbcol=seagreen]
> I have the exact same problem using Excel 97/MS-Query8. I tried your
> suggestion, it did not work. I am still getting the error.
> --
> Ade
>
> "preddy" wrote:

Error 2571 - not permission to run DBCC TRACEON

Hi,
I am trying to connect to SQL Server 2005 via Excel/ODBC. (ODBC Test IS
successfull) and get the following error after entering Login ID and Passwor
d:
Connection failed:
SQLState: '37000'
SQL Server Error: 2571
....does not have permission to run DBCC TRACEON
Security setup on SQL Server seems to be fine (I can connect to SQL Server
from Reporting Services on same Login/Password).
Any idears?
Best regards,
SorenTo run DBCC Traceon you requires membership in the sysadmin fixed
server role.
Regards
Amish|||That did it! Thanks !!!
"amish" wrote:

> To run DBCC Traceon you requires membership in the sysadmin fixed
> server role.
>
> Regards
> Amish
>|||I had the same problem, but there are multiple users who use that
spreadsheet using Windows authentication. I did not want any of them to
be sysadmins. They only had SLECT permissions to certain tables. In my
case, deleting the Application name (from the SQL Server Login dialog)
fixed it. You need to click the Options button on the dialog to see
this. The application name seems to be an issue if it has certain
characters (like =AE in Microsoft=AE Query). Depending on the MS Office
version, the default value may be Microsoft=AE Query/MS Office XP/'.
You can also programmatically change the connection string (and even
the command text if necessary). Here is a sample.
'ChangeConnection
Sub ChangeConnection()
Dim sh As Worksheet
Dim qt As QueryTable
Dim sConnection As String
For Each sh In ActiveWorkbook.Sheets
For Each qt In sh.QueryTables
'Show current connectionstring
MsgBox ("Tab: " & sh.Name & vbCr & " Current Connection: "
& vbCr & qt.Connection)
'Show current query
MsgBox ("Tab: " & sh.Name & vbCr & "Current Query: " & vbCr
& qt.CommandText)
'Change Connection
qt.Connection =3D "ODBC;DRIVER=3DSQL
Server;SERVER=3Dmyserver;DATABASE=3DmyDB
;Trusted_Connection=3DYes;APP=3DExc=
el_TopCustomers;"
'Change Qry text (the owner for instance)
qt.CommandText =3D Replace(qt.CommandText, "DB.dbo.",
"DB.Me")
qt.SavePassword =3D False
'Show new connectionstring
MsgBox ("Tab: " & sh.Name & vbCr & "Connection: " & vbCr &
qt.Connection)
'Show new query
MsgBox ("Tab: " & sh.Name & vbCr & "Query: " & vbCr &
qt.CommandText)
Next qt
Next sh
End Sub|||I have the exact same problem using Excel 97/MS-Query8. I tried your
suggestion, it did not work. I am still getting the error.
--
Ade
"preddy" wrote:

> I had the same problem, but there are multiple users who use that
> spreadsheet using Windows authentication. I did not want any of them to
> be sysadmins. They only had SLECT permissions to certain tables. In my
> case, deleting the Application name (from the SQL Server Login dialog)
> fixed it. You need to click the Options button on the dialog to see
> this. The application name seems to be an issue if it has certain
> characters (like ? in Microsoft? Query). Depending on the MS Office
> version, the default value may be Microsoft? Query/MS Office XP/'.
> You can also programmatically change the connection string (and even
> the command text if necessary). Here is a sample.
> 'ChangeConnection
> Sub ChangeConnection()
> Dim sh As Worksheet
> Dim qt As QueryTable
> Dim sConnection As String
> For Each sh In ActiveWorkbook.Sheets
> For Each qt In sh.QueryTables
> 'Show current connectionstring
> MsgBox ("Tab: " & sh.Name & vbCr & " Current Connection: "
> & vbCr & qt.Connection)
> 'Show current query
> MsgBox ("Tab: " & sh.Name & vbCr & "Current Query: " & vbCr
> & qt.CommandText)
> 'Change Connection
> qt.Connection = "ODBC;DRIVER=SQL
> Server;SERVER=myserver;DATABASE=myDB;Tru
sted_Connection=Yes;APP=Excel_TopC
ustomers;"
> 'Change Qry text (the owner for instance)
> qt.CommandText = Replace(qt.CommandText, "DB.dbo.",
> "DB.Me")
> qt.SavePassword = False
> 'Show new connectionstring
> MsgBox ("Tab: " & sh.Name & vbCr & "Connection: " & vbCr &
> qt.Connection)
> 'Show new query
> MsgBox ("Tab: " & sh.Name & vbCr & "Query: " & vbCr &
> qt.CommandText)
> Next qt
> Next sh
> End Sub
>|||Sorry my mistake, it does work. You have to replace the string "Microsoft?
Query" with something else.
--
Ade
"Ade" wrote:
[vbcol=seagreen]
> I have the exact same problem using Excel 97/MS-Query8. I tried your
> suggestion, it did not work. I am still getting the error.
> --
> Ade
>
> "preddy" wrote:
>

Error 2571 - not permission to run DBCC TRACEON

Hi,
I am trying to connect to SQL Server 2005 via Excel/ODBC. (ODBC Test IS
successfull) and get the following error after entering Login ID and Password:
Connection failed:
SQLState: '37000'
SQL Server Error: 2571
....does not have permission to run DBCC TRACEON
Security setup on SQL Server seems to be fine (I can connect to SQL Server
from Reporting Services on same Login/Password).
Any idears?
Best regards,
SorenTo run DBCC Traceon you requires membership in the sysadmin fixed
server role.
Regards
Amish|||That did it! Thanks !!!
"amish" wrote:
> To run DBCC Traceon you requires membership in the sysadmin fixed
> server role.
>
> Regards
> Amish
>|||I had the same problem, but there are multiple users who use that
spreadsheet using Windows authentication. I did not want any of them to
be sysadmins. They only had SLECT permissions to certain tables. In my
case, deleting the Application name (from the SQL Server Login dialog)
fixed it. You need to click the Options button on the dialog to see
this. The application name seems to be an issue if it has certain
characters (like =AE in Microsoft=AE Query). Depending on the MS Office
version, the default value may be Microsoft=AE Query/MS Office XP/'.
You can also programmatically change the connection string (and even
the command text if necessary). Here is a sample.
'ChangeConnection
Sub ChangeConnection()
Dim sh As Worksheet
Dim qt As QueryTable
Dim sConnection As String
For Each sh In ActiveWorkbook.Sheets
For Each qt In sh.QueryTables
'Show current connectionstring
MsgBox ("Tab: " & sh.Name & vbCr & " Current Connection: "
& vbCr & qt.Connection)
'Show current query
MsgBox ("Tab: " & sh.Name & vbCr & "Current Query: " & vbCr
& qt.CommandText)
'Change Connection
qt.Connection =3D "ODBC;DRIVER=3DSQL
Server;SERVER=3Dmyserver;DATABASE=3DmyDB;Trusted_Connection=3DYes;APP=3DExc=el_TopCustomers;"
'Change Qry text (the owner for instance)
qt.CommandText =3D Replace(qt.CommandText, "DB.dbo.",
"DB.Me")
qt.SavePassword =3D False
'Show new connectionstring
MsgBox ("Tab: " & sh.Name & vbCr & "Connection: " & vbCr &
qt.Connection)
'Show new query
MsgBox ("Tab: " & sh.Name & vbCr & "Query: " & vbCr &
qt.CommandText)
Next qt
Next sh
End Sub|||I have the exact same problem using Excel 97/MS-Query8. I tried your
suggestion, it did not work. I am still getting the error.
--
Ade
"preddy" wrote:
> I had the same problem, but there are multiple users who use that
> spreadsheet using Windows authentication. I did not want any of them to
> be sysadmins. They only had SLECT permissions to certain tables. In my
> case, deleting the Application name (from the SQL Server Login dialog)
> fixed it. You need to click the Options button on the dialog to see
> this. The application name seems to be an issue if it has certain
> characters (like ® in Microsoft® Query). Depending on the MS Office
> version, the default value may be Microsoft® Query/MS Office XP/'.
> You can also programmatically change the connection string (and even
> the command text if necessary). Here is a sample.
> 'ChangeConnection
> Sub ChangeConnection()
> Dim sh As Worksheet
> Dim qt As QueryTable
> Dim sConnection As String
> For Each sh In ActiveWorkbook.Sheets
> For Each qt In sh.QueryTables
> 'Show current connectionstring
> MsgBox ("Tab: " & sh.Name & vbCr & " Current Connection: "
> & vbCr & qt.Connection)
> 'Show current query
> MsgBox ("Tab: " & sh.Name & vbCr & "Current Query: " & vbCr
> & qt.CommandText)
> 'Change Connection
> qt.Connection = "ODBC;DRIVER=SQL
> Server;SERVER=myserver;DATABASE=myDB;Trusted_Connection=Yes;APP=Excel_TopCustomers;"
> 'Change Qry text (the owner for instance)
> qt.CommandText = Replace(qt.CommandText, "DB.dbo.",
> "DB.Me")
> qt.SavePassword = False
> 'Show new connectionstring
> MsgBox ("Tab: " & sh.Name & vbCr & "Connection: " & vbCr &
> qt.Connection)
> 'Show new query
> MsgBox ("Tab: " & sh.Name & vbCr & "Query: " & vbCr &
> qt.CommandText)
> Next qt
> Next sh
> End Sub
>|||Sorry my mistake, it does work. You have to replace the string "Microsoft®
Query" with something else.
--
Ade
"Ade" wrote:
> I have the exact same problem using Excel 97/MS-Query8. I tried your
> suggestion, it did not work. I am still getting the error.
> --
> Ade
>
> "preddy" wrote:
> > I had the same problem, but there are multiple users who use that
> > spreadsheet using Windows authentication. I did not want any of them to
> > be sysadmins. They only had SLECT permissions to certain tables. In my
> > case, deleting the Application name (from the SQL Server Login dialog)
> > fixed it. You need to click the Options button on the dialog to see
> > this. The application name seems to be an issue if it has certain
> > characters (like ® in Microsoft® Query). Depending on the MS Office
> > version, the default value may be Microsoft® Query/MS Office XP/'.
> >
> > You can also programmatically change the connection string (and even
> > the command text if necessary). Here is a sample.
> >
> > 'ChangeConnection
> > Sub ChangeConnection()
> >
> > Dim sh As Worksheet
> > Dim qt As QueryTable
> >
> > Dim sConnection As String
> >
> > For Each sh In ActiveWorkbook.Sheets
> > For Each qt In sh.QueryTables
> >
> > 'Show current connectionstring
> > MsgBox ("Tab: " & sh.Name & vbCr & " Current Connection: "
> > & vbCr & qt.Connection)
> > 'Show current query
> > MsgBox ("Tab: " & sh.Name & vbCr & "Current Query: " & vbCr
> > & qt.CommandText)
> >
> > 'Change Connection
> > qt.Connection = "ODBC;DRIVER=SQL
> > Server;SERVER=myserver;DATABASE=myDB;Trusted_Connection=Yes;APP=Excel_TopCustomers;"
> >
> > 'Change Qry text (the owner for instance)
> > qt.CommandText = Replace(qt.CommandText, "DB.dbo.",
> > "DB.Me")
> >
> > qt.SavePassword = False
> >
> > 'Show new connectionstring
> > MsgBox ("Tab: " & sh.Name & vbCr & "Connection: " & vbCr &
> > qt.Connection)
> > 'Show new query
> > MsgBox ("Tab: " & sh.Name & vbCr & "Query: " & vbCr &
> > qt.CommandText)
> >
> > Next qt
> > Next sh
> >
> > End Sub
> >
> >

Error 21776: After creating new login

I run this code:
EXEC DATA0003.dbo.sp_addlogin 'test','pwd'
EXEC DATA0003.dbo.sp_grantdbaccess 'test'
EXEC DATA0003.dbo.sp_addrolemember 'Full','test'
When I go into enterprise and go to the properties of
login and to Data Access Tab and select the Data0003
(which is checked) I get this error:
Error 21776:[SQL-DMO]The name 'test' was not found in the
Users collection. If the name is a qualified name, use
[] to separte various parts of the name, and try again.
The only way I found to get rid of the error is to go to
DATA0003 and select the users and refresh the list.
Then, their is no problem.
But, I would like to not have to go refresh user
everytime I add a login.
I would appreciate any help.
Thanks in advance,
BobEM uses SQLDMO and caches a lot of the information you see. In general this
is a good thing. I don't believe there is any way to alter the behaviour in
Enterprise Manager. See this note from BOL about SQLDMO collections
"To enable more efficient processing, SQL-DMO caches much of the information
about SQL Server components referenced by objects maintained in a
collection. When component data is cached, administrative activity of
another SQL Server session is not visible to the SQL-DMO session. The
Refresh method queries the organization server, filling the collection with
the most up-to-date component information."
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Bob Haines" <bhaines@.pahousegop.com> wrote in message
news:164f901c4173c$4c0e51e0$a501280a@.phx
.gbl...
> I run this code:
> EXEC DATA0003.dbo.sp_addlogin 'test','pwd'
> EXEC DATA0003.dbo.sp_grantdbaccess 'test'
> EXEC DATA0003.dbo.sp_addrolemember 'Full','test'
> When I go into enterprise and go to the properties of
> login and to Data Access Tab and select the Data0003
> (which is checked) I get this error:
> Error 21776:[SQL-DMO]The name 'test' was not found in the
> Users collection. If the name is a qualified name, use
> [] to separte various parts of the name, and try again.
> The only way I found to get rid of the error is to go to
> DATA0003 and select the users and refresh the list.
> Then, their is no problem.
> But, I would like to not have to go refresh user
> everytime I add a login.
> I would appreciate any help.
> Thanks in advance,
> Bob|||try this
type:
use DATA0003
before :
EXEC DATA0003.dbo.sp_addlogin 'test','pwd'
EXEC DATA0003.dbo.sp_grantdbaccess 'test'
EXEC DATA0003.dbo.sp_addrolemember 'Full','test'
and execute it. this may solve the problem

quote:

---

Originally posted by Jasper Smith
EM uses SQLDMO and caches a lot of the information you see. In general this
is a good thing. I don't believe there is any way to alter the behaviour in
Enterprise Manager. See this note from BOL about SQLDMO collections
"To enable more efficient processing, SQL-DMO caches much of the information
about SQL Server components referenced by objects maintained in a
collection. When component data is cached, administrative activity of
another SQL Server session is not visible to the SQL-DMO session. The
Refresh method queries the organization server, filling the collection with
the most up-to-date component information."
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Bob Haines" <bhaines@.pahousegop.com> wrote in message
news:164f901c4173c$4c0e51e0$a501280a@.phx
.gbl...
> I run this code:
> EXEC DATA0003.dbo.sp_addlogin 'test','pwd'
> EXEC DATA0003.dbo.sp_grantdbaccess 'test'
> EXEC DATA0003.dbo.sp_addrolemember 'Full','test'
> When I go into enterprise and go to the properties of
> login and to Data Access Tab and select the Data0003
> (which is checked) I get this error:
> Error 21776:[SQL-DMO]The name 'test' was not found in the
> Users collection. If the name is a qualified name, use
> [] to separte various parts of the name, and try again.
> The only way I found to get rid of the error is to go to
> DATA0003 and select the users and refresh the list.
> Then, their is no problem.
> But, I would like to not have to go refresh user
> everytime I add a login.
> I would appreciate any help.
> Thanks in advance,
> Bob

---