Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

HELP!!!  Cannot attach content database for SharePoint Foundation 2010...

Posted on 2012-03-21
3
Medium Priority
?
1,067 Views
Last Modified: 2012-03-21
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.
0
Comment
Question by:rsnellman
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
3 Comments
 

Author Comment

by:rsnellman
ID: 37750125
OK, adding "-databaseserver SQLServer1:1433\" did not work either.
0
 

Author Comment

by:rsnellman
ID: 37750135
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.
0
 

Accepted Solution

by:
rsnellman earned 0 total points
ID: 37750271
OK, I have it figured out.  Sorry for the freaking out.

Apparently, you have to recreate the SharePoint port 80 web app before you can migrate/upgrade the WSS_Content from WSS 3.0 because it needs to be able to attach to an existing web app.  Duh.

Thanks anyways.
0

Featured Post

Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When using a search centre, I'm going to show you how to configure Sharepoint's search to only return results from the current site collection. Very useful when using Office 365 with multiple site collections.
I was prompted to write this article after the recent World-Wide Ransomware outbreak. For years now, System Administrators around the world have used the excuse of "Waiting a Bit" before applying Security Patch Updates. This type of reasoning to me …
This tutorial will give a short introduction and overview of Backup Exec 2012 and how to navigate and perform basic functions. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as conne…
This tutorial will walk an individual through setting the global and backup job media overwrite and protection periods in Backup Exec 2012. Log onto the Backup Exec Central Administration Server. Examine the services. If all or most of them are stop…

609 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question