Showing posts with label Microsoft SharePoint 2010. Show all posts
Showing posts with label Microsoft SharePoint 2010. Show all posts

Friday, June 28, 2013

SharePoint 2010 Event ID 6482 - Part 2

This is a follow up to an earlier blog post we wrote. In that case, clearing the SharePoint cache on all the servers in the farm did the trick. We recently saw the 6482 event log error again and tried clearing the cache, but this time it didn't work.

What else was going on?

  • We had just migrated the SharePoint databases from SQL 2008 to SQL 2012.
  • Looking at the services on the search server, the SharePoint Server Search 14 service would fail starting up.
  • When we tried to do anything in Application Management - Manage Service Applications - Search Service Application (ex: look at content sources, crawl log, crawl rules, etc...) it would generate a SharePoint error with a correlation ID.
How did we fix it?

After scouring the Internet, we found someone who got the search app running again by adding the service account used to run the search application to the local admin group on the server. Once we did that, we were able to start the SharePoint Server Search 14 service through the services interface. Once it was going, we simply removed the account from the admin group.

Wednesday, May 23, 2012

New eBook for Splitting an Oversized Sub Site into a New Site Collection & Database

Most companies strive to implement solid governance plans and design their site structure accordingly, but reality often gets in the way. What was supposed to be a small site can have a sub site which grows unexpectedly. Next thing you know, your sub site alone has grown to over 100 GB. What do you do? If you don’t care that the URL of the sub site changes, then you can simply copy it to a new site collection with a new content database. This usually isn’t an option when people have links in documents and SharePoint sites that point to the original location. Moving it and trying to put forwarders or links to the new location is simply too painful. This detailed eBook will show you how to split that troublesome sub site off into a new site collection with its own content database using powershell and central administration while maintaining your URL structure. You'll get all the required steps with screen shots for the low price of $9.99 USD. If you're not satisfied, we'll gladly refund your money!




Monday, May 7, 2012

New eBook for Automating SharePoint Backups with PowerShell

We've had a lot of requests for more details on how to setup automated SharePoint backups with PowerShell, so we've gone ahead and created a detailed ebook which outlines the steps and permissions you need to get your backups up and running. In addition to screen shots, there are also copies of the scripts we use as well as an email notification section that will let you know if your backups failed. Simply click on the Buy Now button below and you can pay with your Paypal account or credit card. At only $9.99 USD, it's thousands cheaper than a 3rd party solution and will let you sleep a little sounder at night. If you're not satisfied, we'll gladly refund your money!





Monday, April 30, 2012

Windows PowerShell Command Builder for SharePoint 2010 Products and Office 365

If you're like us, you're starting to figure out that you can do much more with SharePoint through PowerShell than you can through Central Admin. Microsoft recognize that not everyone is comfortable with PowerShell so they've created an excellent tool to help rookies create scripts they can use for everyday administration tasks.


Windows PowerShell Command Builder for SharePoint 2010 Products and Office 365 is a Silverlight® 4 application that is designed to help IT professionals and power users learn how to use Windows PowerShell for administrative tasks. The Windows PowerShell Command Builder enables IT professionals and power users to visually assemble commands related to SharePoint 2010 Products and Office 365 in the browser and take those commands to their respective products.


You can access the tool here: http://www.microsoft.com/resources/TechNet/en-us/Office/media/WindowsPowerShell/WindowsPowerShellCommandBuilder.html


And the getting started guide is here: http://www.microsoft.com/download/en/details.aspx?id=27588


Here's a screen shot to give you an idea of how the drag and drop interface looks:


If you're interested in learning more about administering SharePoint with PowerShell, have a look at the following:


http://dmitrysotnikov.wordpress.com/2010/04/14/sharepoint-2010-powershell-cheat-sheet/
http://technet.microsoft.com/en-us/sharepoint/ee518673
http://technet.microsoft.com/en-us/library/ee806878.aspx


Happy scripting!

Friday, April 27, 2012

List of SharePoint 2010 Site and List Templates

The following is a handy list of all the available site templates followed by the list templates in SharePoint 2010:



Thursday, March 17, 2011

SharePoint 2010 December Cumulative Update

The SharePoint 2010 Foundation and SharePoint Server 2010 Cumulative updates are available from the SharePoint Update site:

http://technet.microsoft.com/en-us/sharepoint/ff800847.aspx

We're running SharePoint 2010 in a farm configuration with two web front ends, and two application servers. To properly update the environment, Microsoft recommended that we use the following procedure:

  1. As always, make sure you have a backup of the environment.
  2. Login to the servers with the same account you used to install SharePoint.
  3. Run the Foundation updates on all the servers in the farm and reboot.
  4. Run the Server updates on all the servers in the farm (presuming you have server installed). Microsoft told us running the Server updates alone might be fine, but they recommended running the Foundation updates first. Re-boot all servers after the second update is applied.
  5. Run the SharePoint Configuration Wizard on the server that hosts the Central Admin site.
  6. Run the SharePoint Configuration Wizard on the other servers.
  7. Note that you can also run the configuration wizard from powershell: PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures 
  8. You must restart the User Profile Synchronization service after installing this cumulative update. For more information see the Start the User Profile Synchronization service section in the Configure profile synchronization article in the library.
Here's some info from MS on known issues with the updates:

http://support.microsoft.com/kb/2459257

That should be all. Let us know if you have any issues.

Wednesday, February 23, 2011

Error Overlaying Exchange Calendars in SharePoint 2010

We recently came across an error when users tried to overlay their Exchange calendars on a SharePoint 2010 calendar. Basically, they would browse to the calendar.aspx page and select the Calendar tab in the ribbon. Next, they'd select the Calendar Overlay option and enter the OWA URL and Exchange Web Services URL.




When they hit OK and tried to view the calendar they got an error saying:

"Could not establish trust relationship for the SSL/TLS secure channel with authority"

The solution is to export the certificate you're using on your Exchange Outlook Web Access server to a .cer file and save it to somewhere you can access it from your local machine. Next, login to Central Admin and select Security - Manage trust - New

Give it a simple name like OWA and provide the location to the certificate. Hit OK and you should no longer get the error when you add and Exchange calendar.

Here's an article with a little more explanation from Microsoft: http://support.microsoft.com/kb/982982

Thursday, September 23, 2010

SharePoint 2010 Network Load Balancing

In an effort to make my web front end severs a little more redundant, I introduced Windows Server 2008 R2 Network Load Balancing to my environment. After configuring the environment as per Microsoft documentation, I was not able to connect to the virtual IP I'd setup for my test site collection. After banging my head against the wall and rebuilding the servers a couple of times, I opened a ticket with Microsoft.


It turns out that you can't use NLB in the recommended unicast configuration if your cluster nodes are on two separate VMWare ESX hosts as per this article: http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1556&sliceId=1&docTypeID=DT_KB_1_1&dialogID=26310418&stateId=0 0 26304946


To learn more about the potential problems you might encouter if you use Cisco switches, have a look at the following:


http://www.cisco.com/en/US/products/hw/switches/ps708/products_configuration_example09186a0080a07203.shtml


And from Microsoft:


http://technet.microsoft.com/en-us/library/cc781305(WS.10).aspx

In the end, I reconfigured the NLB nodes to use Multicast mode and then utilized the Cisco documentation to create a static entry for the MAC of the NLB cluster virtual IP at the local gateway.


Tuesday, September 21, 2010

DocAve Version 5 for SharePoint 2010

Up until recently I've been running my backups using the built in backup and recover tool and Powershell (see http://imperfectit.blogspot.com/2010/03/automate-sharepoint-2010-farm-backups.html), but my environment has started to grow and become more complex. That, and it's larger than the recommended 150 GB limit "suggested" by Microsoft. As a result I had to find a more robust data protection solution. After much testing I went with AvePoint's DocAve v5.

DocAve Backup and Recovery for SharePoint 2010 offers two types of backup and recovery: Granular and Platform


Granular Content and Data Protection

• Supports SharePoint 2010, Microsoft Office SharePoint Server (MOSS) 2007 and Windows SharePoint Services 3.0 environments (via DocAve v5), and SharePoint Portal Server 2003 and Windows SharePoint Services 2.0 (via DocAve 4.5). Support for SharePoint 2001 is available – please contact an AvePoint representative).

• Full fidelity backup and restore of all lists, libraries and items (including Events, Links, Tasks, Contacts, Announcements, Discussion Boards, Surveys, Issues, Custom Lists, Areas, Sub Areas, Portal Links, Workflow Definitions, Layout Templates, and Site Definitions, along with access permissions, metadata and version histories)

• Backs up and restores SharePoint workflow definitions

• Full fidelity item-level restore from DocAve, SQL native backups created by T-SQL script or a maintenance plan, DPM, IBM-TSM, HP Data Protector, as well as third-party embedded SQL backup engines, including HyperBac and LiteSpeed Engine

• Granular, item-level restore with sliding timeline view, along with full text keyword search and identification criteria mask search

• Restore content to different SharePoint instances or locations, including file systems and networked file shares with DocAve's "out-of-place restore" functionality

• Manual and Automated Data Pruning feature helps manage historic SharePoint backup data and improve access speed to more recent backups

• Data Coalescing feature allows collapsing incremental backups into one backup data set for easy retrieval.

• Item-level "out-of-place restore" for complete hardware failure

• Fast granular backup speeds, up to 60GB/hour

Comprehensive Platform Protection

• Backup and recover entire SharePoint farms or selective components including all servers and back-end SQL databases with all configurations, Index/Job servers, as well as front-end IIS settings and file system resources

• Quickly and selectively restore individual or a combination of farm components (content databases, web applications, SSP, etc.)

• Safeguard front-end web server resources (IIS settings, Template files, user selected resources, local file systems, etc.)

• Backup InfoPath form templates, Project Server content and Site Definitions

• Support for SharePoint Features

• Up-to-the-minute restore using SQL logs restoration

• Leverages Volume Shadow Copy Service (VSS) to ensure consistent point-in-time backups

• Fast platform backup speeds, up to 100 GB/hour

• Efficient data streaming via open standards, including VDI and VSS without staging location requirements

If you've worked with this product or others, I'd be interested to hear your opinions.

Thanks!

SharePoint 2010 Anitvirus Exclusions

I recently updated the local antivirus on my SharePoint 2010 server and noticed users were getting "access denied" errors when trying to upload documents. Turns out I had forgotten to update the folders my antivirus solution should ignore.

A quick search turned up this: http://support.microsoft.com/kb/952167

Basically go to the drive you installed SharePoint 2010 on (D: drive in my case) and exclude the following:

Drive:\Program Files\Microsoft Office Servers\14.0\Data
Drive:\Program Files\Microsoft Office Servers\14.0\Logs
Drive:\Program Files\Microsoft Office Servers\14.0\Bin

The above folders handle indexing for your farm.

Tuesday, June 22, 2010

SharePoint 2010 Granular Backup and Restore - Recovering Data from an Unattached Content Database

he built-in backup tool in SharePoint 2010 accommodates backing up the following:

• Back up a farm
• Back up a farm configuration
• Copy configuration settings from one farm to another
• Back up a Web application
• Back up a service application
• Back up search
• Back up the Secure Store service
• Back up a content database
• Back up databases to snapshots
• Back up customizations
• Back up a site collection
• Export a site, list, or document library
• Back up or archive logs

See here for more detail: http://technet.microsoft.com/en-us/library/ee428315.aspx

Sounds pretty good right? What if you have a user who deleted a list, library or even an individual document? If it's not sitting in the recycle bin for the site collection, then what?

The answer is a new feature called granular restore which gives you one more option to use before you have to go to an expensive third party backup and restore solution. The only catch is that you have to have a SQL backup of the content database in question that you can mount in SQL using SQL Management Studio. To be safe, I use the built-in SharePoint 2010 backup tool to run farm backups (How to Automate SharePoint 2010 Farm Backups), but I also do regular SQL backups. In the event of some type of disaster, I've given myself a few options for doing a restore.

Step 1

In SQL highlight the content database you want to restore, right-click it and select Tasks - Restore -Database. In the "To Database" field, type a name for the new database (ex: DatabaseName_restore). Specify the point in time you want to do the restore from.

Step 2

Go into Central Admin on the SharePoint server and select Backup and Restore - Recover data from an unattached content database. Specify the SQL server and database name you created above during the restore. Select Browse Content and hit next.


Step 3

Select the site collection, site, and list or library you want to restore. Specify that you want to export the selected content, and specify a location for the file. I find the best way to locate the library, list, etc that I want to restore is to use the Search field that's presented to you.
When you hit Next, you'll be prompted for the location you want to export the site to. I just use a local folder. Next, hit Start Export.
Step 4

Now that you exported the data from the restored database, you can import the data into the production site to restore the missing list, library, document, etc.

Open SharePoint PowerShell while logged in as Farm Admin and run the Import-SPWeb command to specify the identity of the web you're working with, and the path to the restore file you created above:

Note that you specify the root web, and it will restore the data you specified when you browsed the restored database to its original location. To learn more about what options are available when importing data visit http://technet.microsoft.com/en-us/library/ff607613.aspx.

Wednesday, June 9, 2010

SharePoint Manager 2010

Although SharePoint 2010 offers the Central Administration Site and PowerShell as methods to expose current settings in your SharePoint environment, they can often be a little clunky to work with.

If you've never seen it, you're going to love SharePoint Manager 2010. It's a free download from codeplex. As the description for the tool states, "SharePoint Manager 2010 is a SharePoint object model explorer. It enables you to browse every site on the local farm and view every property. It also enables you to change the properties".

To get your very own copy for free, simply visit http://spm.codeplex.com/.

I first stumbled on this tool when I was going through application event logs on my SharePoint 2010 server and couldn't figure out what site certain errors were referring to. As many of you know event logs simply use the ID of a site (ex: 0a90494e-c226-4067-9762-7d75f952c803). A simple Google search for linking ID's to names turned up SPM 2010. Now I can simply drill down to my Site Collections with the tool and it's easy to see:

The tool is also very handy for finding all your application pool and IIS settings, not to mention having a look at what's in a sites recycle bin. You can also look at quota settings, as well as what features or services are deployed. Curious to know who has permissions on a site or what lists are in a site? Just drill down and the information is there!

Some additional points:
  • The application has to be installed on the SharePoint Server you want to work with.
  • You have to be logged in as a SharePoint administrator.
  • The tool has multilingual support. 
  • It uses the SharePoint object model and doesn't access SQL directly.
  • It was architected and designed by Carsten Keutman - http://www.keutmann.dk/. Thanks Carsten!
Download it today and let me know what you think. If you know of any other tools other admins might be interested in, pleas let me know.

Wednesday, May 12, 2010

List All SharePoint 2010 Databases

If you're like me you've setup numerous SharePoint 2010 test boxes in order to get comfortable with all the great new features. Because I'm running in a test environment I hadn't been paying too much attention to the SQL server I was using. Yesterday I logged in and found a staggering number of similarly named databases which were no longer being used because the test boxes were done.

So how do you figure out which databases are which? There's a great SharePoint Powershell cmdlet you can run on your SharePoint server that will give you a list of all the databases your server is using:

Get-SPDatabase | Sort-Object disksizerequired -desc | Format-Table Name

When you run the command, you'll get a list of all the databases similar to the following:

Now that you have your list, log into SQL Server Management Studio and delete the corresponding databases:

Get-SPDatabase | Sort-Object disksizerequired -desc | Format-Table Name | out-file c:\databases.txt

You can also see how big the databases are by running the following:

Get-SPDatabase | Sort-Object disksizerequired -desc Format-Table Name, @{Label ="Size in MB"; Expression = {$_.disksizerequired/1024/1024}}



Tuesday, May 11, 2010

Installing the RTM Version of Microsoft Office Web Apps 2010 (OWA)

I recently had a request from my users to test Office Web Apps in our new SharePoint 2010 RTM environment. This feature comes in very handy if you have a number of users who don’t have Microsoft Office 2010 installed on their client computers yet. Most of my users are running legacy versions of Office.

For my test environment, we set apps to open in the client by default (not the browser) so we don't break existing document links in the site collections. You can achieve this by following this procedure.

1. Go to Central Administration and select Site Actions - Site Settings – Site Collection Administration and click on Site Collection Features.

2. Activate the Open Documents in Client Applications by Default feature.

Run the OWA setup

1. Run setup.exe from the root of the OWA installation source, and input your product key.

2. Accept the license agreement and specify an install path and hit Install Now.




When the install finishes, you’ll be prompted to open the Configuration Wizard. Click Next when the Wizard opens and answer yes to the service re-start warning. Let the configuration finish and perform the following steps:

Start the service instances

A service instance provides the physical location for a service application. For each server that you want to run the Office Web Apps service applications; you must start the service instances. You can start the service instances by using SharePoint Central Administration or by using Windows PowerShell.

Procedures in this task will start the service instances on those servers specified. This task must be completed after you have run WCSetup and PSConfig on each server in the farm.

To start the service instances by using Central Administration

1. Click Start, point to All Programs, Microsoft SharePoint 2010 Products, and then SharePoint 2010 Central Administration.

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

3. On the Services on server:page, in Server, select a server, and then start Excel Calculation Services, Word Viewing Service, and PowerPoint Service. Repeat this step for each server in the farm you want to run Office Web Apps services. The OneNote Web App does not use a SharePoint service.


Now to test.

Upload an Office document into a document library and select the drop down menu:


When you select "Edit in Browser", the web app version of Word will open and you're free to edit your document.


Try it out for yourself and let me know how it works for 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.