Archive for the ‘Administration’ Category

‘New Document’ requires a Microsoft SharePoint Foundation-compatible application and web browser – Office 2013 and SharePoint 2010

February 26, 2013

Office 2013 is not compatible with SharePoint 2010.

I have seen when creating content from a document library, a dialog box states that a SharePoint Foundation compatible application and web browser is required to create content.

In order to work around this problem, uninstall InfoPath 2013 and this problem will go away.

This has been tested on Windows 8 running Office 2013 and IE 10.

Advertisements

Troubles opening Windows Explorer from a Document Library in SharePoint 2010

August 4, 2011

Ever come across the issue where a document library refuses to open in Windows Explorer with SharePoint Foundation 2010?

I came across an issue – whenever I opened a document library in Windows Explorer, I was prompted with an Office install set up dialog, requesting for my installation disk.

Yes, I know, strange but it’s true.

To overcome this issue, go to services.msc on your PC/Server and ensure that WebDav client is started. In my case, it was disabled, stopped and well.. enabling it fixed the issue.

Here is a WIKI explaination on what the WebDav client does: http://en.wikipedia.org/wiki/WebDAV

Hope this helps!

Office SP2 Roll Out on 28 April 2009

April 27, 2009

Straight from the SP Team Blog:

Service Pack 2 for Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3.0 due to ship April 28th

Office Service Pack team announced Service Pack 2 for Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3.0 would be available on April 28th. It provides many fixes and performance improvements, as well as some new features. Also with the new service pack, Internet Explorer 8 will be added into browser support matrix as level one, and Firefox 2.0 and 3.0 as level two. We recommend every customer to start planning their patch window to apply this service pack. Please look out for more details on April 28th.

I would recommend that you deploy this on your dev machines to see if there are any potential issues. Keep your eyes peeled in the blogs so that you know what to expect with this new patch.

Cannot create MySite

April 6, 2009

Sometimes, even after adjusting personalised permissions in Shared Services, you’ll get a prompt:

“Your personal site cannot be created because Self-Service Site Creation is not enabled. Contact your site administrator for more information”

In order to fix this, go to Central Administration, Application Management and go to the categorySite Security and click Self-service site management. Enable it (ensuring that the mysite web application is selected) and the problem is fixed (not really a problem, it’s to turn off MySite creation)

Enjoy!

SharePoint Infrastructure Updates & SP1

March 30, 2009

After a clean installation, you can install SP1 without running the Configuration Wizard. Microsoft have an excellent blog outlining the order.

Links to updates:

Infrastructure Update for Microsoft Office Servers (KB951297)x86

Infrastructure Update for Microsoft Office Servers (KB951297)x64

Infrastructure Update for Windows SharePoint Services 3.0 (KB951695)x86

Infrastructure Update for Windows SharePoint Services 3.0 (KB951695)x64

“For reference the following products require the following updates to be applied.

If you are running SharePoint Server 2007 you should:

  1. Install Windows SharePoint Services 3.0 Service Pack 1 (SP1) if you haven’t already
  2. Install 2007 Microsoft Office Servers Service Pack 1 (SP1) if you haven’t already.
  3. Install the Infrastructure Update for Windows SharePoint Services 3.0 (KB951695).
  4. Cancel out of the “SharePoint 3.0 Products and Technologies Configuration Wizard”. (You CAN run the wizard if you want. It will just save you time if you run it once at the end.)
  5. Install Infrastructure Update for Microsoft Office Servers (KB951297)
  6. Run the “SharePoint 3.0 Products and Technologies Configuration Wizard”.”

Content Types

March 19, 2009

Inheritance is incredibly it comes to Content Types. Some may say that it’s vital the Content Types are deployed as features rather than used Out of The Box.

I, however, would recommend that all content types are managed at all times from the root home of your site collection. I made a silly mistake where I added custom columns to a document library that had content type management, this in effect, broke inheritance from home to sub sites and inheritance cannot be filtered upwards.

When you amend content types at library level, it cannot be updated in any form from the home root. You either need to re-build the library or remove the content type and re-apply it. Also, when you remove the content type, you must remove all instances of it first.

I have been going through an exercise of re-attaching document libraries the long way, yes, manually. It gives me far better control of my documentation and I am becoming an expert in knowing what not to do when it comes to SharePoint libraries 🙂

Further information about content types can be found here: http://msdn.microsoft.com/en-us/library/ms472236.aspx

Server Farm Maintainence

March 10, 2009

Most excellent blog was posted and wanted to re-iterate the importance of keeping your server clean.

In summary:

– Install, verify, update SharePoint software.

– Event logging, check event logs and rectify problems, take a farm back up in Central Administration

– SQL Maintenance plans including “Check Database, Shrink Database, Reorganize Index, Clean up the History as well as Defragmenting your databases”

– Document your install!

Search Errors – Error Microsoft Windows SharePoint Services Protocol Handler

February 20, 2009

In order to clear this error that you may see in your error log in Central Administration, stop the Search Service.

This will detatch the indexer from the farm.

Start it up again and assign the correct server as the indexer.

Go to Shared Services and make sure you edit it so that you choose the indexer.

Go to your search settings, reset crawled content and re-crawl.

After I did that, got another horrible error: Element not found. (Exception from HRESULT: 0x8002802B (TYPE_E_ELEMENTNOTFOUND)) (ComInterop Exception).

Yes, nasty. I re-crawled content from the server directly and it is nicely crawling content again.

STSADM Command Tool

January 30, 2009

When I first started out administration of SharePoint 2007, when I first heard of STSADM, I thought…. what on earth is it?!

Firstly, where is the STSADM command and where can I find it?

The STSADM tool is found under C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN.

Why is this tool useful?

For a variety of reasons, you can deploy custom solutions, use it as a back up and restore tool, attach databases that were once working.

I recently downloaded a pretty neat utility that expands on the STSADM tool from Gary Lapointe’s blog. http://stsadm.blogspot.com/

As a starter for 10 with this tool, here is a sample the command line script to add a WSP file to your farm. For example, I want to deploy UzmaCustom.wsp which is held on my C:\ drive

stsadm.exe -o addsolution -filename C:\UzmaCustom.wsp
stsadm -o deploysolution -name UzmaCustom.wsp -allowgacdeployment -immediate

You’ll get on-screen prompts to say that the deployment was successful and deployed. To check deployment, go to Central Administration and go to Solution Management under Operation to check the deployment, here you could actually retract or deploy the solution.

Of course the deploysolution does have other parameters you could use – See Technet for further details.

Hope this helps!