SharePoint 2013: A State Service Application Has No Database Defined

Description

After configuring the State Service Application, Central Administration, Monitoring, Health Analyzer, Review Problems and Solutions shows an error; "A State Service Application has no database defined" even though a database does exist.

Solution

I've seen this problem occur when the the State Service Application was configured while logged into the server with an account different from the Farm Account.

1.  Log into the SharePoint Server using the Farm Account.
2.  In Central Administration, Application Management, Service Applications, Manage Service Applications, delete the State Service Application Proxy.
3.  Delete the State Service Application.
4.  Use PowerShell to find the Identity of the State Service Database you would like to remove; Get-SPStateServiceDatabase (Microsoft TechNet, 2012).
5.  Using PowerShell, remove the State Service Application Database; Remove-SPStateServiceDatabase -Identity 00000000-0000-0000-0000-000000000000, replace the zeros with the ID of the State Service Database retrieved from the prior cmdlet.
6.  Using PowerShell, create a new State Service Application.


References

Bisciotti, N. (November, 2012).  SharePoint 2013: How to Configure State Service Application using PowerShell. Retrieved June, 6, 2014 from http://njbblog.blogspot.com/2012/11/sharepoint-2013-how-to-configure-state.html

Microsoft TechNet (July, 2012).  Get-SPStateServiceDatabase.  Retrieved June 6, 2014, from http://technet.microsoft.com/en-us/library/ff608133(v=office.15).aspx

SharePoint Server or Project Server Patch Installed Patch Missing

Description

After installing a SharePoint Server or Project Server Service Pack or Cumulative Update, the Configuration Wizard shows that the Patch is missing from servers in the farm.  In this case, the Configuration Wizard on Server 1 is showing that the Project Server 2013 SP1 Patch is missing, yet it was already installed.

Error:  Some farm products and patches were not detected on this or other servers.  If products or patches are missing locally, you must quit this program and install the required products and patches on this server before restarting this wizard.  If products or patches are missing on other servers, you must install the required products and patches on the specific servers, and you may then click the Refresh button to perform the status check again.

Attempting to run the Project Server 2013 SP1 Patch installation again from the .exe verifies that the Patch is already installed on the system.  Herein lies the problem.  On one hand, the Configuration Wizard will not run because it thinks the patch is missing.  On the other hand, it is not possible to install the patch because it is already installed on local server.  Patch installed, patch missing, patch installed, patch missing.

Solution

The solution to this problem is to run a PowerShell cmdlet on each of the servers that the Configuration Wizard is reporting, patch missing.

1.  Log into the SharePoint Server

2.  Open the SharePoint Management Shell as Administrator

3.  Get-SPProduct -local

This cmdlet retrieves a list of the SharePoint-related products installed in the farm.  It also retrieves the version information for updates installed.  Using the -Local switch retrieves information for local server only.

It may take some time for the cmdlet to run, but once it completes on the servers, you can do a refresh on the Configuration Wizard and the Configuration will recognize that the patches are, in fact, installed on the servers and it will advance automatically to the next screen.  You can continue run the Configuration Wizard upgrade procedure.

References

Microsoft TechNet (May, 2010).  Document farm configuration settings (SharePoint Foundation 2010).  Retrieved March 3, 2014 from http://technet.microsoft.com/en-us/library/ff645390%28v=office.14%29.aspx

Microsoft TechNet (January, 2014).  Document farm configuration settings in SharePoint 2013.  Retrieved March 3, 2014 from http://technet.microsoft.com/en-us/library/ff645391.aspx

Microsoft TechNet (July, 2012).  Get-SPProduct.  Retrieved March 3, 2014 from http://technet.microsoft.com/en-us/library/ff607885.aspx

SharePoint 2013: How to Increase Shutdown Time Out on Central Administration Application Pool

Description

The Process Model, Shutdown Time Limit setting determines how long a worker process is allowed to stay alive.  The default value is 90 second, however, if a process does not finish in time, it will be shutdown.  In a sluggish environment that does not have adequate RAM, then it is common to see issues when interacting with Central Administration.

For example, when creating a Web Application using Central Administration, the process may only partially complete before it is shutdown, leaving a Web Application in Central Administration, a content database in SQL Server, a Virtual Directory folder in the file system, but no corresponding Web site in IIS.  In this case, you have to delete the Web Application from Central Administration and recreate it.


Solution

If possible, meet the minimum hardware requirements for RAM (Microsoft TechNet, 2014).

Additionally, it is possible to increase the value of the Shutdown Time Limit to allow Central Administration more time to process the types of changes that are prone to timeout in an environment that is resource-challenged.

To make this configuration change, open Internet Information Services (IIS) Manager and then expand the server node and click on Application Pools.

Right-click the SharePoint Central Administration Application Pool and select Advanced Settings.

The default Shutdown Time Limit (seconds) is 90.

 Increase the Shutdown Time Limit (seconds) as you see fit.  The example below shows the setting at 480 seconds.

References

Microsoft TechNet (2014).  Hardware and software requirements for SharePoint 2013.  Retrieved February 14, 2014 from http://technet.microsoft.com/en-us/library/cc262485.aspx

SharePoint 2013: Web Application General Settings: Error, Something Went Wrong...

Description

When attempting to modify the Web Application General Settings of a particular Web Application, an error occurs and it is not possible to view the Web Application General Settings page in Central Administration.

Error:  Sorry, something went wrong.  Updates are currently disallowed on GET requests.  To allow updates on a GET, set the 'AllowUnsafeUpdates' property on SPWeb.

Solution

1.  Open the SharePoint Management Shell

2.  Type $WebApp = Get-SPWebApplication http://host.domain.com and press Enter

3.  Type $WebApp.HttpThrottleSettings and press Enter

4.  Type  $WebApp.Update() and Press Enter

5.  Attempt to open the Web Application General Settings from Central Administration.  The page should work at this point.



References

Microsoft TechNet (July, 2012).  Get-SPWebApplication.  Retrieved February 12, 2014 from http://technet.microsoft.com/en-us/library/ff607562.aspx

SharePoint 2013: Set-SPEnterpriseSearchTopology : Could not connect to the HostController

Description

After configuring all of the Enterprise Search components for a new Search Topology, the activation of the Search Topology fails.


Error Message


PS C:\> Set-SPEnterpriseSearchTopology -Identity $SearchTopologyName
Set-SPEnterpriseSearchTopology : Could not connect to the HostController
service on server SERVERNAME Topology Activation could not be started.
At line:1 char:1
+ Set-SPEnterpriseSearchTopology -Identity $SearchTopologyName
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (Microsoft.Offic...tSearchTopology:
SetSearchTopology) [Set-SPEnterpriseSearchTopology], InvalidTopologyExcept
ion
+ FullyQualifiedErrorId : Microsoft.Office.Server.Search.Cmdlet.SetSearchT
opology

Troubleshooting Steps

In Services.msc and in Central Administration, verified the Search Host Controller Service is "Started" on all SharePoint servers in the Topology.

Restarted the Search Host Controller Service


Solution

The Search Host Controller Service was running under the identity of an Application Pool Account, which did not have the required permissions to establish the connection.

In Central Administration, Security, Configure Service Accounts, changed the Service Account assigned to the Search Host Controller Service, to the SharePoint Farm Account.  Ran the activation again, and it was successful.


References

Microsoft TechNet (2013).  Change the default search topology in SharePoint Server 2013.  Retrieved January 29, 2014 from http://technet.microsoft.com/en-us/library/jj862356.aspx

Solution for Site Collection Lock, Missing Site Settings Menu in SharePoint 2007

Description

Logged into a SharePoint 2007 Site Collection as a Site Collection Administrator with Full Control permission level, the Site Actions, Site Collection Settings menu is not present.  The reason for this is that the Site Collection has a lock on it and is in a "Read-Only" state.  In a case observed, this lock occured because a disk partition lacked adequate free space to complete a backup when new Site Collection backup process began.

Once the disk space and backup issues are corrected, an STSADM.exe command can be run from the Command Line that will put the Site Collection in a "Not Locked" state.  This will make the Site Collection Settings menu appear.

As explained below, the desired state is "Not Locked" but problem state is "Read-only":

• Read-only - Blocks additions, updates, and deletions to the site collection.
• Not Locked - Sets the site collection to an unlock status. This is the default setting.

(TechNet, 2008)


Solution

1) Open the CMD line (Start, Run, CMD)

2) Change Directory to Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Bin directory

3) Run this command to unlock the Site Collection:
stsadm -o setsitelock -url http://hostname.domainname.com -lock none

4)  Run this command to verify the Site Collection is Not Locked (None):
stsadm -o getsitelock -url http://hostname.domainname.com

(Aquino, 2009)


Key Words
Site Settings missing, Site Collection Settings menu missing, Site Collection lock, Backup ran out of space. 



References

Aquino, F. (November, 2009).  Moss 2007 Site Action -> Site Settings have disappeared.  Retrieved January, 2014 from http://stackoverflow.com/questions/1809512/moss-2007-site-action-site-settings-have-disappeared

Microsoft TechNet (May, 2008).  Lock site collections (Office SharePoint Server).  Retrieved January 27, 2014 from http://technet.microsoft.com/en-us/library/cc508855(v=office.12).aspx

Windows Server 2012, Windows 8, Product Key and Activate

Description

The "Change product key" link is not visible in Windows Server 2012 or Windows Server 2008 and the license is not activated.


Solution

Enter a Product Key and Activate Windows.

1)  All Apps, Run, slui.exe 0x3, click OK

2)  Type Product Key, click Activate


Reference

Microsoft Support (2013).  "Change product key" link is not available in Windows 8 or in Windows Server 2012.  Retrieved August 17, 2013 from http://support.microsoft.com/kb/2750773

TechNet (2013).  Slmgr.vbs Options.  Retrieved August 17, 2013 from http://technet.microsoft.com/en-us/library/ff793433.aspx

Blindly Diagnosing a RAM Issue affecting SharePoint 2010 W3Wp.exe and SQL Server 2005 Enterprise Edition

I received limited information about an issue.  Here are some ideas.

Description

A SharePoint Server 2010 Farm with a SQL Server 2005 Enterprise Edition database server has RAM issues which are affecting affecting both the Web front end (w3wp.exe) and SQL Server.

Would be Helpful to Know

Is it 32-bit or 64-bit? How much physical RAM is assigned to each server role? What version and patch level is the OS?  What version and patch level is SQL Server? How is SharePoint being used?  How many users?  Are there custom Web parts? Custom Web pages? What are the SQL Server performance counters reading?  When does a memory spike occur?  How long does it last?  When did it start?  What recently changed in the environment?  Are the systems physical or virtual?  What is the server farm topology?

Possible Causes

Need a Service Pack/Patch for OS:  self-explanatory, but need the current information to know if this is a possibility.

Antivirus:  Investigate antivirus software running on the servers.  IIS Forums reported that McAfee Enterprise V8  had a buffer overflow protection feature that was causing problems with w3wp.exe (IIS Forums, 2008).

Incorrectly disposed objects:  Unmanaged memory can lead to memory problems (MSDN, 2010).

Scheduled jobs:  SQL Server maintenance plans, SQL agent jobs (e.g. backups), SharePoint full or incremental crawl schedules can create noticeable degradation while running.

On the SQL Server side of things:  Resource bottlenecks, TempDB bottlenecks, or a slow running user query (less likely in this situation) (MSDN, 2010).  Query the sys.dm_os_memory_clerks and sys.dm_exec_query_memory_grants DMVs to get an idea how SQL Server is utilizing memory.

Reference

IIS Forums(July, 2008).  W3wp.exe memory usage is out of control.  Retrieved March 10, 2013 from http://forums.iis.net/t/1150494.aspx

Microsoft TechNet (2005).  Troubleshooting Performance Problems in SQL Server 2005.  Retrieved March 10, 2013 from http://technet.microsoft.com/library/Cc96654

MSDN (2010).  Disposing Objects.  Retrieved March 10, 2013 from http://msdn.microsoft.com/en-us/library/ee557362.aspx 

MSDN (2010).  SharePoint Dispose Checker Tool.  Retrieved March 10, 2013 from http://archive.msdn.microsoft.com/SPDisposeCheck

Error: SharePoint 2013: Adding ContentDB with No Free Space

Description

When attempting to add a Content Database to a SharePoint Web Application, an error occurs:
"Sorry, something went wrong..."


The error message is self explanatory.  It states that "There is not enough disk space on disk".

Solution

Make free space and then recreate Content Database.  It is time to investigate the reasons why free disk space was drawn down to zero.  This situation should not be allowed to occur on the SQL Server data file partition.  Therefore, an activity plan following the error message should be aim towards preventing this situation from occurring in the future. 

Some initial questions to ask might include:

• Was the initial storage allocation sufficient?
• Is the server storage partitioned properly?
• What is consuming space?
• Are backups configured for the SQL data file partition?
• Are database backup cleanup jobs scheduled?
• Is there any logging on the partition?
• What is the logging retention?

Error: SharePoint 2013: Central Administration - Service Unavailable: HTTP Error 503

Description


When attempting to open the SharePoint 2013 Central Administration Web site, the site does not come up, and there is an error:

"Service Unavailable.  HTTP Error 503. The Service is unavailable."

Cause


The SQL Server services are stopped because the domain Service Account used to run the SQL Server services is locked out.  This is visible from All Programs, Microsoft SQL Server 2012, Configuration Tools, SQL Server Configuration Manager.

Solution

In Active Directory Users and Computers, perform the following:

• Unlock the Service Account
• Ensure that the Service Account is not set to require user to change password at next login
• Ensure that the password never expires
• Verify Group Policies on the Organizational Unit to ensure that the account password is not being expired as a result of an effective policy.  If so, change the policy inheritance on the OU.
• If possible, reboot the SQL Server or manually start all of the services that were affected by the account lockout.

Error: "Unable to display this Web Part"

Description

A Data View Web Part (DVWP) is configured to display data from a Microsoft SQL Server datasource.  However, instead of data from the datasource, the Data View Web Part displays the following error message:

"Unable to display this Web Part.  To troubleshoot the problem, open this Web page in a Micrsofot SharePoint Foundation-compatible HTML editor such as Microsoft SharePoint Designer.  If the problem persists, contact your Web server administrator."

Solution *

1.  Using SharePoint Designer, test the datasource for the DVWP.  One possible cause for this error is that the credentials for the datasource are expired, as indicated in the SharePoint Designer dialog box.

2.  Open SQL Server Management Studio, expand Security, expand Logins, right-click on the Login and click Properties.  Uncheck the "Enforce Password Expiration" checkbox and click OK.

3.  Test the Data View Web Part, datasource again in SharePoint Designer.  If the issue is resolved, test the DVWP also in the Web browser.

* Disclaimer:  This solution represents only one of many possible solutions and may or may not be applicable in your environment.

SharePoint 4.0: Content Type Column Does Not Display in Datasheet View

Thanks to Glyn Clough for suggesting the correct answer to this over Twitter!

Description

When creating a Datasheet View in SharePoint Server 2010 and choosing to display the Content Type column in the view, the Content Type does not appear in the view.

In this Datasheet View Definition, the Content Type column is in position #4.

The Content Type column does not display in the Datasheet View.

This is especially frustrating when working with documents in bulk because you would want the ability to modify the Content Type of multiple documents at one time.  When the Content Type column doesn't display in Datasheet View, it is not possible to modify the Content Type of multiple documents at once.

Solution

The solution is to modify the Datasheet View and set the Content Type column to position #1.

1.  Navigate to the SharePoint site where the Document Library is located.
2.  Site Actions > View All Site Content.
3.  Click on the Document Library to open the default view.
4.  On the Ribbon, click on the Library tab.
5.  On the Ribbon, click on Library Settings.
6.  Beneath the Views heading, click on the Datasheet View, or the Standard View you would like to open in Datasheet mode.
7.  Set the Content Type column to display in position #1.
8.  Click OK to save the changes.

In this Datasheet View definition, the Content Type column is in position #1.

The Content Type column does, indeed, display in the Datasheet View.

References

Clough (2011).  Glyn Clough's Blog - All About Microsoft SharePoint.  Retrieved August 29, 2011 from http://www.glynblogs.com.

SharePoint 4.0: Unable to Open PDF Files in Edit Mode from Document Library

Description

SharePoint users having Adobe Acrobat Professional expect to be able to open PDF files in Edit Mode, directly from a SharePoint document library.  These users are not able to open PDF files in Edit Mode.  When attempting to edit a PDF document directly from a SharePoint Document Library, they receive the error message, "The document could not be opened for editing."

Solution

The issue may be corrected by modifying the Require Check Out setting of the Document Library.

1.  Navigate to the SharePoint site where the Document Library is located.
2.  Site Actions > View All Site Content.
3.  Click on the Document Library to open the default view.
4.  On the Ribbon, click on the Library tab.
5.  On the Ribbon, click on Library Settings.
6.  Beneath the General Settings heading, click on Versioning Settings.
7.  Note the current setting for Require Check Out.  If Require documents to be checked out before they can be edited? is set to No, change this to Yes.
8.  Click OK to save the configuration change.
9.  From the Document Library, invoke the Document Context Menu by hovering the mouse over the title of the PDF document.  Check out a PDF document.
10.  Open the Document Context Menu again, and select to Edit Document (assumes that Adobe Acrobat Professional is installed on client computer).

Refer to Check out and edit a file for more information on the "Use my local drafts folder" prompt.


Reference

Adobe (2011).  Which Acrobat X Software is right for you?  Retrieved August 29, 2011 from http://www.adobe.com/products/acrobat.html.

Microsoft Office (2011).  Check out and edit a file.  Retrieved August 29, 2011 from http://office.microsoft.com/en-us/windows-sharepoint-services-help/check-out-and-edit-a-file-HA010153570.aspx

Error: Microsoft SQL Server: Cannot connect to (local)

Description

Error when attempting to log into SQL Server Management Studio:  "Cannot connect to (local)."

Solution

As the error message indicates, the SQL Server is not accessible.  The issue may be caused by one of the following:

1)  Issue with Server Connection Configuration

Start > All Programs > Microsoft SQL Server > Configuration Tools > SQL Server Configuration Manager

Verify the correct protocols are configured (this will vary based on type of environment).  Refer to Microsoft TechNet article, Choosing a Network Protocol, for further assistance with this topic.

2)  Issue with Service Account Authentication
Start > Administrative Tools > Services
Verify that the SQL Server (MSSQLServer) Service is running.  If it is not running, try to start it.  Make sure the Service Account credentials are properly configured and that the account is not locked out.

References

Microsoft TechNet (August, 2011).  Choosing a Network Protocol.  Retrieved August 29, 2011 from http://technet.microsoft.com/en-us/library/ms187892.aspx.

Error: Content Type Still in Use

Description

When attempting to delete a content type from the site collection, Content Type Gallery, an error is returned:

Error
The content type is in use.
Troubleshoot with Microsoft SharePoint Foundation.
Correlation ID:  50b2222f-ee94-406eb7bb-d12a0be59dcd

Solution

There must be a document library, some place within the site collection using the Content Type that you are trying to delete.  For this reason it is not possible to delete the Content Type.  To fix this issue, identify the document library that is currently using the Content Type.  Change the Content Type of any documents in the library currently set to the Content Type.  Delete or remove the Content Type from the document library.

Once you've done this, it will be possible to delete the Content Type from the gallery.

Links: SharePoint 4.0 Service Pack 1

SharePoint Foundation 2010

KB 2460058: Description of SharePoint Foundation 2010 SP1
http://support.microsoft.com/kb/2460058

White paper: Service Pack 1 for SharePoint Foundation 2010
http://technet.microsoft.com/library/hh301732(office.14).aspx

SharePoint Server 2010

KB 2460045: Description of SharePoint Server 2010 SP1
http://support.microsoft.com/kb/2460045

White paper: Service Pack 1 for SharePoint Server 2010
http://technet.microsoft.com/library/hh285676(office.14).aspx


Related Links

Known issues when you install Office 2010 SP1 and SharePoint 2010 SP1
http://support.microsoft.com/kb/2532126

List of all SharePoint 2010 and Office Server 2010 SP1 packages
http://support.microsoft.com/kb/2510766

Microsoft SharePoint Server 2010 June 2011 Cumulative Update
http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=2536599

Update Center for Microsoft Office, Office Servers, and Related Products
http://technet.microsoft.com/en-us/office/ee748587.aspx

Updates for SharePoint 2010 Products
http://technet.microsoft.com/en-us/sharepoint/ff800847.aspx

Links: SharePoint 4.0: March 2011 Cumulative Hotfix

Descriptions

SharePoint Foundation 2010
KB2475880: Description of the SharePoint Foundation 2010 cumulative update package (SharePoint Foundation server-package): March 3, 2011
http://support.microsoft.com/kb/2475880

SharePoint Server 2010
KB2475878:
Description of the SharePoint Server 2010 Cumulative Update Server Hotfix Package (MOSS server-package): March 3, 2011
http://support.microsoft.com/kb/2475878


Downloads

SharePoint Foundation 2010
Download for Microsoft SharePoint Foundation 2010
http://support.microsoft.com/hotfix/KBHotfix.aspx?kbln=en-us&kbnum=2475880

SharePoint Server 2010
Download for Microsoft SharePoint Server 2010
http://support.microsoft.com/hotfix/KBHotfix.aspx?kbln=en-us&kbnum=2475878

Error: Microsoft SQL Server Shared Feature Directory (INSTALLSHAREDDIR, INSTALLSHAREDWOWDIR)

Description


During an installation of Microsoft SQL Server 2008 R2 x64 Standard Edition on a Windows Server 2008 R2 Service Pack 1 x64 Standard Edition operating system, I encountered issues on the Feature Selection screen.


Issue #1 - While the installation is 64bit, the Shared Feature Directory is hard coded as x86 - this is wrong.


Issue #2 - Error:  "The INSTALLSHAREDWOWDIR command line value is not valid. Please ensure the specified path is valid and different than the INSTALLSHAREDDIR path."

Solution



Aside from the regular disclaimer about don't modify the registry unless you have backups and know what you are doing, I want to also mention that the solution that worked for me does not apply to all situations.  For example, if I experienced this issue while installing on an Itanium processor, then the solution would be different (Microsoft Support, 2011).

So, having said that, the solution for this particular situation was the following:



1.  Open the Registry Editor

2.  Export the following key (as a backup)

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-518\Components\0D1F366D0FE0E404F8C15EE4F1C15094]

3.  Delete the key.

4.  Close the Registry Editor.

5.  Open the Command Prompt (Start > Run > CMD)

6.  Type the following command:

[Path to Setup.exe]\setup.exe /action=install /INSTALLSHAREDDIR=”C:\Program Files\Microsoft SQL Server\" /INSTALLSHAREDWOWDIR=”C:\Program Files (x86)\Microsoft SQL Server\" (MSDN, 2011)

7.  Press Enter.  The SQL Server Setup launches from the beginning.

Notes


"INSTALLSHAREDDIR" is the 64-bit shared component files directory with a path of "Program Files\Microsoft SQL Server" (Microsoft Support, 2011)


"INSTALLSHAREDWOWDIR" is the 32-bit shared component files with a path of "Program Files(x86)\Microsoft SQL Server" (Microsoft Support, 2011)


When specifying the the directories, there are known issues with putting a "\" at the end of the path.  For this reason, omit the symbol.


Examples:
Good - Program Files\Microsoft SQL Server
Bad - Program Files\Microsoft SQL Server\ 



Reference


Microsoft Support (2011). You receive an error message if you change the "Shared component directory" path on the Feature Selection screen when you install SQL Server 2008 on a computer that is running an Itanium-based version of Windows. Retrieved May 17, 2011 from http://support.microsoft.com/kb/955458.


MSDN (2011). How to: Install SQL Server 2008 from the Command Prompt. Retrieved May 17, 2011 from http://msdn.microsoft.com/en-us/library/ms144259(SQL.100).aspx.


MSDN (2011). Feature Selection. Retrieved May 17, 2011 from http://msdn.microsoft.com/en-us/library/ms143786.aspx.


MSDN (2011). File Locations for Default and Named Instances of SQL Server. Retrieved May 17, 2011 from http://msdn.microsoft.com/en-us/library/ms143547(v=SQL.105).aspx.

Error: SharePoint Server 2010 Installation, SharePoint Configuration Failed

Description:

After configuring the operating systems and SQL Server instance in a multi-tiered server farm, I installed the SharePoint Server 2010 prerequisites and server binaries on the first Web front end.  Next, I opened PowerShell and began creating a new farm from the command line.  After only the first step, I received the error shown below.

Windows PowerShell
Copyright (C) 2009 Microsoft Corporation. All rights reserved.

PS C:\Windows\system32> New-SPConfigurationDatabase -DatabaseName "FarmName_Configuration_Database_01" -DatabaseServer "FarmDBSQLAlias" -A
dministrationContentDatabaseName "FarmName_Content_Database_01" -Passphrase (ConvertTo-SecureString "FarmPassPhrase" -AsPlaintext -Force) -FarmCredentials (Get-Credential)
...
New-SPConfigurationDatabase : CREATE FILE encountered operating system error 3(The system cannot find the path specifie
d.) while attempting to open or create the physical file 'I:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\
MSSQL\Data\FarmName_Configuration_Database_01_log.LDF'.
CREATE DATABASE failed. Some file names listed could not be created. Check related errors.
At line:1 char:28
...

So, I navigated to the log directory: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS and opened up the current PSCDiagnostics log file.


CTRL + F "error" brought me to this error:

...
01/20/2011 17:46:26 10 ERR Exception: System.Data.SqlClient.SqlException: CREATE FILE encountered operating system error 3(The system cannot find the path specified.) while attempting to open or create the physical file 'I:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Data\FarmName_Configuration_Database_01_log.LDF'.
CREATE DATABASE failed. Some file names listed could not be created. Check related errors.
...

Solution:

After viewing the log file message, I immediately knew what the cause of the error was.  The SQL Server default path for LDF was not accessible because it hadn't been created yet.  During the SQL Server 2008 R2 installation, I specified a particular default drive letter for MDF and LDF.  After the installation, I changed the default path location for LDF's to a different drive letter, however, the new folder path (I:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Data) didn't exist yet!

The fix was simply to go to the I: drive letter and create the necessary folder paths that I had set as the default LDF location for the SQL instance.

Note:  When you install SQL Server 2008 R2 and you encounter the screen that asks for the default locations, be sure to set the MDF first and then the LDF second.  The reason is that if you do the MDF path second, the installation wizard will reset your LDF location back to the MDF setting.  It's just one of those things!

Windows Server: ADO.NET Data Services Update for .NET Framework 3.5 SP1

This update is required in order to install SharePoint Server 2010 on Windows Server 2008 R2.

"The ADO.NET Data Services framework consists of patterns and libraries that enable the creation and consumption of REST-based data services for the web. This update to the Microsoft .NET Framework 3.5 SP1 provides additional features which extend the functionality provided in version 1.0 of the ADO.NET Data Services framework."
(Microsoft, 2010)

Reference

Microsoft (2010). ADO.NET Data Services Update for .NET Framework 3.5 SP1 for Windows 7 and Windows Server 2008 R2. Retrieved January 3, 2011 from http://www.microsoft.com/downloads/details.aspx?FamilyID=79D7F6F8-D6E9-4B8C-8640-17F89452148E&displaylang=fi&displaylang=en.

Microsoft (2010). A hotfix for the.NET Framework 3.5 Service Pack 1 is available for Windows 7 and for Windows Server 2008 R2 as a prerequisite for Microsoft Office SharePoint Server 2010. Retrieved January 3, 2011 from http://support.microsoft.com/kb/976462.