SharePoint 2010 - From The Field

11/2/2009

Does this SQL Server Host a SharePoint Farm ?

I recently responded to a thread on Twitter (http://www.twitter.com) offering to describe a method of detecting whether a SQL server hosts a SharePoint farm. Several folks followed up asking for a blog on how to do this so here goes. Note: This is the same for 2007 and for 2010

Consider the way PSConfig identifies a Configuration Database when you try to join a server to an existing farm.

Once you choose to join an existing farm, you will then be asked to specify a database server. At that point you have the option of retrieving the database names of every configuration database on that server so that you can choose the farm you would like to join.

The database name field is populated by issuing the following SQL command from the WFE to the SQL Server:

SELECT name FROM sysdatabases WHERE has_dbaccess (name) = 1

The server responds with a list of all databases to which the logged in user has access.

In order to determine which databases are configuration databases, the following SQL query is used:

SELECT @Version=Version FROM [dbo].[Versions] WHERE VersionId=@VersionId

In this case the VersionId that SharePoint is trying to match is:

60B1F2BE-5130-45AB-AF1D-EDD34E626B5D

Only a configuration database will have a row that matches this GUID although you will find a Versions table in all SharePoint databases.
Once the information requested is provided, clicking Next will perform the following actions.
The database id is determined using the friendly name for the database.

SELECT @dbid = db_id(@databaseName)

Next, SharePoint will read in the application settings that are related to the farm to be connected to. Once that is complete, the configuration wizard will display a final confirmation before performing the configuration.

Posted at 4:06 PM by Neil 'The Doc' Hodgkinson | Category: Administration; SharePoint 2010; Troubleshooting | Permalink | Email this Post | Comments (3)

10/19/2009

Single Server Complete Install of SharePoint 2010 using local accounts

UPDATED 19 Nov 2009 - It is suggested the reader refer to MSDN article -

Setting Up the Development Environment for SharePoint Server

- http://msdn.microsoft.com/en-us/library/ee554869(office.14).aspx

Before commencing with implementing this approach to a single server installation.

Something that was possible in SharePoint Server 2007 has become tricky in SharePoint Server 2010. The complete installation on a single server using non-domain accounts. Something most developers, demonstrators and testers do a lot of suddenly requires the use of domain accounts instead of local machine accounts. Or does it....

The recommendation for a single server build of SharePoint 2010 is to use the Stand Alone installation giving you SQL express and a default configuration. But what if you want to use SQL Server 2008 and to have more control over the build, and to use local service accounts. In this case you need to use complete install and either PowerShell alone or a combination of Windows PowerShell and PSCONFIG(UI).EXE

To begin with carry out your SharePoint 2010 installation using the advanced option and complete as the server type. This is recommended in a farm configuration.

Next you would think to use either PSCONFIG or PSCONFIGUI to create the farm. Well you would be wrong

PSCONFIG.EXE -cmd configdb -create -server neilhw2k8r2 -database sharepoint_2010_config -user neilhw2k8r2\administrator -password ******** -passphrase ********
-admincontentdatabase sharepoint2010_admincontent

Results in

The specified user neilhw2k8r2\administrator is a local account.

Local accounts should only be used in stand alone mode.

So how do we get around this limitation without using the corporate domain or else promoting the server to a domain controller.

Windows PowerShell is your friend, New-SPConfigurationDatabase allows you to specify none domain credentials for the farm.

To execute this command launch the SharePoint 2010 management shell (in the same location as the central admin link) and simply type the command at the cursor and press enter.

The beauty of the Windows PowerShell approach is you get prompted for the missing command line attributes instead of the rather horrible error dialog that PSConfig throws at you

After this completes you will find in SQL a new configuration database and an admin content database (unfortunately the GUID is back but that can be fixed if necessary)

Next the simplest way to complete the installation is revery back to PSConfigUI as you now are starting with the server already joined to the farm.

Follow the wizard through the same options as you had with SharePoint 2007 and complete the installation/configuration with the following screen

Clicking Fiinish launches the central admin website and after agreeing to report back customer experiences to Microsoft (or not) you get your first look at SharePoint 2010 central admin and the configuration wizards.

So wizard - or - manual configuration. That's a subject for another post so come back for more...

Posted at 4:36 PM by Neil 'The Doc' Hodgkinson | Category: SharePoint 2010; PowerShell; Administration; Central Administration | Permalink | Email this Post | Comments (6)

4/16/2009

Service Pack 2 for the 2007 Microsoft Office System due to ship April 28th

This has been posted by the Office Service Pack team over on their blog. Hit the link to find out more and be sure to start planning for SP2 now!

In the meantime, check out the SharePoint Product Group blog for some news on "Microsoft SharePoint 2010". :-)

Posted at 1:06 AM by Chris Whitehead | Category: Upgrade; SP2; SharePoint 2010 | Permalink | Email this Post | Comments (0)

From The Field

From The Field

11/2/2009

10/19/2009

4/16/2009

Error