Cannot find mdf files: moved

Showing posts with label moved. Show all posts

Sunday, March 25, 2012

Cannot rebuild full text catalogs

Recently moved database and full text catalogs to new server with SQL Server
2000 sp3a/SBS 2003 sp1
I am having problems rebuilding and repopulating the fulltext catalogs
restored to the new server.
The message I encounter is "Error 7635: The Microsoft Search cannot be
administered under the present user account".
I understand from the link I have been referred to
"http://support.microsoft.com/default.aspx?scid=kb;en-us;277549" states that
the service logon was changed through the control panel instead of the
Enterprise Manager therefore the service login for SQL Server does not have
administrative priviledges over the MSSearch service.
None of the service logins were changed through the control panel
I have tried the workround as suggested in the link but I still get the same
error message when I try to rebuild the full text catalog.
Any of you MVP's with another approach or suggestions to solve this problem?What account is MSSearch running under? It must be running under the local
system account. If it is not change it, you can change it through the
services applet in Control panel - Administrative Tasks.
Check that the builtin\Admins group is in the sysadmin role, and if not do
the following
use master
go
exec sp_grantlogin N'NT Authority\System'
exec sp_defaultdb N'NT Authority\System', N'master'
exec sp_defaultlanguage N'NT Authority\System','us_english'
exec sp_addsrvrolemember N'NT Authority\System', sysadmin
goThen change the SQL Server account to a the local system account in
Enterprise manger, right click on it and select properties and then select
the security tab and make the modifcation here, bounce it and the repeat the
process to have it run under a local adminstrators account.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Jarvis Allen" <JarvisAllen@.discussions.microsoft.com> wrote in message
news:DA108BC7-E94F-4391-A71F-505CF6D42E0A@.microsoft.com...
> Recently moved database and full text catalogs to new server with SQL
> Server
> 2000 sp3a/SBS 2003 sp1
> I am having problems rebuilding and repopulating the fulltext catalogs
> restored to the new server.
> The message I encounter is "Error 7635: The Microsoft Search cannot be
> administered under the present user account".
> I understand from the link I have been referred to
> "http://support.microsoft.com/default.aspx?scid=kb;en-us;277549" states
> that
> the service logon was changed through the control panel instead of the
> Enterprise Manager therefore the service login for SQL Server does not
> have
> administrative priviledges over the MSSearch service.
> None of the service logins were changed through the control panel
> I have tried the workround as suggested in the link but I still get the
> same
> error message when I try to rebuild the full text catalog.
> Any of you MVP's with another approach or suggestions to solve this
> problem?|||"Hilary Cotter" wrote:
> What account is MSSearch running under? It must be running under the local
> system account. If it is not change it, you can change it through the
> services applet in Control panel - Administrative Tasks.
> Check that the builtin\Admins group is in the sysadmin role, and if not do
> the following
> use master
> go
> exec sp_grantlogin N'NT Authority\System'
> exec sp_defaultdb N'NT Authority\System', N'master'
> exec sp_defaultlanguage N'NT Authority\System','us_english'
> exec sp_addsrvrolemember N'NT Authority\System', sysadmin
> goThen change the SQL Server account to a the local system account in
> Enterprise manger, right click on it and select properties and then select
> the security tab and make the modifcation here, bounce it and the repeat the
> process to have it run under a local adminstrators account.
>
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Jarvis Allen" <JarvisAllen@.discussions.microsoft.com> wrote in message
> news:DA108BC7-E94F-4391-A71F-505CF6D42E0A@.microsoft.com...
> > Recently moved database and full text catalogs to new server with SQL
> > Server
> > 2000 sp3a/SBS 2003 sp1
> > I am having problems rebuilding and repopulating the fulltext catalogs
> > restored to the new server.
> > The message I encounter is "Error 7635: The Microsoft Search cannot be
> > administered under the present user account".
> >
> > I understand from the link I have been referred to
> > "http://support.microsoft.com/default.aspx?scid=kb;en-us;277549" states
> > that
> > the service logon was changed through the control panel instead of the
> > Enterprise Manager therefore the service login for SQL Server does not
> > have
> > administrative priviledges over the MSSearch service.
> > None of the service logins were changed through the control panel
> >
> > I have tried the workround as suggested in the link but I still get the
> > same
> > error message when I try to rebuild the full text catalog.
> >
> > Any of you MVP's with another approach or suggestions to solve this
> > problem?
> Thank you for your reply Hilary
The MS Search service is using the local system logon and built in admin has
the role of sydadmin.
I followed your instructions which was similiar to the instruction I
followed in the link i was reffered to inmy original message.
Unfortunately the your instructions I followed failed to cure the 7635 error
(cannot administer MS Search service under present user account).
Are ther any other slutions to try?
>|||"Jarvis Allen" wrote:
I have tried suggestions by Hilary and the problem still persists.
The MS Search is running under the local system account as it should which
seems to be the problem.
The problem seems to be getting the administer rights over the MS Search
service.
The SQL Server does start with the Domain Admin user.
For some reason the Domain Admin user can administer the MS Search service
even though I have used the suggested way to gain admin rights over the MS
Search!
Any other ideas from you SQL experts?
>
> "Hilary Cotter" wrote:
> > What account is MSSearch running under? It must be running under the local
> > system account. If it is not change it, you can change it through the
> > services applet in Control panel - Administrative Tasks.
> >
> > Check that the builtin\Admins group is in the sysadmin role, and if not do
> > the following
> >
> > use master
> > go
> > exec sp_grantlogin N'NT Authority\System'
> > exec sp_defaultdb N'NT Authority\System', N'master'
> > exec sp_defaultlanguage N'NT Authority\System','us_english'
> > exec sp_addsrvrolemember N'NT Authority\System', sysadmin
> > goThen change the SQL Server account to a the local system account in
> > Enterprise manger, right click on it and select properties and then select
> > the security tab and make the modifcation here, bounce it and the repeat the
> > process to have it run under a local adminstrators account.
> >
> >
> >
> > --
> > Hilary Cotter
> > Director of Text Mining and Database Strategy
> > RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> >
> > This posting is my own and doesn't necessarily represent RelevantNoise's
> > positions, strategies or opinions.
> >
> > Looking for a SQL Server replication book?
> > http://www.nwsu.com/0974973602.html
> >
> > Looking for a FAQ on Indexing Services/SQL FTS
> > http://www.indexserverfaq.com
> >
> >
> >
> > "Jarvis Allen" <JarvisAllen@.discussions.microsoft.com> wrote in message
> > news:DA108BC7-E94F-4391-A71F-505CF6D42E0A@.microsoft.com...
> > > Recently moved database and full text catalogs to new server with SQL
> > > Server
> > > 2000 sp3a/SBS 2003 sp1
> > > I am having problems rebuilding and repopulating the fulltext catalogs
> > > restored to the new server.
> > > The message I encounter is "Error 7635: The Microsoft Search cannot be
> > > administered under the present user account".
> > >
> > > I understand from the link I have been referred to
> > > "http://support.microsoft.com/default.aspx?scid=kb;en-us;277549" states
> > > that
> > > the service logon was changed through the control panel instead of the
> > > Enterprise Manager therefore the service login for SQL Server does not
> > > have
> > > administrative priviledges over the MSSearch service.
> > > None of the service logins were changed through the control panel
> > >
> > > I have tried the workround as suggested in the link but I still get the
> > > same
> > > error message when I try to rebuild the full text catalog.
> > >
> > > Any of you MVP's with another approach or suggestions to solve this
> > > problem?
> >
> > Thank you for your reply Hilary
> The MS Search service is using the local system logon and built in admin has
> the role of sydadmin.
> I followed your instructions which was similiar to the instruction I
> followed in the link i was reffered to inmy original message.
> Unfortunately the your instructions I followed failed to cure the 7635 error
> (cannot administer MS Search service under present user account).
> Are ther any other slutions to try?
> >|||>
> "Jarvis Allen" wrote:
> I have tried suggestions by Hilary and the problem still persists.
> The MS Search is running under the local system account as it should which
> seems to be the problem.
> The problem seems to be getting the administer rights over the MS Search
> service.
> The SQL Server does start with the Domain Admin user.
> For some reason the Domain Admin user cannot administer the MS Search service
> even though I have used the suggested way to gain admin rights over the MS
> Search!
> Any other ideas from you SQL experts?
> >
> >
> > "Hilary Cotter" wrote:
> >
> > > What account is MSSearch running under? It must be running under the local
> > > system account. If it is not change it, you can change it through the
> > > services applet in Control panel - Administrative Tasks.
> > >
> > > Check that the builtin\Admins group is in the sysadmin role, and if not do
> > > the following
> > >
> > > use master
> > > go
> > > exec sp_grantlogin N'NT Authority\System'
> > > exec sp_defaultdb N'NT Authority\System', N'master'
> > > exec sp_defaultlanguage N'NT Authority\System','us_english'
> > > exec sp_addsrvrolemember N'NT Authority\System', sysadmin
> > > goThen change the SQL Server account to a the local system account in
> > > Enterprise manger, right click on it and select properties and then select
> > > the security tab and make the modifcation here, bounce it and the repeat the
> > > process to have it run under a local adminstrators account.
> > >
> > >
> > >
> > > --
> > > Hilary Cotter
> > > Director of Text Mining and Database Strategy
> > > RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> > >
> > > This posting is my own and doesn't necessarily represent RelevantNoise's
> > > positions, strategies or opinions.
> > >
> > > Looking for a SQL Server replication book?
> > > http://www.nwsu.com/0974973602.html
> > >
> > > Looking for a FAQ on Indexing Services/SQL FTS
> > > http://www.indexserverfaq.com
> > >
> > >
> > >
> > > "Jarvis Allen" <JarvisAllen@.discussions.microsoft.com> wrote in message
> > > news:DA108BC7-E94F-4391-A71F-505CF6D42E0A@.microsoft.com...
> > > > Recently moved database and full text catalogs to new server with SQL
> > > > Server
> > > > 2000 sp3a/SBS 2003 sp1
> > > > I am having problems rebuilding and repopulating the fulltext catalogs
> > > > restored to the new server.
> > > > The message I encounter is "Error 7635: The Microsoft Search cannot be
> > > > administered under the present user account".
> > > >
> > > > I understand from the link I have been referred to
> > > > "http://support.microsoft.com/default.aspx?scid=kb;en-us;277549" states
> > > > that
> > > > the service logon was changed through the control panel instead of the
> > > > Enterprise Manager therefore the service login for SQL Server does not
> > > > have
> > > > administrative priviledges over the MSSearch service.
> > > > None of the service logins were changed through the control panel
> > > >
> > > > I have tried the workround as suggested in the link but I still get the
> > > > same
> > > > error message when I try to rebuild the full text catalog.
> > > >
> > > > Any of you MVP's with another approach or suggestions to solve this
> > > > problem?
> > >
> > > Thank you for your reply Hilary
> > The MS Search service is using the local system logon and built in admin has
> > the role of sydadmin.
> > I followed your instructions which was similiar to the instruction I
> > followed in the link i was reffered to inmy original message.
> > Unfortunately the your instructions I followed failed to cure the 7635 error
> > (cannot administer MS Search service under present user account).
> > Are ther any other slutions to try?
> > >

Cannot rebuild full text catalogs

Cannot reattach DB

Hi,
One of our DB's had to be detached yesterday and moved to
another drive while some work was done on the original
drive. It was then transfered back to its original drive
and then I tried to reattach it but I came up with the
following error msg:
Server: Msg 5172, Level 16, State 15, Line 1
The header for file 'G:\Data\2002Data_Data.MDF' is not a
valid database file header. The PageAudit property is
incorrect.
I need to mention that before detaching the DB it was
marked as 'Suspect' and would not open the error message
said something like NOLOCK / lack of space but we had to
carry on and detach the DB.
I have done some research on newsgroup and some suggest
creating a blank DB, stop SQL, rename the newly created DB
MDF file with the original (suspect) DB files. How do you
do this? I have tried:
ALTER DATABASE [02Data] --> dummy DB name
MODIFY FILE
(
NAME = '02Data_data', -->logical file name
filename = [2002Data_Data.MDF] --> new file name (the one
I'm trying to overwritte)
)
All this is happening on SQL2000 no SQL 7 involved.
Also you can't modify the filename from ETS manager.
Any ideas'
Many thanks> I have done some research on newsgroup and some suggest
> creating a blank DB, stop SQL, rename the newly created DB
> MDF file with the original (suspect) DB files. How do you
> do this?
Move away the "production" mdf file to somewhere else. Create the new database, and then you
*create* it, you specify the same name as the production mdf file name. Then delete the newly
created mdf file. And then copy the prod mdf file to the plae where it should be (where the newly
created one points).
And this applies for the ldf file as well. If you don't have an ldf file (lessens the chance to
suceed even more), then delete the newly created one to see if SQL Server will create one st
startup.
I don't give you much hope on this, so be prepared to restore from latest OK backup or open a case
with MS support (who *might* be able to help you).
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"Elisabeth Smith" <lise_bisou@.hotmail.com> wrote in message
news:0db401c36706$d2bf6850$a101280a@.phx.gbl...
> Hi,
> One of our DB's had to be detached yesterday and moved to
> another drive while some work was done on the original
> drive. It was then transfered back to its original drive
> and then I tried to reattach it but I came up with the
> following error msg:
> Server: Msg 5172, Level 16, State 15, Line 1
> The header for file 'G:\Data\2002Data_Data.MDF' is not a
> valid database file header. The PageAudit property is
> incorrect.
> I need to mention that before detaching the DB it was
> marked as 'Suspect' and would not open the error message
> said something like NOLOCK / lack of space but we had to
> carry on and detach the DB.
> I have done some research on newsgroup and some suggest
> creating a blank DB, stop SQL, rename the newly created DB
> MDF file with the original (suspect) DB files. How do you
> do this? I have tried:
> ALTER DATABASE [02Data] --> dummy DB name
> MODIFY FILE
> (
> NAME = '02Data_data', -->logical file name
> filename = [2002Data_Data.MDF] --> new file name (the one
> I'm trying to overwritte)
> )
>
> All this is happening on SQL2000 no SQL 7 involved.
> Also you can't modify the filename from ETS manager.
> Any ideas'
> Many thanks
>|||You CANNOT delete the newly created mdf file because of
sharing violation! if you detach the db beforehand and
delete the file and replace it with the bad file then
you're back to square one when trying to reattach!
>--Original Message--
>> I have done some research on newsgroup and some suggest
>> creating a blank DB, stop SQL, rename the newly created
DB
>> MDF file with the original (suspect) DB files. How do
you
>> do this?
>Move away the "production" mdf file to somewhere else.
Create the new database, and then you
>*create* it, you specify the same name as the production
mdf file name. Then delete the newly
>created mdf file. And then copy the prod mdf file to the
plae where it should be (where the newly
>created one points).
>And this applies for the ldf file as well. If you don't
have an ldf file (lessens the chance to
>suceed even more), then delete the newly created one to
see if SQL Server will create one st
>startup.
>I don't give you much hope on this, so be prepared to
restore from latest OK backup or open a case
>with MS support (who *might* be able to help you).
>--
>Tibor Karaszi, SQL Server MVP
>Archive at: http://groups.google.com/groups?oi=djq&as
ugroup=microsoft.public.sqlserver
>
>"Elisabeth Smith" <lise_bisou@.hotmail.com> wrote in
message
>news:0db401c36706$d2bf6850$a101280a@.phx.gbl...
>> Hi,
>> One of our DB's had to be detached yesterday and moved
to
>> another drive while some work was done on the original
>> drive. It was then transfered back to its original drive
>> and then I tried to reattach it but I came up with the
>> following error msg:
>> Server: Msg 5172, Level 16, State 15, Line 1
>> The header for file 'G:\Data\2002Data_Data.MDF' is not a
>> valid database file header. The PageAudit property is
>> incorrect.
>> I need to mention that before detaching the DB it was
>> marked as 'Suspect' and would not open the error message
>> said something like NOLOCK / lack of space but we had to
>> carry on and detach the DB.
>> I have done some research on newsgroup and some suggest
>> creating a blank DB, stop SQL, rename the newly created
DB
>> MDF file with the original (suspect) DB files. How do
you
>> do this? I have tried:
>> ALTER DATABASE [02Data] --> dummy DB name
>> MODIFY FILE
>> (
>> NAME = '02Data_data', -->logical file name
>> filename = [2002Data_Data.MDF] --> new file name (the
one
>> I'm trying to overwritte)
>> )
>>
>> All this is happening on SQL2000 no SQL 7 involved.
>> Also you can't modify the filename from ETS manager.
>> Any ideas'
>> Many thanks
>
>.
>|||try stopping the sql service before you delete the original
--
BR,
Mark Broadbent mcdba,mcse+i
_________________________
"Elisabeth Smith" <lise_bisou@.hotmail.com> wrote in message
news:04b901c3670f$e6bc0d00$a001280a@.phx.gbl...
> You CANNOT delete the newly created mdf file because of
> sharing violation! if you detach the db beforehand and
> delete the file and replace it with the bad file then
> you're back to square one when trying to reattach!
>
> >--Original Message--
> >> I have done some research on newsgroup and some suggest
> >> creating a blank DB, stop SQL, rename the newly created
> DB
> >> MDF file with the original (suspect) DB files. How do
> you
> >> do this?
> >
> >Move away the "production" mdf file to somewhere else.
> Create the new database, and then you
> >*create* it, you specify the same name as the production
> mdf file name. Then delete the newly
> >created mdf file. And then copy the prod mdf file to the
> plae where it should be (where the newly
> >created one points).
> >And this applies for the ldf file as well. If you don't
> have an ldf file (lessens the chance to
> >suceed even more), then delete the newly created one to
> see if SQL Server will create one st
> >startup.
> >
> >I don't give you much hope on this, so be prepared to
> restore from latest OK backup or open a case
> >with MS support (who *might* be able to help you).
> >
> >--
> >Tibor Karaszi, SQL Server MVP
> >Archive at: http://groups.google.com/groups?oi=djq&as
> ugroup=microsoft.public.sqlserver
> >
> >
> >"Elisabeth Smith" <lise_bisou@.hotmail.com> wrote in
> message
> >news:0db401c36706$d2bf6850$a101280a@.phx.gbl...
> >> Hi,
> >>
> >> One of our DB's had to be detached yesterday and moved
> to
> >> another drive while some work was done on the original
> >> drive. It was then transfered back to its original drive
> >> and then I tried to reattach it but I came up with the
> >> following error msg:
> >>
> >> Server: Msg 5172, Level 16, State 15, Line 1
> >> The header for file 'G:\Data\2002Data_Data.MDF' is not a
> >> valid database file header. The PageAudit property is
> >> incorrect.
> >>
> >> I need to mention that before detaching the DB it was
> >> marked as 'Suspect' and would not open the error message
> >> said something like NOLOCK / lack of space but we had to
> >> carry on and detach the DB.
> >>
> >> I have done some research on newsgroup and some suggest
> >> creating a blank DB, stop SQL, rename the newly created
> DB
> >> MDF file with the original (suspect) DB files. How do
> you
> >> do this? I have tried:
> >>
> >> ALTER DATABASE [02Data] --> dummy DB name
> >> MODIFY FILE
> >> (
> >> NAME = '02Data_data', -->logical file name
> >> filename = [2002Data_Data.MDF] --> new file name (the
> one
> >> I'm trying to overwritte)
> >> )
> >>
> >>
> >> All this is happening on SQL2000 no SQL 7 involved.
> >>
> >> Also you can't modify the filename from ETS manager.
> >>
> >> Any ideas'
> >>
> >> Many thanks
> >>
> >
> >
> >.
> >|||Yeah I clicked eventually... Cheers mate.
>--Original Message--
>try stopping the sql service before you delete the
original
>--
>BR,
>Mark Broadbent mcdba,mcse+i
>_________________________
>"Elisabeth Smith" <lise_bisou@.hotmail.com> wrote in
message
>news:04b901c3670f$e6bc0d00$a001280a@.phx.gbl...
>> You CANNOT delete the newly created mdf file because of
>> sharing violation! if you detach the db beforehand and
>> delete the file and replace it with the bad file then
>> you're back to square one when trying to reattach!
>>
>> >--Original Message--
>> >> I have done some research on newsgroup and some
suggest
>> >> creating a blank DB, stop SQL, rename the newly
created
>> DB
>> >> MDF file with the original (suspect) DB files. How do
>> you
>> >> do this?
>> >
>> >Move away the "production" mdf file to somewhere else.
>> Create the new database, and then you
>> >*create* it, you specify the same name as the
production
>> mdf file name. Then delete the newly
>> >created mdf file. And then copy the prod mdf file to
the
>> plae where it should be (where the newly
>> >created one points).
>> >And this applies for the ldf file as well. If you don't
>> have an ldf file (lessens the chance to
>> >suceed even more), then delete the newly created one to
>> see if SQL Server will create one st
>> >startup.
>> >
>> >I don't give you much hope on this, so be prepared to
>> restore from latest OK backup or open a case
>> >with MS support (who *might* be able to help you).
>> >
>> >--
>> >Tibor Karaszi, SQL Server MVP
>> >Archive at: http://groups.google.com/groups?oi=djq&as
>> ugroup=microsoft.public.sqlserver
>> >
>> >
>> >"Elisabeth Smith" <lise_bisou@.hotmail.com> wrote in
>> message
>> >news:0db401c36706$d2bf6850$a101280a@.phx.gbl...
>> >> Hi,
>> >>
>> >> One of our DB's had to be detached yesterday and
moved
>> to
>> >> another drive while some work was done on the
original
>> >> drive. It was then transfered back to its original
drive
>> >> and then I tried to reattach it but I came up with
the
>> >> following error msg:
>> >>
>> >> Server: Msg 5172, Level 16, State 15, Line 1
>> >> The header for file 'G:\Data\2002Data_Data.MDF' is
not a
>> >> valid database file header. The PageAudit property is
>> >> incorrect.
>> >>
>> >> I need to mention that before detaching the DB it was
>> >> marked as 'Suspect' and would not open the error
message
>> >> said something like NOLOCK / lack of space but we
had to
>> >> carry on and detach the DB.
>> >>
>> >> I have done some research on newsgroup and some
suggest
>> >> creating a blank DB, stop SQL, rename the newly
created
>> DB
>> >> MDF file with the original (suspect) DB files. How do
>> you
>> >> do this? I have tried:
>> >>
>> >> ALTER DATABASE [02Data] --> dummy DB name
>> >> MODIFY FILE
>> >> (
>> >> NAME = '02Data_data', -->logical file name
>> >> filename = [2002Data_Data.MDF] --> new file name
(the
>> one
>> >> I'm trying to overwritte)
>> >> )
>> >>
>> >>
>> >> All this is happening on SQL2000 no SQL 7 involved.
>> >>
>> >> Also you can't modify the filename from ETS manager.
>> >>
>> >> Any ideas'
>> >>
>> >> Many thanks
>> >>
>> >
>> >
>> >.
>> >
>
>.
>|||"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
skrev i melding news:uI171jwZDHA.1644@.TK2MSFTNGP10.phx.gbl...
> > I have done some research on newsgroup and some suggest
> > creating a blank DB, stop SQL, rename the newly created DB
> > MDF file with the original (suspect) DB files. How do you
> > do this?
> Move away the "production" mdf file to somewhere else. Create the new
database, and then you
> *create* it, you specify the same name as the production mdf file name.
Then delete the newly
> created mdf file. And then copy the prod mdf file to the plae where it
should be (where the newly
> created one points).
> And this applies for the ldf file as well. If you don't have an ldf file
(lessens the chance to
> suceed even more), then delete the newly created one to see if SQL Server
will create one st
> startup.
> I don't give you much hope on this, so be prepared to restore from latest
OK backup or open a case
> with MS support (who *might* be able to help you).
> --
> Tibor Karaszi, SQL Server MVP
> Archive at: http://groups.google.com/groups?oi=djq&as
ugroup=microsoft.public.sqlserver
>
> "Elisabeth Smith" <lise_bisou@.hotmail.com> wrote in message
> news:0db401c36706$d2bf6850$a101280a@.phx.gbl...
> > Hi,
> >
> > One of our DB's had to be detached yesterday and moved to
> > another drive while some work was done on the original
> > drive. It was then transfered back to its original drive
> > and then I tried to reattach it but I came up with the
> > following error msg:
> >
> > Server: Msg 5172, Level 16, State 15, Line 1
> > The header for file 'G:\Data\2002Data_Data.MDF' is not a
> > valid database file header. The PageAudit property is
> > incorrect.
> >
> > I need to mention that before detaching the DB it was
> > marked as 'Suspect' and would not open the error message
> > said something like NOLOCK / lack of space but we had to
> > carry on and detach the DB.
> >
> > I have done some research on newsgroup and some suggest
> > creating a blank DB, stop SQL, rename the newly created DB
> > MDF file with the original (suspect) DB files. How do you
> > do this? I have tried:
> >
> > ALTER DATABASE [02Data] --> dummy DB name
> > MODIFY FILE
> > (
> > NAME = '02Data_data', -->logical file name
> > filename = [2002Data_Data.MDF] --> new file name (the one
> > I'm trying to overwritte)
> > )
> >
> >
> > All this is happening on SQL2000 no SQL 7 involved.
> >
> > Also you can't modify the filename from ETS manager.
> >
> > Any ideas'
> >
> > Many thanks
> >
MSSQL2000
I had the same problem on some databases there was gonedown when there was
an error on a RAID controller and disks. There was NO WAY for me to reattach
or fix the mdf file so it will work 100%. I have tried everything thats
possible. The result was that i needed to use a 3d part utility called
MSSQLRecovery version 1.5 to extract the data and manualy check all the data
and then copied the data on to the SQL server and there was/is a hell of a
jobb. I also called MS, but they coudn't do anything with the file(s). So
good luck. SQL files sucks when there is something wrong with dem. So from
now i only trust the backup made by Veritas Backup Exec on Tape.
/Per W.

Friday, February 10, 2012

Cannot find stored proc dbo.sp_MSmakeexpandproc

This question has to do with SL Server replication with CRM
I moved the CRM SQL Server mdf & ldf files from the C drive to the E drive
following the instructions in KB872585.
Everything went well except I cannot enable replication.
I performed the following steps:
Reopen Microsoft SQL Enterprise Manager; click Start, point to All Programs,
point to Microsoft SQL Server, and then click Enterprise Manager.
Expand Microsoft SQL Servers, expand SQL Server Group, expand your Microsoft
CRM SQL Server, then expand Replication Monitor, expand Publishers, and
expand your SQL Server Name where you will find the CRMMetaPub and CRMPub
publications.
Select CRMMetaPub and right-click the Snapshot in the right window pane.
Click Start Agent. (When finished the CRMMetaPub snapshot states, "A
snapshot of 79 article(s) was generated." )
Select CRMPub and right-click the Snapshot in the right window pane. Click
Start Agent.
This step fails with the error:
"Cannot find stored proc dbo.sp_MSmakeexpandproc."
When I search both drives for this file, I cannot find it.
I cannot find this error message in the knowledgebase.
Is this issue CRM specific or is it a general SQL Server replication
problem?
Can anyone tell me what is wrong? Right now our CRM is dead in the water.
Sounds like this proc is missing

I'm not sure why this is, but from time to time on this newsgroup and on one
site I have worked on the replication stored procedures go missing. The last
time this happened I think we were pretty sure that the service pack had not
been correctly applied.
Any way you can reapply the sp? Perhaps even SP4?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Dave" <dave@.nospam.ru> wrote in message
news:OsotUBNVFHA.3312@.TK2MSFTNGP09.phx.gbl...
> This question has to do with SL Server replication with CRM
> I moved the CRM SQL Server mdf & ldf files from the C drive to the E drive
> following the instructions in KB872585.
> Everything went well except I cannot enable replication.
> I performed the following steps:
> Reopen Microsoft SQL Enterprise Manager; click Start, point to All
Programs,
> point to Microsoft SQL Server, and then click Enterprise Manager.
> Expand Microsoft SQL Servers, expand SQL Server Group, expand your
Microsoft
> CRM SQL Server, then expand Replication Monitor, expand Publishers, and
> expand your SQL Server Name where you will find the CRMMetaPub and CRMPub
> publications.
> Select CRMMetaPub and right-click the Snapshot in the right window pane.
> Click Start Agent. (When finished the CRMMetaPub snapshot states, "A
> snapshot of 79 article(s) was generated." )
> Select CRMPub and right-click the Snapshot in the right window pane. Click
> Start Agent.
> This step fails with the error:
> "Cannot find stored proc dbo.sp_MSmakeexpandproc."
> When I search both drives for this file, I cannot find it.
> I cannot find this error message in the knowledgebase.
> Is this issue CRM specific or is it a general SQL Server replication
> problem?
> Can anyone tell me what is wrong? Right now our CRM is dead in the water.
>
>

Sunday, March 25, 2012

Cannot rebuild full text catalogs

Cannot rebuild full text catalogs

Cannot rebuild full text catalogs

Cannot reattach DB

Friday, February 10, 2012

Cannot find stored proc dbo.sp_MSmakeexpandproc

Cannot find mdf files

Blog Archive

About Me