|
Home > Archive > Microsoft Content Management Server > October 2004 > CMS Database Restore
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
CMS Database Restore
|
|
|
| Stefan:
Our production database is over 3 gig and unless we create several small
SDO's, which we don't have time to do, we can't use export/import.
So I explored a different way which worked in developement but doesn't work
on our staging environment.
Here is what I did..
I restored my development CMS database from a SQLServer CMS backup using
SQLServer Enterprise manager. All is well. Since the production database is
on a differnet domain, initally, when I launch Site Manager it fails due to
authentication issues. This is expected.
So I created a new Domain Admin account on the Domain controller and then I
added this new account to SQLServer. I made this user a System Admin.
Next I launched the DCA tool and added this new user to the CMS Database. I
was then able to launch Site Manager on my develolpment server.
But when I used this same approach on our staging environment, I got this
error.
Administrator error during the DCA add.
Failed to create initital Content Management Server administrator.
Extended error: [What='Cannot open database requested in login CMS. Login
fails. Cannot open database requested in login CMS. Login fails
[lcid=1024][sourcefile="][sourcefileline=-1][DebugInfo="][RecommendedAction='The
ODBC data source may be incorrectly configured, the database may noit be
running or there may be incorrect data in the database.
Can you advise?
Thanks
Tom
| |
| Angus Logan [MVP] 2004-10-19, 8:47 pm |
| Hi Tom,
Sounds like the account dosen't have permissions to the SQL db.
Can you go through and drop the SQL Login, SQL DB User and then re-create
them and run the DCA again?
Also are you using Trusted authentication or SQL when you select the DB from
the DCA?
Regards
--
________________________________________
Angus Logan (MCAD/MCDBA/MCP/MVP for MCMS)
Product Specialist
Microsoft Application Solutions
Data#3 Limited
E angus_logan@data3.com.au
BLOG www.anguslogan.com
________________________________________
"Tom" <Tom@discussions.microsoft.com> wrote in message
news:45879B9B-C63B-45EE-9695-0A04CB72BDD1@microsoft.com...
> Stefan:
>
> Our production database is over 3 gig and unless we create several small
> SDO's, which we don't have time to do, we can't use export/import.
>
> So I explored a different way which worked in developement but doesn't
> work
> on our staging environment.
>
> Here is what I did..
>
> I restored my development CMS database from a SQLServer CMS backup using
> SQLServer Enterprise manager. All is well. Since the production database
> is
> on a differnet domain, initally, when I launch Site Manager it fails due
> to
> authentication issues. This is expected.
>
> So I created a new Domain Admin account on the Domain controller and then
> I
> added this new account to SQLServer. I made this user a System Admin.
>
> Next I launched the DCA tool and added this new user to the CMS Database.
> I
> was then able to launch Site Manager on my develolpment server.
>
> But when I used this same approach on our staging environment, I got this
> error.
>
> Administrator error during the DCA add.
> Failed to create initital Content Management Server administrator.
> Extended error: [What='Cannot open database requested in login CMS.
> Login
> fails. Cannot open database requested in login CMS. Login fails
> [lcid=1024][sourcefile="][sourcefileline=-1][DebugInfo="][RecommendedAction='The
> ODBC data source may be incorrectly configured, the database may noit be
> running or there may be incorrect data in the database.
>
> Can you advise?
>
> Thanks
>
> Tom
>
| |
| Mei Ying [MVP] 2004-10-19, 8:47 pm |
| Hi
You don't need to give SA permissions to the account.
If you are using trusted authentication, the MCMS System
account needs to have at least db_reader, db_writer,
db_ddladmin and CMSSystem (if its available for selection)
rights.
For SQL authentication, assign the SQL account db_owner
and CMSSystem rights.
And the account used to run the DCA (that should be your
account) needs db_owner access to the database too. This
can be removed once the DCA has been ran successfully and
if you do not foresee running the DCA again.
Angus is right, one hiccup to take note of when backing up
and restoring databases is that SQL logins may need to be
re-linked after being restored. Check out the
sp_change_users_login stored procedure. This article (and
the links within it) also serves as an excellent guide on
how to move SQL databases from one server to another:
http://support.microsoft.com/default.aspx?kbid=314546
HTH
Mei Ying
---
Blog: http://meiyinglim.blogspot.com
Contact: meiyinglim@hotmail.com
---
>-----Original Message-----
>Hi Tom,
>
>Sounds like the account dosen't have permissions to the
SQL db.
>
>Can you go through and drop the SQL Login, SQL DB User
and then re-create
>them and run the DCA again?
>
>Also are you using Trusted authentication or SQL when you
select the DB from
>the DCA?
>
>Regards
>--
> ________________________________________
>
>Angus Logan (MCAD/MCDBA/MCP/MVP for MCMS)
>Product Specialist
>Microsoft Application Solutions
>Data#3 Limited
>E angus_logan@data3.com.au
>BLOG www.anguslogan.com
> ________________________________________
>"Tom" <Tom@discussions.microsoft.com> wrote in message
>news:45879B9B-C63B-45EE-9695-0A04CB72BDD1@microsoft.com...
create several small[vbcol=seagreen]
export/import.[vbcol=seagreen]
developement but doesn't[vbcol=seagreen]
CMS backup using[vbcol=seagreen]
production database[vbcol=seagreen]
Manager it fails due[vbcol=seagreen]
controller and then[vbcol=seagreen]
System Admin.[vbcol=seagreen]
the CMS Database.[vbcol=seagreen]
server.[vbcol=seagreen]
environment, I got this[vbcol=seagreen]
administrator.[vbcol=seagreen]
in login CMS.[vbcol=seagreen]
Login fails[vbcol=seagreen]
[DebugInfo="]& #91;RecommendedAction='The[vbcol=seagree
n]
database may noit be[vbcol=seagreen]
>
>
>.
>
| |
|
| Angus:
A few more questions.
1. I tried what you had suggested. If I drop my SQL Login from SQLServer,
recreate it and then use the DCA to readd the same user, CMS says the user
has already been added to the database! Its as if CMS is holding on to this
account somewhere. So I tried creating a second domain account, then added
him to SQLServer with access to the CMS database and then ran the DCA tool.
This failed too. So my question is does CMS hold on to the account somewhere
other than SQLServer? Is their any additional clean up I can do?
2. When I create my domain account, what rights does he need. Should he be
a doamin user or does he need to be a memebr of Domain Admin?
3. Should I add my domain user to the box where CMS is installed as a local
Administrator?
Thanks
"Angus Logan [MVP]" wrote:
> Hi Tom,
>
> Sounds like the account dosen't have permissions to the SQL db.
>
> Can you go through and drop the SQL Login, SQL DB User and then re-create
> them and run the DCA again?
>
> Also are you using Trusted authentication or SQL when you select the DB from
> the DCA?
>
> Regards
> --
> ________________________________________
>
> Angus Logan (MCAD/MCDBA/MCP/MVP for MCMS)
> Product Specialist
> Microsoft Application Solutions
> Data#3 Limited
> E angus_logan@data3.com.au
> BLOG www.anguslogan.com
> ________________________________________
> "Tom" <Tom@discussions.microsoft.com> wrote in message
> news:45879B9B-C63B-45EE-9695-0A04CB72BDD1@microsoft.com...
>
>
>
| |
| Stefan [MSFT] 2004-10-20, 7:47 am |
| Hi Tom,
the user you are talking about is the initial administrator and not the MCMS
system account.
Don't mix these two accounts!
The MCMS administrator is stored in the MCMS database and does not need any
rights on the SQL server machine or on the database.
Cheers,
Stefan.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
MCMS FAQ:
http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm
MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
MCMS Sample Code:
http://www.gotdotnet.com/community/...t+S
erver
MCMS Whitepapers and other docs:
http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
--------------------------------
"Tom" <Tom@discussions.microsoft.com> wrote in message
news:8D3711C6-5D57-43A1-B07C-AB4C0396281F@microsoft.com...
> Angus:
>
> A few more questions.
>
> 1. I tried what you had suggested. If I drop my SQL Login from SQLServer,
> recreate it and then use the DCA to readd the same user, CMS says the user
> has already been added to the database! Its as if CMS is holding on to
this
> account somewhere. So I tried creating a second domain account, then
added
> him to SQLServer with access to the CMS database and then ran the DCA
tool.
> This failed too. So my question is does CMS hold on to the account
somewhere
> other than SQLServer? Is their any additional clean up I can do?
>
> 2. When I create my domain account, what rights does he need. Should he
be
> a doamin user or does he need to be a memebr of Domain Admin?
>
> 3. Should I add my domain user to the box where CMS is installed as a
local[vbcol=seagreen]
> Administrator?
>
>
>
> Thanks
>
>
>
> "Angus Logan [MVP]" wrote:
>
re-create[vbcol=seagreen]
from[vbcol=seagreen]
small[vbcol=seagreen]
using[vbcol=seagreen]
database[vbcol=seagreen]
due[vbcol=seagreen]
then[vbcol=seagreen]
Database.[vbcol=seagreen]
this[vbcol=seagreen]
[lcid=1024][sourcefile="][sourcefileline=-1][DebugInfo="][RecommendedAction=
'The[vbcol=seagreen]
be[vbcol=seagreen]
|
|
|
|
|