Blog posts - recent

Blog posts > SharePoint 2007 > , , , , ,

Installing MOSS 2007 on Windows Server 2008 and SQL Server 2008 - Part 6: Installing MOSS 2007

14. August 2008
| by Andreas
| 13 Comments |

This article is a part of a series describing the installation of Microsoft Office SharePoint Server 2007 (MOSS) on a Windows Server 2008 with the newly released SQL Server 2008. Please have a look at "Installing MOSS 2007 on Windows Server 2008 and SQL Server 2008 - Part 1: Overview".

  • Select Advanced installation mode.
  • Select "Complete - Install all components. Can add servers to form a SharePoint farm."

Chose advanced installation mode. Select complete install.

  • Wait until the installation process finishes.
  • Note that you can download a MOSS 2007 installation DVD including SP1 from Microsoft. You need an installation source including SP1 in order to install MOSS 2007 on a Windows Server 2008.

Wait until setup has finished. You need SP1 for MOSS 2007 in order to work with Windows Server 2008.

  • Click Yes and proceed to the next screen.
  • Select "No, I want to create a new server farm".

Click yes to proceed. Create a new server farm.

  • Now you have to enter the name of your SQL Server (This is usually your system NAME or ip address or Default Database Server Name [thx to Veer]) and the MOSS farm account credentials (In my case aglaser\MOSSfarm).
  • If you are getting the error

    "Failed to connect to the database server or the database name does not exist.  Ensure the database server exists, is a Sql server, and that you have the appropriate permissions to access the database server.  To diagnose the problem, review the extended error information located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\PSCDiagnostics_8_13_2008_11_19_34_359_1143906485.log.  Please consult the SharePoint Products and Technologies Configuration Wizard help for additional information regarding database server security configuration and network access." or

    "An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)"

    you have to make sure you

    -have deactivated your firewall or opened the ports needed and
    -that you have a working network connection to your Active Directory server. Try to ping your AD server.

Enter your SQL Server name and your farm account credentials. If you get an error check firewall and network settings.

  • Specify the port number for Central Administration and the authentication provider.
  • Wait until the configuration wizard has finished.

Specify port number for central administration and select authentication provider. Wait until the configuration wizard has finished.

Please take a look at Part 7: Configuring MOSS 2007.

Comments

12/4/2008 4:56:48 PM #

Trackback from Office et SharePoint pour et par les administrateurs

Installation MOSS 2007 sur Windows 2008 et SQL Server 2008...

Office et SharePoint pour et par les administrateurs

2/10/2009 5:12:58 PM #

I am getting Event 6141 – Site couldn't be created – Exception 0x81070209, followed by event 104 – Failed to create Configuration database

All accounts seem to be in order, active directory is working OK. this is a dev system that is only a few days old so its pretty healthy and patched up to a decent level.

I am not sure what troubleshooting steps to do next, I have read through many forums but there doesn't seem to be many answers out there in this topic.

Any suggestions would be much appreciated.

Peter Bright United Kingdom

2/12/2009 8:30:22 AM #

Just to understand the whole thing:

-You have a dev system and wanted to install and configurate SharePoint...
-Install worked...
-Configuration did not work, right?

Can you please give me additional information?

-> What setup do you have? Did you install the SQL Server on the same maschine as the SharePoint Server?
-> Where is the AD located?

My trouble shooting steps would be:

-Checking log files for detailed messages:
SQL Server -> msdn.microsoft.com/en-us/library/ms143702.aspx
SharePoint -> I don't know if this is the 12 hive when you install and configurate

-Checking Event Viewer for additional information
-Pinging all servers
-Checking SQL Server services if they are running
-Checking SQL Server configuration (named pipes enabled)
-Checking setup account permission

-Do you use virtualization? Maybe the environment configuration isn't working...


I don't know what you already did but I hope it helps you...

Andreas

Andreas Switzerland

8/22/2009 9:48:16 PM #

Andreas,

Shouldn't you be using the setupAdmin account when creating the new server farm and NOT the MOSSfarm account? You give the setupAdmin account permissions to be a dbcreator and securityadmin within SQL, but I don't see the step where you give the MOSSfarm account any permissions.

Thanks in advance!!

--
Joe

Joe United States

8/22/2009 10:40:44 PM #

Hi Joe,

MOSS 2007 installation needs only 1 account you have to give permission by yourself: the setupAdmin.

The setupAdmin gives permission to the MOSSFarm account because the setupAdmin
-has dbcreator + securityadmin rights in SQL Server and
-is on every SharePoint server in the local administrators group.

So if you run the SharePoint Products and Technologies Configuration Wizard using the setupAdmin the MOSSFarm automatically gets all permissions.

Regards,
Andreas

Andreas Switzerland

8/29/2009 6:37:20 PM #

After disable firewall and use Account setupAdmin, I still got error, the exception through due to existing config mdf file can not be overwrite. After delete existing, process gone as normal. Thanks

Hoang Thanh Dong Vietnam

9/4/2009 11:46:19 AM #

Error with Windows Server 2008 R2 (Blocked application)
If you are running Microsoft Server 2008 R2 you get an errormessage telling you that the application is blocked if you try to install SharepointServer(officeserver.exe) or Sharepointserver with SP1 (OfficeServerWithSP1.exe).  The solution to this problem is to make your own Sharepointserver installation with SP2 included in the installation files.  Here is a walkthrough guide to how you do it: blogs.technet.com/.../...arepoint-server-2007.aspx
Follow this guide, and the error message is gone Smile

Audun Norway

9/13/2009 6:57:57 PM #

Hi Audun,

thanks for the info and for the guide creating slipstreams Smile

Andreas

Andreas Switzerland

9/23/2009 5:44:02 PM #

I had some trouble with the connection error.  For me the solution was to start the SQl browser service, and set it to auto...  I also had to put the instance name and server name "SQL_server\SQL_Instance"

Zack Paradise United States

11/4/2009 4:58:57 AM #

When I attempted to proceed past the database settings window, I was told that IIS wasn't running. I followed the directions in the previous step, but uninstalled the app server and IIS roles just in case.  No dice.  Then I found this:

www.moggoly.me.uk/blog/post/IIS-not-installed.aspx

I enabled the IIS 6 compatibility as the page describes and was able to continue the install.

Thanks for the great how-to!

jason z United States

12/20/2009 10:43:29 PM #

Hi Andreas,

Thanks for the Excellent tutorial/how-to. This was very helpful especially for newb like me, but I am stuck at the above mentioned exception during the sharepoint configuration wizard. My setup is a dev env, so SQL server 2008 is also on the same machine as sharepoint. I have tried the following to eliminate the cause for this exception.

1.Ensured that IIS7(Application Server, WebServer, DNS server are all in running state). Pinged Domain name with 100% reply back with ip address.
2. Ensured that SQLserver, Sqlbrowser, SQLWriter is in running state with TCP/IP & Nested pipes enabled. Made all the three services as Automatic with system startup
3. Ensured that firewall has port forward exception to 1433 & SQLServer allows remote connections.(I also tried the wizard with firewall off, but still got the same exception).
4. I have installed the sharepoint as Administrator & am running the wizard as Administrator. So I have also tried giving Administrator as 'dbcreator' & 'securityAdmin' before running the wizard.
5. Ensured that 'setupAdmin' account has dbcreator, public & securityAdmin role mappings in SQL. Ensure that 'setupAdmin' is a part of Administrators group under Active DNS settings. Login into the OS(win 2008 r2 X86) as setupAdmin & ran the sharepoint wizard.
6. I have also rebooted the OS several times to release & refresh settings & tried the wizard. Same Exception.

Could you shed some light on any other possible conditions to fix this issue.

Thanks again,
Veer

Veer United States

12/20/2009 11:48:59 PM #

Hi Andreas,

Thanks for the excellent tutorial. It really helpful.
I would like to point a very small text addition to the above Part6: Install Moss2007 page.

"Now you have to enter the name of your SQL Server (This is usually your system NAME or ip address or Default Database Server Name)".
I overlooked it & has given 'SQLServer2008' as the server name in my installation & this took me an hour more to figure out what went wrong. Even though this is a simple thing to realize, I just thought it would help people like me.

On the other hand, this issue also made me learn all the other required things like remote connections, Firewall port forwards & Nested Pipelines.

Thanks again,
Veer

Veer United States

12/23/2009 11:33:12 AM #

Hi Veer,

thank you for your additions Smile they are very appreciated!

I'm really sorry for the late reply... I'm on vacation and didn't had time to check my mails.

Andreas

Andreas Switzerland

Add comment




  Country flag

biuquote
Loading