Advertisement

01.09.2008 at 08:29AM PST, ID: 23069890
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!
9.6

Moving configuration database for WSS V3

Asked by need-wss-help in MOSS-Sharepoint

Tags:

We moved our WSS V3 databases from Server A to Server B, and then stopped SQL Server on Server A. Everything seems to be running fine, but on the Web Front End Server, event logs are being generated every couple of minutes where it is trying to connect the Server A.

When we moved the databases, this is the process we used:
- Detached content database from SharePoint
- Detached SharePoint database from SQL Server on Server A
- Move data & log files from Server A to Server B
- Attached SharePoint database to SQL Server on Server B
- Disconnected Web Front End Server from SharePoint Farm with Server A thru SharePoint Products and Technologies Configuration Wizard
- Connected Web Front End Server to SharePoint Farm with Server B thru SharePoint Products and Technologies Configuration Wizard
- Set configuration database to reference Server B using stsadm o setconfigdb
- Added Central Administration content db using stsadm o addcontentdb
- Attached the content database to SharePoint thru Central Administration

When I look at the Servers in Farm page in Central Administration, it still shows the configuration database as being Server A. How can I get SharePoint to fully recognize that the configuration database is on Server B? I would like to get rid of all references to Server A and completely remove it from the farm.

Please let me know if you need more details.
Start Free Trial
[+][-]01.09.2008 at 01:17PM PST, ID: 20622518

View this solution now by starting your 7-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zone: MOSS-Sharepoint
Tags: Microsoft, Windows Sharepoint Services, 3.0, SQL backend
Sign Up Now!
Solution Provided By: Robbie_Leggett
Participating Experts: 1
Solution Grade: A
 
 
[+][-]09.04.2008 at 02:41PM PDT, ID: 22393012

Experts Exchange has a courteous staff of administrators who help members get the most out of the website by means of administrative comments like this one.

Start your 7-day free trial to view this Administrative Comment or ask the Experts your question.

 
[+][-]09.09.2008 at 08:14PM PDT, ID: 22434615

Experts Exchange has a courteous staff of administrators who help members get the most out of the website by means of administrative comments like this one.

Start your 7-day free trial to view this Administrative Comment or ask the Experts your question.

 
 
Loading Advertisement...
20080716-EE-VQP-32 / EE_QW_2_20070628