Archive for the ‘MS Office SharePoint Server’ Category

SharePoint Current Visitors Web Part

March 5, 2014

The Current Visitors Web Part is intended to display a list of users that are currently visiting a SharePoint site collection.

All you need to do is just to place the Web Part on your SharePoint page (Web Part or Master).

The Web Part is using OOB SharePoint auditing so please note when you activate the Current Visitors Web Part feature on your site collection, this in turn enables the site collection audit logging.

By default the ‘currently visiting’ user is a person who viewed any content in the site collection in the last five minutes. This period can be configured in the Web Part’s properties.

Download

SharePoint 2010/2013 Tabbed Web Part Zone

March 3, 2014

Tabs in SharePoint Project Description

This project shows a working example of how to implement a tabbed web part zone in both SharePoint 2010 and 2013 using only a custom page layout and JQuery.
This project contains a sample SharePoint Publishing Page Layout (For both 2010 and 2013) with a “Tabbed Web Part Zone”.  See http://softlanding.ca/blog/adding-tabs-in-both-sharepoint-2013-and-2010 for more information.
Please see the Downloads section for pre-packaged WSPs for both SharePoint 2010 and 2013 if you’d like to directly deploy it to an on-premise SharePoint farm.
Please contact pbauer@softlanding.ca if you have any questions, comments or issues.

New! Tabbed Web Parts for SharePoint Online (365)

I have now created a manually deployable publishing page layout that is fully compatible with SharePoint Online 2013 with publishing (as well as backwards compatible with SharePoint 2013 Enterprise On-Premise if you do not want to deploy the entire WSP). Please check it out here: https://sharepointtabs.codeplex.com/downloads/get/784784

Download

SharePoint Admin Dashboard

March 1, 2014

Project Description Easily compare server configuration.   “Grid” layout shows configuration of the full farm in one table.  Export to Excel for filter, sort, and pivot chart.

Benefits

  • Do admin tasks faster
  • Scale up beyond RDP
  • Add new servers without fear
  • Verify consistent configuration

Features

  • New WSP format
  • Central Admin > Monitoring > SPDash easy navigation
  • View server config data in table format
  • Export to Excel
  • Timer job refreshes data cache of XML files
  • Wide screen layout for SharePoint 2013
  • Automatic hive (14/15) detection for SP2010/2013 support

Data Sources

  • WMI query
  • Global Assembly Cache
  • IIS web.config
  • Logical disk size and space
  • File versions (to confirm patching)
  • Display Local Administrator members
  • Kerberos SPN for all managed accounts and farm machines

Background SharePoint farms have many servers with various services, applications, traffic patterns, and purposes.  Having “grid” scripts like the below sample screen-shots can save lots of time.  What’s a “grid”?   Simple.   I wanted to build a real-time Excel spreadsheet to display ALL configuration without RDP.  RDP won’t scale.  While great for 1-2 servers, it’s awful for 10+ servers.  Having confidence in your configs and knowing everything is 100% consistent are BIG steps forward for most admins.

Download

The SharePoint Diagnostic Studio 2010 (SPDiag 3.0)

February 5, 2014

Microsoft seems to have snuck in a new tool to help diagnose/troubleshoot issues in SharePoint.  It is part of the Microsoft SharePoint 2010 Administration Toolkit v2.0 and provides SharePoint administrators with a unified interface that can be used to gather relevant information from a farm, display the results in a meaningful way, identify performance issues, and share or export the collected data and reports for analysis by Microsoft support personnel.

image

In the example above I installed it on a WFE server in the SharePoint farm

image

Selecting “New Project” and accepting the server will give you a dashboard.similar to above and access to reports in the following categories: Base, Capacity, Performance, Availability and Usage.  NOTE: Make sure you launch SPDiag 3.0 as “Administrator” if you are running it on one of the SharePoint Servers, you can also run it from a client workstation provided some additional configuration has been performed.

SharePoint Diagnostic Studio 2010: Can be installed on any computer running 64-bit Windows 7, or on any server running a 64-bit Windows operating system. Requires Windows PowerShell 2.0.

To find out more about SPDiag 3.0 including: What’s new, Installing and Configuring, and Using it please check out the link here on TechNet.

The Microsoft SharePoint Team Blog has a great article detailing the features of SharePoint Diagnostic Studio.

SharePoint Diagnostic Studio in combination with SharePoint Health Analyzer and System Center Operations Manager gives an unprecedented view into your SharePoint Farm.

Important Links:

SharePoint 2010 and BCS – Unable to display this Web Part

January 24, 2014

Using SharePoint Designer 2010 to create a external content type and external list is a good choice and spent a lot of time. But when you open the external list in your browser you can get the following error.

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

The reason is very easy. If your source return more than 2000 elements this error occurred. So here are the solutions.

  1. Filter your data by using stored procedure, view etc. and make sure that you didn’t get more than 2000 elements.
  2. Change the Throttling settings

The default value of the throttling is 2000 elements. So you can edit this throttling by run the SharePoint 2010 Management Shell as Administrator.

The console will be open and you have to enter the following command:

Get-SPServiceApplicationProxy

You get a list of all Proxy Services. The Service “Business Data Connectivity Service” is important for us. The rest is in this case Trash ;-)  .

Copy the GUID of the Business Data Connectivity Service and run the following comand, for showing the current throttling settings:

Get-SPBusinessDataCatalogThrottleConfig -Scope Database -ThrottlyType Items -ServiceApplicationProxy <GUID>

For editing the current settings you have to save them into a global variable.

$db = Get-SPBusinessDataCatalogThrottleConfig -Scope Database -ThrottleType Items -ServiceApplicationProxy <GUID>

Set-SPBusinessDataCatalogThrottleConfig -Identity $db -maximum 10000 -default 8000

Now the Throttling is set to a maximum of 10000 elements and a default value of 8000 elements. If you have a source with more then 1000 elements, then you have to set a higher value.

Source

How to delete the default SSP in SharePoint 2007

November 10, 2013

If you attempt to delete the default SSP from within Shared Services Administration, the Delete link will be greyed out. That’s because it’s the default SSP and SharePoint doesn’t allow you to delete the default SSP via the GUI.

One option to get around this is to create a new SSP and change associations to point to that new SSP. Once you do that, the Delete link for the original SSP becomes available because it no longer has any shared services associated with it.

If you’re like me however, and you don’t want to go to all that effort, then there’s a little trick to get around this.

stsadm -o deletessp -title SharedServices -force

The help for the deletessp command won’t actually indicate that -force is a valid switch, but without it, the command may fail. If you run into errors, try running it with -force.

The deletessp command will force the removal of the default SSP. If you receive an error after running the command, that’s fine. Sign back into Shared Services Administration and the delete link for the default SSP should no longer be greyed out.

Once you click Delete, you will be prompted to delete the associated databases, but in my experience, this generally doesn’t work. As a secondary step, I often find myself doing a bit of clean up. Within the database server, I remove all the default SSP databases and within IIS, I remove the SSP web site and application pool.

That should do it! You should now be able to create a new SSP. If you have any problems, or encounted an issue I did not cover here, please contact me or post a comment, I’d be happy to help.

You shouldn’t have to recreate your My Sites web app or any other web app that was associated with that SSP. You should be able to just re-configure those associations. Any search, profile or audience data will be lost and will have to be re-configured.

Source

Free MS Office SharePoint 2013 Themes available

October 15, 2013

Get free SharePoint 2013 Color Themes for the SharePoint 2013 design gallery. Palkotools provides fresh color themes for the latest release of the leading intranet platform SharePoint 2013 as ready to use SharePoint solution packages.

With the latest SharePoint release, website owners can now change the webdesign of any intranet website on their own. A SharePiont administrator can deploy ready to use designs for the use in the SharePoint design gallery.

Download SharePoint 2013 Themes:

Palkotools SharePoint 2013 Themes Gallery

Sample Themes

Image
Palkotools Cool Blue SharePoint 2013 Theme
Image
Palkotools Hot Red SharePoint 2013 Theme
Image
Palkotools Fresh Orange SharePoint 2013 Theme

Theme Gallery: 

Palkotools SharePoint 2013 Themes Gallery

Microsoft SharePoint Server 2013 Useful Resources

October 3, 2013

What’s New in Microsoft SharePoint Server 2013

http://office.microsoft.com/en-us/support/whats-new-in-microsoft-sharepoint-server-2013-HA102785546.aspx

Explore what is new

http://technet.microsoft.com/en-us/library/cc261970(v=office.15).aspx

Capability and Features in SP 2013

http://technet.microsoft.com/en-US/sharepoint/fp142374

SharePoint 2013 Workflows

http://msdn.microsoft.com/en-us/library/jj163986(v=office.15).aspx

Training for IT Pros

http://technet.microsoft.com/en-US/sharepoint/fp123606

What is SkyDrive Pro

http://office.microsoft.com/en-us/sharepoint-server-help/what-is-skydrive-pro-HA102822076.aspx?CTT=5&origin=HA102785546

MS Office SharePoint 2013 Integration with MS Dynamics CRM 2011

September 10, 2013

Microsoft has released an updated component for SharePoint 2013 that allows you to store documents in SharePoint and relate them to CRM entities.  One of the features of CRM 2011 has been the ability to relate SharePoint document libraries to CRM data, but it was only for SharePoint 2010.  This updated component now officially supports SharePoint 2013.  This article will show you how to install and configure it.

1. Download the SharePoint components

Download the latest components from http://www.microsoft.com/en-ca/download/details.aspx?id=5283.  This includes the solutions for both SharePoint 2010 and SharePoint 2013.  Select the appropriate version (in this case I am assuming you are using SharePoint 2013.  Run the installer to extract the files to your local file system.

This will give you three files: AllowHtcExtn.ps1, crmlistcomponent.wsp, and mscrmsharepointeula.txt.

Also note that the installation instructions are not included in this download – they are on the download page itself.  I recommend that you copy/paste the instructions and place them in the same location you just extracted the download file to.

2. Enable .htc extensions

This component makes use of legacy .htc files that are not supported by default in SharePoint.  To enable the use of .htc extensions in SharePoint, open up a powershell command line and run the AllowHtcExtn.ps1 file you extracted using your sharepoint url as the first parameter.

3. Install the solution to your site collection

Navigate to the site collection that you want to use as a base url for your CRM documents library.  Once you are at the correct site, click on the settings icon in the upper right corner of the site and select Site Settings.  On the site settings page, click the Solutions link under the Web Designer Galleries section.  Click Upload Solution in the ribbon, browse to the crmlistcomponent.wsp file that you extracted earlier and upload it to SharePoint.

4. Activate the solution

After you upload the crmlistcomponent.wsp file, click the Activate button in the ribbon to activate the component.

Once activated you can now configure CRM to use SharePoint 2013 as a document library using the standard instructions that are available for CRM 2011.

Finding SharePoint GUIDs using PowerShell

August 6, 2013

2007 version:

[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint")
$site = New-Object Microsoft.SharePoint.SPSite("http://yourserver/sites/yoursite")
$web = $site.OpenWeb("yoursubsite")
write-host "Site: " + $site.id
write-host "Web: " + $web.id
$web.lists | Format-Table title,id -AutoSize
$web.Dispose()
$site.Dispose()

2010 version:

$site = Get-SPSite http://yourserver/sites/yoursite
$web = $site.OpenWeb("yoursubsite")
write-host "Site: " + $site.id
write-host "Web: " + $web.id
$web.lists | Format-Table title,id -AutoSize
$web.Dispose()
$site.Dispose()

Note: You could change $site.OpenWeb(“yoursubsite”)  to $site.RootWeb to get just the top site.


Follow

Get every new post delivered to your Inbox.

Join 31 other followers