rsnellman
asked on
HELP!!! Cannot attach content database for SharePoint Foundation 2010...
HELP!!! I cannot attach the content database for SharePoint Foundation 2010.
I am using the SharePoint 2010 Management Shell on the new server that is running Foundation.
When I type in the following command, I receive a "The server instance specified was not found. Please specify the server's address and port."
stsadm -o addcontentdb -url http://SPServer2 -clearchangelog -databasename WSS_Content -databaseserver SQLServer1\ -databaseuser domain\Administrator -databasepassword xxxxxxx -sitewarning 9000 -sitemax 15000
The SQL Server 2005 database resides on a remote SQL server (SQLServer1) while the Foundation is installed on the server (SPServer2) I am trying to attach/upgrade the content database that is being migrated from my old WSS 3.0 server.
SPServer2 = Server 2008 R2 with SharePoint Foundation 2010
SQLServer1 = Server 2008 R2 with SQL 2005 SP4 x64
I already have the Foundation Server Farm/Site settings configured. Now I am just trying to attach this content database. I was successful with a test server migration, but never ran into this issue during the testing phase.
What am I missing? Any ideas?
Thanks in advance.
I am using the SharePoint 2010 Management Shell on the new server that is running Foundation.
When I type in the following command, I receive a "The server instance specified was not found. Please specify the server's address and port."
stsadm -o addcontentdb -url http://SPServer2 -clearchangelog -databasename WSS_Content -databaseserver SQLServer1\ -databaseuser domain\Administrator -databasepassword xxxxxxx -sitewarning 9000 -sitemax 15000
The SQL Server 2005 database resides on a remote SQL server (SQLServer1) while the Foundation is installed on the server (SPServer2) I am trying to attach/upgrade the content database that is being migrated from my old WSS 3.0 server.
SPServer2 = Server 2008 R2 with SharePoint Foundation 2010
SQLServer1 = Server 2008 R2 with SQL 2005 SP4 x64
I already have the Foundation Server Farm/Site settings configured. Now I am just trying to attach this content database. I was successful with a test server migration, but never ran into this issue during the testing phase.
What am I missing? Any ideas?
Thanks in advance.
ASKER
I know it the firewall is not blocking it because I had a default content database that up until a few moments ago resided on the SQLServer1 system.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER