Tuesday, July 31, 2012 12:33 PM
I have SharePoint 2007 installed on Windows Server 2003 and Clustered SQL Server 2008 installed on Windows Server 2008.
I have an SQL content database that I need to add it to add it to the SharePoint using addcontentdb STSADM command.
When I execute the STSADM command to add the database, below error are returned:A network-related or instance-specific error occurred while establishing a conne
ction to SQL Server. The server was not found or was not accessible. Verify that
the instance name is correct and that SQL Server is configured to allow remote
connections. (provider: Named Pipes Provider, error: 40 - Could not open a conne
ction to SQL Server)
1- I checked the protocols settings for SQL: Shared Memory, TCP/IP, and Named Pipes. And all of them are enabled.
2- I checked that the Remote Connection on SQL Server are Enabled.
3- I checked for the port 1433 if it is open or no, and it is open and no problem with it.
4- The same error appear when I add content database from central admin >> Application Management >> Manage Content Database.
5- When I create new web application with new Site Collection from Central Admin no thing happen and every thing working fine.
6- The user that I used to execute the command, working on Central Admin, and the owner of the content database are same.
So please advice me about this issue.
Tuesday, July 31, 2012 2:30 PM
Is the database you are trying to add located in the same SQL Server instance that the farm uses?
Will you provide us with the server names in your farm and the stsadm command you are using?
Can you verify the connection to SQL Server from the SharePoint server using a UDL file?
Wednesday, August 01, 2012 7:33 AM
Thanks for your reply.
Yes, the database in the same SQL Server instance that the farm use.
and for the Command that I used, is below:
stsadm -o addcontentdb -url http://portal:88 -databasename Intra_Site_Cont -databaseserver SQLVirtual
the servers name are:
SharePoint Server: portal
Node1 & Node2.
Finally, I verified the the connection using UDL file and it connected without problems using server name and its IP address.
Thanks for you again.
Wednesday, August 01, 2012 2:09 PM
Do you receive the same error if you try the addcontentdb operation but without the -databaseserver parameter? For example:
stsadm -o addcontentdb -url http://portal:88 -databasename Intra_Site_Cont
- Edited by Jason WarrenMicrosoft Community Contributor Wednesday, August 01, 2012 2:09 PM
Thursday, August 02, 2012 5:21 AM
How big is the content DB? and how much space is left for the Data and log files drives.
Thursday, August 02, 2012 9:04 AMYes I tried this command, but return the same error.
Thursday, August 02, 2012 9:06 AMDatabase size is about 7.5 GB and there are about 30 GB free space, I think it is enough...
Thursday, August 02, 2012 11:59 PM
is database is located in separate server or the same SharePoint installed server?
are you using the same account that you have use to create a web application through central admin.
Can you pls also let us know what sort of right and roles you have on the sql server side with the account you are trying to run stsadm.
dont copy and paste the cmd and use the parameter as url and dbname only.
can you try to add the content DB by using CA going through "Manage content DB" option under Application Management.
Also follow this article
Tuesday, August 07, 2012 7:31 AM
Try adding the instance name to the --databaseserver parameter. e.g. MYSQL\MSSQLSERVER.
That has helped us in some cases.