Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

New front end server

  Asked By: Haresh    Date: Jan 18    Category: Sharepoint    Views: 3173

We are in the process of moving all Sharepoint web front end to a new server
2008 x64 windows (“ does anyone have a procedure to use for such an activity
that will not lose current workflows in progress we have appx 250 sites and
bamboo solutions installed on the current front end web server.

Share: 

 

10 Answers Found

 
Answer #1    Answered By: Manohar Kothare     Answered On: Jan 18

Am I missing something here? Web front  Ends pull their information from the
configuration database when they are added to the farm. All you need to do is
install the new server, add it to the farm and to whatever load balancing
mechanism you are using. Be sure to install any SSL certificates that you might
need and update any additional host headers that might exist in IIS.

Your sites and workflows  are all contained in the content databases for the web
applications, which reside on your SQL server  and won't be affected by moving
your front end  to a new server.

 
Answer #2    Answered By: Terri Wolfe     Answered On: Jan 18

I think that's just it, there Is no load balancing just a replacement of the
front end  server

 
Answer #3    Answered By: Andre Mason     Answered On: Jan 18

Everything I was reading though said to backup and restore to a new database-
which I did and now my workflows  are a mess (to be polite) as a matter of fact
they do not execute at all and the ones in process  are all error-ing out.

 
Answer #4    Answered By: Esteban Frank     Answered On: Jan 18

If all you were doing was replacing the Front End server  you shouldn’t have
had to anything to your databases. Were you replacing SQL? In your original post
you merely stated you wanted to put in a new Web Front End. To do this, all you
need to do is install the new system, install the SharePoint bits so they are at
the same service pack level as your existing farm, and then run the
configuration wizard to add the new server to the farm.

Do you have an application server or are you actually running all SharePoint
functions on a single server?

 
Answer #5    Answered By: Jabari Burks     Answered On: Jan 18

I did try that. Updated the original front  end with sp2, ran the config and it
started throwing exception errors, back end  SQL database throws exceptions when
trying to update

Now database throws incorrect schema error

This is just an app server  front end with SQL on another box. I seemed to have
fubar'ed the entire site now

 
Answer #6    Answered By: Heena Desai     Answered On: Jan 18

An "app server front  end"? That sounds suspiciously like everything
(except the database) is running on that one box. Needless to say, that's a
bit more involved than swapping out a WFE server.

 
Answer #7    Answered By: Manuel Crawford     Answered On: Jan 18

I am between a rock and a hard place - my only solution seem to be to
dismount the current  SP databases from SQL and restore from a full farm
backup done previous to this nightmare. Coule either of you proved some
guidance - the backup was taken prior to Service Pack 2 being installed. I
have both a sharepoint  backup and a SQL DB backup.

 
Answer #8    Answered By: Indraneel Haldar     Answered On: Jan 18

App server  - just sharepoint front  end nothing else. Databases server is
still showing version 12.0.0.4518 all both other frone end  server ( I was
able to bring the old one back online) are at version 12.0.0.6412 Database
fails with the following fron the log:
Configuration of SP products and technologies failed....config must be
performed.
Operation is not valid due to the current  state of the object (with no clue
as to which object)

Is it necessary of even advisable to have the database server listed in the
central admin- ops Servers in farm? This site has the database server as the
doc conversion launcher service, load balancer, office search server and
windows sharepoint  services database.

 
Answer #9    Answered By: Brittni Harding     Answered On: Jan 18

Have you opened a support call with Microsoft? They might be able to help you
fairly quickly.

It will probably take another set of eyes on the servers.

 
Answer #10    Answered By: Aayush Koli     Answered On: Jan 18

We might be able to give random spot advice, but it's no
substitute for being there when you have a situation like this.

On the other hand, if you want to hire a consultant and give them remote
access, there are several of us here who would be able to assist in a more
meaningful way.

To answer your question, yes, the database server  should be listed in
Ops->Servers in farm. It is, after all, a rather important part of the
installation. As for the other services that are installed on the DB
server, I wouldn't recommend it. I'm wondering why you have a load balancer
running if you aren't actually doing any load balancing.

If you need to get the thing up and running, you might try creating a new
application and loading the content database to it; other than that.

 
Didn't find what you were looking for? Find more on New front end server Or get search suggestion and latest updates.




Tagged: