My server is down, reinstalled Win2003 & WSS. However, I can only restore
STS_* MSDE databases, restored successfully but accessing the sharepoint
site prompts "The Web site that is referenced here is not in the
configuration database." Please help me how can I re-link the content
database and the sharepoint site. Thanks


Ian

Re: Restoring MSDE database by Need

Need
Wed Aug 16 02:06:57 CDT 2006

According to WSS FAQ, it states that STS_config needs not restore, I try it
but I still fails to add content database in Central Admin page. Is that
MSDE limitation?



Re: Restoring MSDE database by Need

Need
Wed Aug 16 02:41:28 CDT 2006

After numerous backup and restore trial and error, I found that since my new
WSS site content database is as the same as the old one.


What I must do that requires minor extra steps are:
http://wss.collutions.com/Lists/FAQ/DispForm.aspx?ID=460

Before step 5, I must make sure my new WSS site content database name cause
no conflict with old content database




"Need Help" <DONTSPAM@DONTSPAM.com> ¼¶¼g©ó¶l¥ó·s»D:uMpjMKQwGHA.1956@TK2MSFTNGP02.phx.gbl...
According to WSS FAQ, it states that STS_config needs not restore, I try it
but I still fails to add content database in Central Admin page. Is that
MSDE limitation?



Re: Restoring MSDE database by Engelbert

Engelbert
Wed Aug 16 03:33:19 CDT 2006

Thanks for this addition.

Do you mean that you needed to make sure that the new content database name
was *the same* as the old one ?

If not, can you please spell out what this

"Before step 5, I must make sure my new WSS site content database name cause
no conflict with old content database"

exactly means ?

Engelbert

"Need Help" <DONTSPAM@DONTSPAM.com> wrote in message
news:%23JalddQwGHA.3364@TK2MSFTNGP02.phx.gbl...
> After numerous backup and restore trial and error, I found that since my
> new WSS site content database is as the same as the old one.
>
>
> What I must do that requires minor extra steps are:
> http://wss.collutions.com/Lists/FAQ/DispForm.aspx?ID=460
>
> Before step 5, I must make sure my new WSS site content database name
> cause no conflict with old content database
>
>
>
>
> "Need Help" <DONTSPAM@DONTSPAM.com>
> ¼¶¼g©ó¶l¥ó·s»D:uMpjMKQwGHA.1956@TK2MSFTNGP02.phx.gbl...
> According to WSS FAQ, it states that STS_config needs not restore, I try
> it
> but I still fails to add content database in Central Admin page. Is that
> MSDE limitation?
>



Re: Restoring MSDE database by Need

Need
Wed Aug 16 22:53:24 CDT 2006

New sharepoint site content database name MUST not be the same as the
original content database name. Overwriting the content database with the
backup will crash the sharepoint site. However, it simply solve the problem
just remove the new content database and recreate one, it will generate a
new one with different name. Then restoring the old content database from
backup and adding this content database to the virtual server completes the
recovery.




"Engelbert" <Engelbert@discussions.nospam.com> ¼¶¼g©ó¶l¥ó·s»D:umrw56QwGHA.4140@TK2MSFTNGP03.phx.gbl...
Thanks for this addition.

Do you mean that you needed to make sure that the new content database name
was *the same* as the old one ?

If not, can you please spell out what this

"Before step 5, I must make sure my new WSS site content database name cause
no conflict with old content database"

exactly means ?

Engelbert

"Need Help" <DONTSPAM@DONTSPAM.com> wrote in message
news:%23JalddQwGHA.3364@TK2MSFTNGP02.phx.gbl...
> After numerous backup and restore trial and error, I found that since my
> new WSS site content database is as the same as the old one.
>
>
> What I must do that requires minor extra steps are:
> http://wss.collutions.com/Lists/FAQ/DispForm.aspx?ID=460
>
> Before step 5, I must make sure my new WSS site content database name
> cause no conflict with old content database
>
>
>
>
> "Need Help" <DONTSPAM@DONTSPAM.com> ¼¶¼g©ó¶l¥ó·s»D:uMpjMKQwGHA.1956@TK2MSFTNGP02.phx.gbl...
> According to WSS FAQ, it states that STS_config needs not restore, I try
> it
> but I still fails to add content database in Central Admin page. Is that
> MSDE limitation?
>


Re: Restoring MSDE database by Engelbert

Engelbert
Wed Aug 16 23:15:10 CDT 2006

OK. Thanks a lot.

This is still confusing for me

"just remove the new content database and recreate one, it will generate a
new one with different name. "

Can you go into details.?

So far we have

- make a copy of your old content database

-------------

- install WSS (which creates a content database and a config database)

- remove the content database (how?)

- recreate one (how?) - will generate a new one with a new name

Note: what is the difference between this one and the one you had when you
newly installed WSS ? They are both empty content databases so why do you
need these 2 steps ?

- restore the old content database from backup
- add the (new) content database to the virtual server

Engelbert

"Need Help" <DONTSPAM@DONTSPAM.com> wrote in message
news:eXflqCbwGHA.1304@TK2MSFTNGP06.phx.gbl...
> New sharepoint site content database name MUST not be the same as the
> original content database name. Overwriting the content database with the
> backup will crash the sharepoint site. However, it simply solve the
> problem just remove the new content database and recreate one, it will
> generate a new one with different name. Then restoring the old content
> database from backup and adding this content database to the virtual
> server completes the recovery.
>
>
>
>
> "Engelbert" <Engelbert@discussions.nospam.com>
> ¼¶¼g©ó¶l¥ó·s»D:umrw56QwGHA.4140@TK2MSFTNGP03.phx.gbl...
> Thanks for this addition.
>
> Do you mean that you needed to make sure that the new content database
> name
> was *the same* as the old one ?
>
> If not, can you please spell out what this
>
> "Before step 5, I must make sure my new WSS site content database name
> cause
> no conflict with old content database"
>
> exactly means ?
>
> Engelbert
>
> "Need Help" <DONTSPAM@DONTSPAM.com> wrote in message
> news:%23JalddQwGHA.3364@TK2MSFTNGP02.phx.gbl...
>> After numerous backup and restore trial and error, I found that since my
>> new WSS site content database is as the same as the old one.
>>
>>
>> What I must do that requires minor extra steps are:
>> http://wss.collutions.com/Lists/FAQ/DispForm.aspx?ID=460
>>
>> Before step 5, I must make sure my new WSS site content database name
>> cause no conflict with old content database
>>
>>
>>
>>
>> "Need Help" <DONTSPAM@DONTSPAM.com>
>> ¼¶¼g©ó¶l¥ó·s»D:uMpjMKQwGHA.1956@TK2MSFTNGP02.phx.gbl...
>> According to WSS FAQ, it states that STS_config needs not restore, I try
>> it
>> but I still fails to add content database in Central Admin page. Is that
>> MSDE limitation?
>>
>