Monday, April 19, 2010

Microsoft Office SharePoint Server 2007 Event ID Errors 6396 and 6482

I recently had a Microsoft Office SharePoint 2007 server start to generate the following event log errors:



I didn't really notice any issues with the SharePoint site itself, but when I tried to run a backup it would error out. Upon closer examination, I noticed that one of our admins had changed the account Office SharePoint Server Search service was using to run. Although the service was started, it wasn't using the account I'd specified when setting up the Office SharePoint Server Search service through Central Administration.

After setting the service to use the orriginal account through Central Administration - Operations - Services on Server and doing a re-boot the event log errors disappeared and my backups worked again. While looking for the cause of the error on Google, I noticed several other people had a similar issue caused by the search service account not having log on locally rights on the server.

Monday, April 12, 2010

SharePoint 2010 Server Search Vs. FAST Search Server 2010

I've been working with some of the members of our internal SharePoint 2010 team to try and determine if there's any benefit to rolling out FAST search in our new SharePoint 2010 environment. We're currently using WSS 3 and SharePoint Portal 2003 so our current search isn't great, but after a little investigation, I don't think we really have a driver to roll out FAST search. The new functionality found in basic SharePoint 2010 Search looks like it will meet our needs for now.

If you're curious to know what feeatures FAST adds to the basic out of the box SharePoint 2010 install, have a look at the following table (click on it to enlarge the image):

You can also find a lot more detail on both versions of search in their respective evaluation guides:

Basic

FAST

Finally, there's an additional cost per server to install FAST, although I'm not entirely sure what it is? If anyone has more info, I'd love to hear from you.


Wednesday, April 7, 2010

Installing Microsoft Project 2010 Beta on a Microsoft SharePoint 2010 Beta Farm

• Add the SharePoint setup account to local admin. Also needs “log on locally permissions”. Also add it to the required SQL roles http://technet.microsoft.com/en-ca/library/cc262243(office.14).aspx.


• Run SharePoint 2010 Enterprise pre-requisite install:


• Run SharePoint 2010 Enterprise setup and chose Server Farm:

Chose Complete and change the file locations if you like. I move them to the D and E drive on the server.


When Setup finishes, run the Configuration Wizard. Click Next, then Yes, then select Create a New Server Farm.

Next, enter your database and farm account information:
Next, enter your farm passphrase (make one up).

Enter a port number for your Central Admin site (I use 1111 for all my servers) and chose NTLM:





Run the setup wizard and enter service application account:

Reboot the server and login with the SharePoint farm admin account.

Run the Project 2010 install (Run As Administrator), and select Install Project Server. The pre-requisites were installed when SharePoint was installed.

Enter your product key, accept the license, and hit Install Now.

When it finishes, run the SharePoint Configuration Wizard.

Hit Next, then Yes to the warning:


Next


To refresh installed products on the farm

Click Start, click All Programs, click Microsoft SharePoint 2010 Products, and then right-click SharePoint 2010 Management Shell and click Run as administrator.

At the Windows PowerShell command prompt (that is, PS C:\>), type:

Set-SPFarmConfig –InstalledProductsRefresh

Press ENTER.

Close the Windows PowerShell window.

To start the Project Application Service

On the SharePoint Central Administration home page, in the System Settings section, click Manage services on server.

On the Services on Server page, select the server where you want to run the Project Application Service from the Server drop-down list.

On the Service list, click Start next to Project Application Service.

To start the PerformancePoint Service

On the Central Administration home page, in the System Settings section, click Manage services on server.

On the Services on Server page, select the server where you want to run the PerformancePoint Service from the Server drop-down list.

On the Service list, click Start next to PerformancePoint Service.

Once you have started the Project Server and PerformancePoint services on the desired computers in the farm, you must create a service application for each service.

To create a Project Server service application

On the Central Administration home page, in the Application Management section, click Manage service applications.

On the Manage Service Applications page, on the ribbon, click New, and then click Project Server Service Application.

On the Create Project Web App service application page:

Type a name for the service application in the Project Web App service application name box.

In the Application Pool section, choose an existing application pool or type the name of the application pool you want to create in the Application pool name box.

Select the Configurable option, and choose the managed account you want to use to run the application pool.


Click OK.

To create a PerformancePoint service application

On the Central Administration home page, in the Application Management section, click Manage service applications.

On the Manage Service Applications page, on the ribbon, click New, and then click PerformancePoint Service Application.

On the New PerformancePoint Service Application page:

Type a name for the service application in the Name box.

Select the Add this service application’s proxy to the farm’s default proxy list check box.

In the Application Pool area, choose an existing application pool or type the name of the application pool that you want to create in the Application pool name box.

Select the Configurable button, and choose the managed account that you want to use to run the application pool.

Click Create.

When the service application has been successfully created, click OK.
The next step is to create a top-level Web site if one does not yet exist, and give users read permission to that site. If there is not yet a top level Web site, create one using the following procedure.

To create a top-level Web site

In Central Administration, in the Application Management section, click Create site collections.

Choose a Web application from the Web Application drop-down menu.

Note:

If no Web application is available, you will need to create one. For more information, see Create a Web application (SharePoint Server 2010).


Type a title for the site collection in the Title box.

In the Template Selection section, choose a template for the site.

Note:

Project Server 2010 does not require a specific template. You can choose one appropriate for your organization.

In the Primary Site Collection Administrator section, type the name of the account you want to use for the site administrator.

Click OK.

To set Read permissions on the top-level Web site

Navigate to the root site (that is, Error! Hyperlink reference not valid.>).

Click Site Actions.

Click Site Permissions.

Click Grant Permissions.

In the Users/Groups box, type NT AUTHORITY\Authenticated Users.

Under Give Permission, select Visitors [Read].

Click OK.

The next step is to create a Project Web App site. Go to the next article, Create a PWA site (Project Server 2010).

Create a PWA site

The Project Web App site requires a Web application to host it. You can use an existing Web application or create a new one for PWA. For more information about creating a Web application, see Create a Web application (SharePoint Server 2010).

Important:

Due to a Project Server Beta issue, you must run the psconfig command before creating the first PWA site. Use the following procedure to run the psconfig command. You do not need to rerun this command for additional PWA sites on the same farm.

To run psconfig

Open a Command Prompt window as an Administrator.

Navigate to \program files\common files\Microsoft shared\Web server extensions\14\bin.

Run the following command:

psconfig -cmd upgrade -inplace b2b


Create a PWA site

The Project Web App site requires a Web application to host it. You can use an existing Web application or create a new one for PWA. For more information about creating a Web application, see Create a Web application (SharePoint Server 2010).

Important:

Due to a Project Server Beta issue, you must run the psconfig command before creating the first PWA site. Use the following procedure to run the psconfig command. You do not need to rerun this command for additional PWA sites on the same farm.

To run psconfig

Open a Command Prompt window as an Administrator.

Navigate to \program files\common files\Microsoft shared\Web server extensions\14\bin.

Run the following command:

psconfig -cmd upgrade -inplace b2b

To create a PWA site

In SharePoint Central Administration, in the Application Management section, click Manage service applications.

On the Manage Service Applications page, click the Project Server Service Application.

On the Manage Project Web Access Sites page, click Create Project Web Access Site.

Complete the Create Project Web Access Site page as designated in the table below:

Option Description

SharePoint Web Application to Host Project Web App - The Web application for the PWA site.

Project Web App path - The path from the root site for this PWA site.

Select a language - The user interface language for this PWA site.

Use Project Web App path as host header - Use this option if you want to host PWA on a root URL (for example, https://www.contoso.com).

Administrator Account - The user account that will be added to the Project Server Administrators security group in this instance of PWA.

Primary database server - The instance of SQL Server where you want to host the Project Server databases. If your database administrator has already created Project Web App databases, specify the names of those databases below. If the databases were not previously created, they will be created automatically.

Published database name - The name of the Project Server Published database for this instance of PWA.

Draft database name - The name of the Project Server Draft database for this instance of PWA.

Archive database name - The name of the Project Server Archive database for this instance of PWA.

Reporting database server - The name of the Project Server Reporting database for this instance of PWA.

Use primary database server - Select the check box to deploy the Reporting database to the primary database server specified above. Clear the check box to deploy the Reporting database to a different database server, and specify the instance of SQL Server that you want to use in the Reporting database name box.

Reporting database name - The instance of SQL Server where you want to deploy the Reporting database (if different from the primary database server).

Quota for SharePoint content in this site - The maximum site storage, in megabytes, for the PWA site.

Quota Warning for SharePoint content in this site - The site storage level, in megabytes, at which a warning e-mail message will be sent to the site administrator.

Click OK.

Project Server will start the PWA site creation process. This may take some time. When the site creation process is completed, the status shown on the PWA site list is Provisioned.
The URL can now be used to connect Internet Explorer, Microsoft Project Professional 2010, and custom-code–based clients to PWA.