Could not setup Web Service Identity --> Error Code 80070003

Hello!
I′m trying to setup a Report Server on my SQL 2005 server. In Reporting Services Configuration Manager I get an error when i try to create the Web Sevice Identity

ReportServicesConfigUI.WMIProvider.WMIProviderException: An unknown error has occurred in the WMI Provider. Error Code 80070003
at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.SetWebServiceIdentity(String applicationPool)

The default website contains an office sharepoint 2007 beta solution if that could cause the error..

Would be real grateful for some hints...

Regards

Erik B

Have you found a solution to this? I'm getting the same error after moving the Identities from one Website to another.|||

8007003 is ERROR_PATH_NOT_FOUND. Are you on Win2K3? I suspect this has something to do with ASP.NET setup. Either the WMI provider could not open the ASP.NET registry keys, or it could not find the machine.config file. Make sure you have run aspnet_regiis -i -enable.

If it doesn't work, I would start using regmon and filemon to looks for suspicious errors that could lead to 8007003. Unfortunately at this point the error code is too general to provide any clue.

|||

Hi... I reinstalled SQL 2005 and then it worked fine.. However I think it had to do something with the Encryption Keys... Gwired if I were you I′d delete those from the Reporting Services Configuration Manager, create new ones and then setup a Web Service Identity.

Have a nice day

/Erk

|||

I ran into the same problem, and discovered the issue had to do with the fact that I installed SQL Server 2005, SP1, SP2 and THEN installed Reporting Services. Because I had installed SP2 before Reporting Services, SP2 was not applied to Reporting Services.

The only other thing of note that happened was that when I tried to run the User Provisioning Tool after installing SP2 I got a 'object not set to an instance of an object error'. I didn't really think anything about it at the time, but I think it was only because I figured I'd find the problem down the road. I guess you can say that I did.

Could not setup Web Service Identity --> Error Code 80070003

Hello!
I′m trying to setup a Report Server on my SQL 2005 server. In Reporting Services Configuration Manager I get an error when i try to create the Web Sevice Identity

ReportServicesConfigUI.WMIProvider.WMIProviderException: An unknown error has occurred in the WMI Provider. Error Code 80070003
at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.SetWebServiceIdentity(String applicationPool)

The default website contains an office sharepoint 2007 beta solution if that could cause the error..

Would be real grateful for some hints...

Regards

Erik B

Have you found a solution to this? I'm getting the same error after moving the Identities from one Website to another.|||

8007003 is ERROR_PATH_NOT_FOUND. Are you on Win2K3? I suspect this has something to do with ASP.NET setup. Either the WMI provider could not open the ASP.NET registry keys, or it could not find the machine.config file. Make sure you have run aspnet_regiis -i -enable.

If it doesn't work, I would start using regmon and filemon to looks for suspicious errors that could lead to 8007003. Unfortunately at this point the error code is too general to provide any clue.

|||

Hi... I reinstalled SQL 2005 and then it worked fine.. However I think it had to do something with the Encryption Keys... Gwired if I were you I′d delete those from the Reporting Services Configuration Manager, create new ones and then setup a Web Service Identity.

Have a nice day

/Erk

|||

I ran into the same problem, and discovered the issue had to do with the fact that I installed SQL Server 2005, SP1, SP2 and THEN installed Reporting Services. Because I had installed SP2 before Reporting Services, SP2 was not applied to Reporting Services.

The only other thing of note that happened was that when I tried to run the User Provisioning Tool after installing SP2 I got a 'object not set to an instance of an object error'. I didn't really think anything about it at the time, but I think it was only because I figured I'd find the problem down the road. I guess you can say that I did.

Could not get into server instance

Hi,
I ran Enterprise manager, but I could not get into my
server. It said that it was not running or to check '
the config, which is fine and is Windows Only Authentication.
Here is the weird and scary part. ZoneAlarm had an alert
at the same time. The alert was asking for Management Console
to use USERINIT.EXE to access 192.5.6.30DNS.
This resolves to a.gtld-servers.net which is part of Verisign.
I refused this outbound access and kept retrying to get into
my server in Enterprise. No luck. I then decided to go ahead
and give outbound access. Next time I tried to get into
my server I was able to.
Does anyone know what's up?
I figured that maybe I should change all my logins?
But, does this show that there is a breach of my system?
There has been another odd thing where WSCRIPT.EXE has
been asking for access to DNS servers. That I keep blocked.
I am pretty sure that is a trojan, but do you think this is this related ?
Thanks for any advice.
FoxAs a very first step -- scan your computer for virus or Trojans, I think you
may have a serious exploit on your hands.
Steve
"Fox" <fox @. connexions .net> wrote in message
news:e9HspB2wDHA.2408@.tk2msftngp13.phx.gbl...

quote:

---

> Hi,
> I ran Enterprise manager, but I could not get into my
> server. It said that it was not running or to check '
> the config, which is fine and is Windows Only Authentication.
> Here is the weird and scary part. ZoneAlarm had an alert
> at the same time. The alert was asking for Management Console
> to use USERINIT.EXE to access 192.5.6.30DNS.
> This resolves to a.gtld-servers.net which is part of Verisign.
> I refused this outbound access and kept retrying to get into
> my server in Enterprise. No luck. I then decided to go ahead
> and give outbound access. Next time I tried to get into
> my server I was able to.
> Does anyone know what's up?
> I figured that maybe I should change all my logins?
> But, does this show that there is a breach of my system?
> There has been another odd thing where WSCRIPT.EXE has
> been asking for access to DNS servers. That I keep blocked.
> I am pretty sure that is a trojan, but do you think this is this related ?
> Thanks for any advice.
> Fox
>

---

|||I have already scanned several times and have come up with nothing.
I changed all logins related to admin.
A few weeks ago I found entries in my firewall to allow 3 IPs
access. I saw them in there once before and deleted them.
This time I block them entirely from access. It seems I've been
playing a cat and mouse game for a while. But I cannot find
the source and a re-install is out of the question. There were
a few other things that happend earlier this year. I don't
know what to do next to try to find the source of this.
Regards,
Fox
"Steve Thompson" <SteveThompson@.nomail.please> wrote in message
news:eZcXtC$wDHA.3116@.TK2MSFTNGP11.phx.gbl...

quote:

---

> As a very first step -- scan your computer for virus or Trojans, I think

---

you

quote:

---

> may have a serious exploit on your hands.
> Steve
>
> "Fox" <fox @. connexions .net> wrote in message
> news:e9HspB2wDHA.2408@.tk2msftngp13.phx.gbl...
?[QUOTE]
>

---

|||What are you using as a firewall?
Is this a "live" SQL Server on the internet?
What type of applications are connecting to this Server?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Could not find stored procedure

User creates a sp and the same is visible in the
enterprise manager. The user has rights to execute also.
However the isql gives the above mentioned error even for
sa!!!
No clue please help.Hi Sandip,
Make sure that you are in the right database when trying to execute the
stored procedure. Unless you specify a database with isql, it will use the
default database for that user, which is usually master.
--
Jacco Schalkwijk
SQL Server MVP
"Sandip" <bsandipk@.hotmail.com> wrote in message
news:072701c40022$9dd31140$3501280a@.phx.gbl...
> User creates a sp and the same is visible in the
> enterprise manager. The user has rights to execute also.
> However the isql gives the above mentioned error even for
> sa!!!
> No clue please help.|||Hi!
The user that creates the procedure is owner of te procedure, if it was not
created with a specific owner (i.e. CREATE PROCEDURE owner.name). The sa
loin is mapped to a specific db user dbo, so SQL Server searches dbo.name
procedure. Eithercreate all n+bjects wit dbo as owner, or use two-part name
when using it.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Sandip" <bsandipk@.hotmail.com> wrote in message
news:072701c40022$9dd31140$3501280a@.phx.gbl...
> User creates a sp and the same is visible in the
> enterprise manager. The user has rights to execute also.
> However the isql gives the above mentioned error even for
> sa!!!
> No clue please help.|||Hi ,
To add on to Dejan Sarka post , Simply execute the below query in Query
analyzer
select user_name(uid) as Creator,name from sysobjects where name ='procedure_name'
Replace the procedure_name with actual name.
Incase the the creator name is not DBO then use sp_changeobjectowner (refer
books online) to change the object owner.
Thanks
Hari
MCDBA
"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si> wrote in
message news:ugW0lfCAEHA.2660@.TK2MSFTNGP10.phx.gbl...
> Hi!
> The user that creates the procedure is owner of te procedure, if it was
not
> created with a specific owner (i.e. CREATE PROCEDURE owner.name). The sa
> loin is mapped to a specific db user dbo, so SQL Server searches dbo.name
> procedure. Eithercreate all n+bjects wit dbo as owner, or use two-part
name
> when using it.
> --
> Dejan Sarka, SQL Server MVP
> Associate Mentor
> Solid Quality Learning
> More than just Training
> www.SolidQualityLearning.com
> "Sandip" <bsandipk@.hotmail.com> wrote in message
> news:072701c40022$9dd31140$3501280a@.phx.gbl...
> > User creates a sp and the same is visible in the
> > enterprise manager. The user has rights to execute also.
> >
> > However the isql gives the above mentioned error even for
> > sa!!!
> >
> > No clue please help.
>

Could not find stored procedure

User creates a sp and the same is visible in the
enterprise manager. The user has rights to execute also.
However the isql gives the above mentioned error even for
sa!!!
No clue please help.Hi Sandip,
Make sure that you are in the right database when trying to execute the
stored procedure. Unless you specify a database with isql, it will use the
default database for that user, which is usually master.
Jacco Schalkwijk
SQL Server MVP
"Sandip" <bsandipk@.hotmail.com> wrote in message
news:072701c40022$9dd31140$3501280a@.phx.gbl...
> User creates a sp and the same is visible in the
> enterprise manager. The user has rights to execute also.
> However the isql gives the above mentioned error even for
> sa!!!
> No clue please help.|||Hi!
The user that creates the procedure is owner of te procedure, if it was not
created with a specific owner (i.e. CREATE PROCEDURE owner.name). The sa
loin is mapped to a specific db user dbo, so SQL Server searches dbo.name
procedure. Eithercreate all n+bjects wit dbo as owner, or use two-part name
when using it.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Sandip" <bsandipk@.hotmail.com> wrote in message
news:072701c40022$9dd31140$3501280a@.phx.gbl...
> User creates a sp and the same is visible in the
> enterprise manager. The user has rights to execute also.
> However the isql gives the above mentioned error even for
> sa!!!
> No clue please help.|||Hi ,
To add on to Dejan Sarka post , Simply execute the below query in Query
analyzer
select user_name(uid) as Creator,name from sysobjects where name =
'procedure_name'
Replace the procedure_name with actual name.
Incase the the creator name is not DBO then use sp_changeobjectowner (refer
books online) to change the object owner.
Thanks
Hari
MCDBA
"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si> wrote in
message news:ugW0lfCAEHA.2660@.TK2MSFTNGP10.phx.gbl...
> Hi!
> The user that creates the procedure is owner of te procedure, if it was
not
> created with a specific owner (i.e. CREATE PROCEDURE owner.name). The sa
> loin is mapped to a specific db user dbo, so SQL Server searches dbo.name
> procedure. Eithercreate all n+bjects wit dbo as owner, or use two-part
name
> when using it.
> --
> Dejan Sarka, SQL Server MVP
> Associate Mentor
> Solid Quality Learning
> More than just Training
> www.SolidQualityLearning.com
> "Sandip" <bsandipk@.hotmail.com> wrote in message
> news:072701c40022$9dd31140$3501280a@.phx.gbl...
>

could not disable publishing and distribution

hello All,

i am trying to delete publications in SQL 2000, SP4 and getting this
error:

SQL Server Enterprise Manager could not disable publishing and distribution on '<publishername>'.

Error 3724 : cannot drop the procedure
'dbo.sp_sel_F854ED4CD7EA4399EFDB9697F4E24A10_pal' because itis being used for replication.

Thanks and Regards

Kanna

Run sp_removedbreplication in the published database.

Corrupted table?

We have a SQL Server 2000 database with a table we cannot delete. We first
try from Enterprise Manager, and then tried through VB code, and a stored
procedure, but nothing is able to delete the table. Is there anything else
to try?
Thank you.DROP TABLE <table name>.
But what is the error you get?
--
Jacco Schalkwijk
SQL Server MVP
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:%23kZjFGgQFHA.1236@.TK2MSFTNGP14.phx.gbl...
> We have a SQL Server 2000 database with a table we cannot delete. We first
> try from Enterprise Manager, and then tried through VB code, and a stored
> procedure, but nothing is able to delete the table. Is there anything else
> to try?
> Thank you.
>|||Have you tried running DBCC CHECKTABLE?
--
Andrew J. Kelly SQL MVP
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:%23kZjFGgQFHA.1236@.TK2MSFTNGP14.phx.gbl...
> We have a SQL Server 2000 database with a table we cannot delete. We first
> try from Enterprise Manager, and then tried through VB code, and a stored
> procedure, but nothing is able to delete the table. Is there anything else
> to try?
> Thank you.
>|||Hi,
First Execute DBCC CHECKTABLE(TABLENAME), If it gives error then try with
REPAIR OPTIONS. See DBCC CHECKTABLE command in books online.
Take a backup of Database prior to execute DBCC with Repair options.
Thanks
Hari
SQL Server MVP
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:%23kZjFGgQFHA.1236@.TK2MSFTNGP14.phx.gbl...
> We have a SQL Server 2000 database with a table we cannot delete. We first
> try from Enterprise Manager, and then tried through VB code, and a stored
> procedure, but nothing is able to delete the table. Is there anything else
> to try?
> Thank you.
>|||Actually, there is no error. Enterprise Manager just freezes, and we have to
stop the task. Query Analyzer, doing the DROP TABLE reacts the same way. We
give it several minutes to come back. It shouldnt' take more than 10 minutes
to drop a table.Maybe we can let it run ...'
"Jacco Schalkwijk" <jacco.please.reply@.to.newsgroups.mvps.org.invalid> wrote
in message news:eYQLnegQFHA.2132@.TK2MSFTNGP09.phx.gbl...
> DROP TABLE <table name>.
> But what is the error you get?
> --
> Jacco Schalkwijk
> SQL Server MVP
>
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:%23kZjFGgQFHA.1236@.TK2MSFTNGP14.phx.gbl...
> > We have a SQL Server 2000 database with a table we cannot delete. We
first
> > try from Enterprise Manager, and then tried through VB code, and a
stored
> > procedure, but nothing is able to delete the table. Is there anything
else
> > to try?
> >
> > Thank you.
> >
> >
>|||That is not what MS recommends. You should not repair without first
determining root cause of the errors and then you should use a backup as the
best way to recover from the error (unless the only repair needed is to
rebuild indexes). Primairly though, you need to work out why the error
happened in the first place.
Regards
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:#rmRpFkQFHA.2876@.TK2MSFTNGP09.phx.gbl...
> Hi,
> First Execute DBCC CHECKTABLE(TABLENAME), If it gives error then try with
> REPAIR OPTIONS. See DBCC CHECKTABLE command in books online.
> Take a backup of Database prior to execute DBCC with Repair options.
> Thanks
> Hari
> SQL Server MVP
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:%23kZjFGgQFHA.1236@.TK2MSFTNGP14.phx.gbl...
> > We have a SQL Server 2000 database with a table we cannot delete. We
first
> > try from Enterprise Manager, and then tried through VB code, and a
stored
> > procedure, but nothing is able to delete the table. Is there anything
else
> > to try?
> >
> > Thank you.
> >
> >
>|||There is no error, we just can't drop the table. We've tried to delete the
table inside Enterprise Manager, from a VB program, and from Query Analyzer.
Each time when the command executes to drop the table, the program freezes,
and we have to stop the task. Maybe we should wait longer (10 minutes) to
see if an error eventually occurs, but after about 10 mins. there is no
error and the program stops responding to the request to drop the table.
I ran DBCC checkTable and there are no reported errors.
ANy ideas? Thanks!
"Paul S Randal [MS]" <prandal@.online.microsoft.com> wrote in message
news:uTAONbERFHA.1392@.TK2MSFTNGP10.phx.gbl...
> That is not what MS recommends. You should not repair without first
> determining root cause of the errors and then you should use a backup as
the
> best way to recover from the error (unless the only repair needed is to
> rebuild indexes). Primairly though, you need to work out why the error
> happened in the first place.
> Regards
> --
> Paul Randal
> Dev Lead, Microsoft SQL Server Storage Engine
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:#rmRpFkQFHA.2876@.TK2MSFTNGP09.phx.gbl...
> > Hi,
> >
> > First Execute DBCC CHECKTABLE(TABLENAME), If it gives error then try
with
> > REPAIR OPTIONS. See DBCC CHECKTABLE command in books online.
> >
> > Take a backup of Database prior to execute DBCC with Repair options.
> >
> > Thanks
> > Hari
> > SQL Server MVP
> >
> > "Dean J Garrett" <info@.amuletc.com> wrote in message
> > news:%23kZjFGgQFHA.1236@.TK2MSFTNGP14.phx.gbl...
> > > We have a SQL Server 2000 database with a table we cannot delete. We
> first
> > > try from Enterprise Manager, and then tried through VB code, and a
> stored
> > > procedure, but nothing is able to delete the table. Is there anything
> else
> > > to try?
> > >
> > > Thank you.
> > >
> > >
> >
> >
>|||Blocking? Did you check using sp_who, sp_who2 etc?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Dean J Garrett" <info@.amuletc.com> wrote in message news:epK3ZkFRFHA.1236@.TK2MSFTNGP14.phx.gbl...
> There is no error, we just can't drop the table. We've tried to delete the
> table inside Enterprise Manager, from a VB program, and from Query Analyzer.
> Each time when the command executes to drop the table, the program freezes,
> and we have to stop the task. Maybe we should wait longer (10 minutes) to
> see if an error eventually occurs, but after about 10 mins. there is no
> error and the program stops responding to the request to drop the table.
> I ran DBCC checkTable and there are no reported errors.
> ANy ideas? Thanks!
>
> "Paul S Randal [MS]" <prandal@.online.microsoft.com> wrote in message
> news:uTAONbERFHA.1392@.TK2MSFTNGP10.phx.gbl...
>> That is not what MS recommends. You should not repair without first
>> determining root cause of the errors and then you should use a backup as
> the
>> best way to recover from the error (unless the only repair needed is to
>> rebuild indexes). Primairly though, you need to work out why the error
>> happened in the first place.
>> Regards
>> --
>> Paul Randal
>> Dev Lead, Microsoft SQL Server Storage Engine
>> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
>> news:#rmRpFkQFHA.2876@.TK2MSFTNGP09.phx.gbl...
>> > Hi,
>> >
>> > First Execute DBCC CHECKTABLE(TABLENAME), If it gives error then try
> with
>> > REPAIR OPTIONS. See DBCC CHECKTABLE command in books online.
>> >
>> > Take a backup of Database prior to execute DBCC with Repair options.
>> >
>> > Thanks
>> > Hari
>> > SQL Server MVP
>> >
>> > "Dean J Garrett" <info@.amuletc.com> wrote in message
>> > news:%23kZjFGgQFHA.1236@.TK2MSFTNGP14.phx.gbl...
>> > > We have a SQL Server 2000 database with a table we cannot delete. We
>> first
>> > > try from Enterprise Manager, and then tried through VB code, and a
>> stored
>> > > procedure, but nothing is able to delete the table. Is there anything
>> else
>> > > to try?
>> > >
>> > > Thank you.
>> > >
>> > >
>> >
>> >
>>
>

Corrupted table?

We have a SQL Server 2000 database with a table we cannot delete. We first
try from Enterprise Manager, and then tried through VB code, and a stored
procedure, but nothing is able to delete the table. Is there anything else
to try?
Thank you.
DROP TABLE <table name>.
But what is the error you get?
Jacco Schalkwijk
SQL Server MVP
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:%23kZjFGgQFHA.1236@.TK2MSFTNGP14.phx.gbl...
> We have a SQL Server 2000 database with a table we cannot delete. We first
> try from Enterprise Manager, and then tried through VB code, and a stored
> procedure, but nothing is able to delete the table. Is there anything else
> to try?
> Thank you.
>
|||Have you tried running DBCC CHECKTABLE?
Andrew J. Kelly SQL MVP
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:%23kZjFGgQFHA.1236@.TK2MSFTNGP14.phx.gbl...
> We have a SQL Server 2000 database with a table we cannot delete. We first
> try from Enterprise Manager, and then tried through VB code, and a stored
> procedure, but nothing is able to delete the table. Is there anything else
> to try?
> Thank you.
>
|||Hi,
First Execute DBCC CHECKTABLE(TABLENAME), If it gives error then try with
REPAIR OPTIONS. See DBCC CHECKTABLE command in books online.
Take a backup of Database prior to execute DBCC with Repair options.
Thanks
Hari
SQL Server MVP
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:%23kZjFGgQFHA.1236@.TK2MSFTNGP14.phx.gbl...
> We have a SQL Server 2000 database with a table we cannot delete. We first
> try from Enterprise Manager, and then tried through VB code, and a stored
> procedure, but nothing is able to delete the table. Is there anything else
> to try?
> Thank you.
>
|||Actually, there is no error. Enterprise Manager just freezes, and we have to
stop the task. Query Analyzer, doing the DROP TABLE reacts the same way. We
give it several minutes to come back. It shouldnt' take more than 10 minutes
to drop a table.Maybe we can let it run ...?
"Jacco Schalkwijk" <jacco.please.reply@.to.newsgroups.mvps.org.invalid > wrote
in message news:eYQLnegQFHA.2132@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> DROP TABLE <table name>.
> But what is the error you get?
> --
> Jacco Schalkwijk
> SQL Server MVP
>
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:%23kZjFGgQFHA.1236@.TK2MSFTNGP14.phx.gbl...
first[vbcol=seagreen]
stored[vbcol=seagreen]
else
>
|||That is not what MS recommends. You should not repair without first
determining root cause of the errors and then you should use a backup as the
best way to recover from the error (unless the only repair needed is to
rebuild indexes). Primairly though, you need to work out why the error
happened in the first place.
Regards
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:#rmRpFkQFHA.2876@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Hi,
> First Execute DBCC CHECKTABLE(TABLENAME), If it gives error then try with
> REPAIR OPTIONS. See DBCC CHECKTABLE command in books online.
> Take a backup of Database prior to execute DBCC with Repair options.
> Thanks
> Hari
> SQL Server MVP
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:%23kZjFGgQFHA.1236@.TK2MSFTNGP14.phx.gbl...
first[vbcol=seagreen]
stored[vbcol=seagreen]
else
>
|||There is no error, we just can't drop the table. We've tried to delete the
table inside Enterprise Manager, from a VB program, and from Query Analyzer.
Each time when the command executes to drop the table, the program freezes,
and we have to stop the task. Maybe we should wait longer (10 minutes) to
see if an error eventually occurs, but after about 10 mins. there is no
error and the program stops responding to the request to drop the table.
I ran DBCC checkTable and there are no reported errors.
ANy ideas? Thanks!
"Paul S Randal [MS]" <prandal@.online.microsoft.com> wrote in message
news:uTAONbERFHA.1392@.TK2MSFTNGP10.phx.gbl...
> That is not what MS recommends. You should not repair without first
> determining root cause of the errors and then you should use a backup as
the
> best way to recover from the error (unless the only repair needed is to
> rebuild indexes). Primairly though, you need to work out why the error
> happened in the first place.
> Regards
> --
> Paul Randal
> Dev Lead, Microsoft SQL Server Storage Engine
> This posting is provided "AS IS" with no warranties, and confers no
rights.[vbcol=seagreen]
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:#rmRpFkQFHA.2876@.TK2MSFTNGP09.phx.gbl...
with
> first
> stored
> else
>
|||Blocking? Did you check using sp_who, sp_who2 etc?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Dean J Garrett" <info@.amuletc.com> wrote in message news:epK3ZkFRFHA.1236@.TK2MSFTNGP14.phx.gbl...
> There is no error, we just can't drop the table. We've tried to delete the
> table inside Enterprise Manager, from a VB program, and from Query Analyzer.
> Each time when the command executes to drop the table, the program freezes,
> and we have to stop the task. Maybe we should wait longer (10 minutes) to
> see if an error eventually occurs, but after about 10 mins. there is no
> error and the program stops responding to the request to drop the table.
> I ran DBCC checkTable and there are no reported errors.
> ANy ideas? Thanks!
>
> "Paul S Randal [MS]" <prandal@.online.microsoft.com> wrote in message
> news:uTAONbERFHA.1392@.TK2MSFTNGP10.phx.gbl...
> the
> rights.
> with
>

Corrupted table?

We have a SQL Server 2000 database with a table we cannot delete. We first
try from Enterprise Manager, and then tried through VB code, and a stored
procedure, but nothing is able to delete the table. Is there anything else
to try?
Thank you.DROP TABLE <table name>.
But what is the error you get?
Jacco Schalkwijk
SQL Server MVP
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:%23kZjFGgQFHA.1236@.TK2MSFTNGP14.phx.gbl...
> We have a SQL Server 2000 database with a table we cannot delete. We first
> try from Enterprise Manager, and then tried through VB code, and a stored
> procedure, but nothing is able to delete the table. Is there anything else
> to try?
> Thank you.
>|||Have you tried running DBCC CHECKTABLE?
Andrew J. Kelly SQL MVP
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:%23kZjFGgQFHA.1236@.TK2MSFTNGP14.phx.gbl...
> We have a SQL Server 2000 database with a table we cannot delete. We first
> try from Enterprise Manager, and then tried through VB code, and a stored
> procedure, but nothing is able to delete the table. Is there anything else
> to try?
> Thank you.
>|||Hi,
First Execute DBCC CHECKTABLE(TABLENAME), If it gives error then try with
REPAIR OPTIONS. See DBCC CHECKTABLE command in books online.
Take a backup of Database prior to execute DBCC with Repair options.
Thanks
Hari
SQL Server MVP
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:%23kZjFGgQFHA.1236@.TK2MSFTNGP14.phx.gbl...
> We have a SQL Server 2000 database with a table we cannot delete. We first
> try from Enterprise Manager, and then tried through VB code, and a stored
> procedure, but nothing is able to delete the table. Is there anything else
> to try?
> Thank you.
>|||Actually, there is no error. Enterprise Manager just freezes, and we have to
stop the task. Query Analyzer, doing the DROP TABLE reacts the same way. We
give it several minutes to come back. It shouldnt' take more than 10 minutes
to drop a table.Maybe we can let it run ...'
"Jacco Schalkwijk" <jacco.please.reply@.to.newsgroups.mvps.org.invalid> wrote
in message news:eYQLnegQFHA.2132@.TK2MSFTNGP09.phx.gbl...
> DROP TABLE <table name>.
> But what is the error you get?
> --
> Jacco Schalkwijk
> SQL Server MVP
>
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:%23kZjFGgQFHA.1236@.TK2MSFTNGP14.phx.gbl...
first[vbcol=seagreen]
stored[vbcol=seagreen]
else[vbcol=seagreen]
>|||That is not what MS recommends. You should not repair without first
determining root cause of the errors and then you should use a backup as the
best way to recover from the error (unless the only repair needed is to
rebuild indexes). Primairly though, you need to work out why the error
happened in the first place.
Regards
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:#rmRpFkQFHA.2876@.TK2MSFTNGP09.phx.gbl...
> Hi,
> First Execute DBCC CHECKTABLE(TABLENAME), If it gives error then try with
> REPAIR OPTIONS. See DBCC CHECKTABLE command in books online.
> Take a backup of Database prior to execute DBCC with Repair options.
> Thanks
> Hari
> SQL Server MVP
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:%23kZjFGgQFHA.1236@.TK2MSFTNGP14.phx.gbl...
first[vbcol=seagreen]
stored[vbcol=seagreen]
else[vbcol=seagreen]
>|||There is no error, we just can't drop the table. We've tried to delete the
table inside Enterprise Manager, from a VB program, and from Query Analyzer.
Each time when the command executes to drop the table, the program freezes,
and we have to stop the task. Maybe we should wait longer (10 minutes) to
see if an error eventually occurs, but after about 10 mins. there is no
error and the program stops responding to the request to drop the table.
I ran DBCC checkTable and there are no reported errors.
ANy ideas? Thanks!
"Paul S Randal [MS]" <prandal@.online.microsoft.com> wrote in message
news:uTAONbERFHA.1392@.TK2MSFTNGP10.phx.gbl...
> That is not what MS recommends. You should not repair without first
> determining root cause of the errors and then you should use a backup as
the
> best way to recover from the error (unless the only repair needed is to
> rebuild indexes). Primairly though, you need to work out why the error
> happened in the first place.
> Regards
> --
> Paul Randal
> Dev Lead, Microsoft SQL Server Storage Engine
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:#rmRpFkQFHA.2876@.TK2MSFTNGP09.phx.gbl...
with[vbcol=seagreen]
> first
> stored
> else
>|||Blocking? Did you check using sp_who, sp_who2 etc?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Dean J Garrett" <info@.amuletc.com> wrote in message news:epK3ZkFRFHA.1236@.TK2MSFTNGP14.phx.
gbl...
> There is no error, we just can't drop the table. We've tried to delete the
> table inside Enterprise Manager, from a VB program, and from Query Analyze
r.
> Each time when the command executes to drop the table, the program freezes
,
> and we have to stop the task. Maybe we should wait longer (10 minutes) to
> see if an error eventually occurs, but after about 10 mins. there is no
> error and the program stops responding to the request to drop the table.
> I ran DBCC checkTable and there are no reported errors.
> ANy ideas? Thanks!
>
> "Paul S Randal [MS]" <prandal@.online.microsoft.com> wrote in message
> news:uTAONbERFHA.1392@.TK2MSFTNGP10.phx.gbl...
> the
> rights.
> with
>

Corrupted Table removal problem

I have a table that I can no longer make design changes too, remove
altogether, or view all rows for. Enterprise manager just hangs. I can do
a view top 1 record, but not view all. I'm testing some stored procedures
to fill ntext fields using writetext and seem to be corrupting it somehow.
All other tables and database work fine ... problems occur here only.
Ideas on how to fix or move forward with this.
Thanks,
Andrew
Your best bet is usually to restore from a previous good backup. If this is
a table in which the data is not critical or can be rebuilt you might want
to take a look at DBCC CHECKTABLE in BooksOnLine.
Andrew J. Kelly SQL MVP
"Andrew Jones" <ajones@.kvmhc.org> wrote in message
news:10fdjev1ikfg8ac@.corp.supernews.com...
> I have a table that I can no longer make design changes too, remove
> altogether, or view all rows for. Enterprise manager just hangs. I can
do
> a view top 1 record, but not view all. I'm testing some stored procedures
> to fill ntext fields using writetext and seem to be corrupting it somehow.
> All other tables and database work fine ... problems occur here only.
> Ideas on how to fix or move forward with this.
> Thanks,
> Andrew
>

Corrupted table

When I try and examine a table in one of my MS SQL Server 2000 databases I
get the following error from Enterprise Manager:
[Microsoft][ODBC..] I/O error (bad page ID) detected during read at offset
0X00000000038000 in file ...MDF
How do I go about fixing this?
Thanks,"Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in
news:O4XR1rJWFHA.3280@.TK2MSFTNGP09.phx.gbl:
> I/O error (bad page ID) detected during read at offset
Run...
DBCC CHECKDB
--
Regards
JTC ^..^|||Hi
In Query Analyzer, run DBCC CHECKDB to get an idea of how widespread the
corruption is. Check all the DBs on the server.
Start looking for you most recent backup.
If the corruption is not too bad, you might be able to run DBCC CECKDB
REPAIR_REBUILD
else, you would need to use DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS (but you may
loose data).
Generally, corruption is caused by hardware faults.
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/
"Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
news:O4XR1rJWFHA.3280@.TK2MSFTNGP09.phx.gbl...
> When I try and examine a table in one of my MS SQL Server 2000 databases I
> get the following error from Enterprise Manager:
> [Microsoft][ODBC..] I/O error (bad page ID) detected during read at offset
> 0X00000000038000 in file ...MDF
> How do I go about fixing this?
> Thanks,
>
>|||Also look at http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
--
--
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/
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:OgvrizJWFHA.3320@.TK2MSFTNGP12.phx.gbl...
> Hi
> In Query Analyzer, run DBCC CHECKDB to get an idea of how widespread the
> corruption is. Check all the DBs on the server.
> Start looking for you most recent backup.
> If the corruption is not too bad, you might be able to run DBCC CECKDB
> REPAIR_REBUILD
> else, you would need to use DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS (but you
> may loose data).
> Generally, corruption is caused by hardware faults.
> 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/
> "Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
> news:O4XR1rJWFHA.3280@.TK2MSFTNGP09.phx.gbl...
>> When I try and examine a table in one of my MS SQL Server 2000 databases
>> I
>> get the following error from Enterprise Manager:
>> [Microsoft][ODBC..] I/O error (bad page ID) detected during read at
>> offset
>> 0X00000000038000 in file ...MDF
>> How do I go about fixing this?
>> Thanks,
>>
>|||Thanks Mike. I was able to Export the table SQL definition, delete the table
and then recreate it from the script.
- Andrew
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:uzMoM3JWFHA.584@.TK2MSFTNGP15.phx.gbl...
> Also look at http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
> --
> --
> 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/
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:OgvrizJWFHA.3320@.TK2MSFTNGP12.phx.gbl...
> > Hi
> >
> > In Query Analyzer, run DBCC CHECKDB to get an idea of how widespread the
> > corruption is. Check all the DBs on the server.
> >
> > Start looking for you most recent backup.
> >
> > If the corruption is not too bad, you might be able to run DBCC CECKDB
> > REPAIR_REBUILD
> > else, you would need to use DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS (but you
> > may loose data).
> >
> > Generally, corruption is caused by hardware faults.
> >
> > 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/
> >
> > "Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
> > news:O4XR1rJWFHA.3280@.TK2MSFTNGP09.phx.gbl...
> >> When I try and examine a table in one of my MS SQL Server 2000
databases
> >> I
> >> get the following error from Enterprise Manager:
> >>
> >> [Microsoft][ODBC..] I/O error (bad page ID) detected during read at
> >> offset
> >> 0X00000000038000 in file ...MDF
> >>
> >> How do I go about fixing this?
> >>
> >> Thanks,
> >>
> >>
> >>
> >
> >
>|||Hi Andrew,
Now you should be in good shape, but still run a DBCC CHECKDB(DBNAME) and
ensure that database is in good shape.
Note:
As part of your routine maintenance please schedule a DBCC CHECKDB for all
production databases. This will help you to identify issues earlier.
Thanks
Hari
SQL Server MVP
"Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
news:e2s03xOWFHA.628@.tk2msftngp13.phx.gbl...
> Thanks Mike. I was able to Export the table SQL definition, delete the
> table
> and then recreate it from the script.
> - Andrew
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:uzMoM3JWFHA.584@.TK2MSFTNGP15.phx.gbl...
>> Also look at http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
>> --
>> --
>> 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/
>> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
>> news:OgvrizJWFHA.3320@.TK2MSFTNGP12.phx.gbl...
>> > Hi
>> >
>> > In Query Analyzer, run DBCC CHECKDB to get an idea of how widespread
>> > the
>> > corruption is. Check all the DBs on the server.
>> >
>> > Start looking for you most recent backup.
>> >
>> > If the corruption is not too bad, you might be able to run DBCC CECKDB
>> > REPAIR_REBUILD
>> > else, you would need to use DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS (but
>> > you
>> > may loose data).
>> >
>> > Generally, corruption is caused by hardware faults.
>> >
>> > 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/
>> >
>> > "Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
>> > news:O4XR1rJWFHA.3280@.TK2MSFTNGP09.phx.gbl...
>> >> When I try and examine a table in one of my MS SQL Server 2000
> databases
>> >> I
>> >> get the following error from Enterprise Manager:
>> >>
>> >> [Microsoft][ODBC..] I/O error (bad page ID) detected during read at
>> >> offset
>> >> 0X00000000038000 in file ...MDF
>> >>
>> >> How do I go about fixing this?
>> >>
>> >> Thanks,
>> >>
>> >>
>> >>
>> >
>> >
>>
>|||Andrew,
A key here that Mike mentioned is "Generally, corruption is caused by
hardware faults".
now that you solved the immediate issue of data\table corruption. The next
step is to figure out "WHY".
If you dont do this, your data is likely going to become corrupt again very
soon.
I suspect a disk is going haywire on you or your RAID Controller is kicking
the bucket.
I just went through this with two different customers. One turned out to be
disk, hte other turned out to be RAID Controller.
cheers
Greg Jackson
PDX, Oregon|||I'll do that.
- Andrew
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:efyvtDTWFHA.3280@.TK2MSFTNGP09.phx.gbl...
> Hi Andrew,
> Now you should be in good shape, but still run a DBCC CHECKDB(DBNAME) and
> ensure that database is in good shape.
> Note:
> As part of your routine maintenance please schedule a DBCC CHECKDB for all
> production databases. This will help you to identify issues earlier.
> Thanks
> Hari
> SQL Server MVP
> "Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
> news:e2s03xOWFHA.628@.tk2msftngp13.phx.gbl...
> > Thanks Mike. I was able to Export the table SQL definition, delete the
> > table
> > and then recreate it from the script.
> >
> > - Andrew
> > "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> > news:uzMoM3JWFHA.584@.TK2MSFTNGP15.phx.gbl...
> >> Also look at
http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
> >>
> >> --
> >> --
> >> 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/
> >>
> >> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> >> news:OgvrizJWFHA.3320@.TK2MSFTNGP12.phx.gbl...
> >> > Hi
> >> >
> >> > In Query Analyzer, run DBCC CHECKDB to get an idea of how widespread
> >> > the
> >> > corruption is. Check all the DBs on the server.
> >> >
> >> > Start looking for you most recent backup.
> >> >
> >> > If the corruption is not too bad, you might be able to run DBCC
CECKDB
> >> > REPAIR_REBUILD
> >> > else, you would need to use DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS (but
> >> > you
> >> > may loose data).
> >> >
> >> > Generally, corruption is caused by hardware faults.
> >> >
> >> > 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/
> >> >
> >> > "Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
> >> > news:O4XR1rJWFHA.3280@.TK2MSFTNGP09.phx.gbl...
> >> >> When I try and examine a table in one of my MS SQL Server 2000
> > databases
> >> >> I
> >> >> get the following error from Enterprise Manager:
> >> >>
> >> >> [Microsoft][ODBC..] I/O error (bad page ID) detected during read at
> >> >> offset
> >> >> 0X00000000038000 in file ...MDF
> >> >>
> >> >> How do I go about fixing this?
> >> >>
> >> >> Thanks,
> >> >>
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >
> >
>|||This is on a development machine rather than a production server so I
suspect it may have been roughly rebooted periodically. There hasn't been
any other evidence of disk problems so i am just backing up frequently for
now.
Thanks,
Andrew
"pdxJaxon" <GregoryAJackson@.Hotmail.com> wrote in message
news:OPRePnVWFHA.2128@.TK2MSFTNGP15.phx.gbl...
> Andrew,
> A key here that Mike mentioned is "Generally, corruption is caused by
> hardware faults".
> now that you solved the immediate issue of data\table corruption. The next
> step is to figure out "WHY".
> If you dont do this, your data is likely going to become corrupt again
very
> soon.
> I suspect a disk is going haywire on you or your RAID Controller is
kicking
> the bucket.
> I just went through this with two different customers. One turned out to
be
> disk, hte other turned out to be RAID Controller.
>
> cheers
>
> Greg Jackson
> PDX, Oregon
>

Corrupted Database Error 3456

After a simple reboot of the file server one of the data bases in the Sql Server 2k of the SBS 2000 appears in enterprise manager as supect. I decided to detach and again to attach the db. I have never been abble to attach the db, and I received teh following error:

Error 3456: could not redo log record(8433:539:79), for transaction ID:(0:0), on page(1:32352), database 'PRICAI2005' (9). Page: LSN=(8432:16085:7), type=11.log: UpCode=5, context 11, PrevPageLsN:(8433:378:3).

I think I have read all kind of information about this error, I tried all th sugestions in the multiples articles I saw, but untill now, the problem remains the same. And no, I haven't any backup of this DB. Is there anyone who knows a solution for my problem. I will be deeply gratefull.

Thanks,

Jos Dinis

suporte.aospc@.sapo.pt

Hi Jose,

i would suggest you to refer the best article i have found for restoring status of suspect database , it was by Svetlana Kuvshinkova
http://www.myitforum.com/articles/18/view.asp?id=7381

and also refer below threads

http://sqljunkies.com/Forums/ShowPost.aspx?PostID=11566

and http://www.sql-server-performance.com/forum/topic.asp?TOPIC_ID=11689&#55322

HTH

Hemantgiri S. Goswami

|||

Do you have a backup for this database?

KBA http://support.microsoft.com/kb/831950 & http://support.microsoft.com/kb/826433 fyi.