Category Archives: SharePoint

SnapTeam – Social Productivity Solution for SharePoint 2010 and Office365

This looks like it might be really good but I wonder what it costs. At the top it says “free” but at the bottom it states: You can activate and deactivate applications with a click of the mouse. You get billed only for what you use.

SnapTeam by SnapworkSocial

Feature list at a glance:

  • Microblogging – Share anything with your team quickly and communicate with specific team members using @replies. Streamline your productivity by asking for feedback, tag content, and much much more.
  • Team Feed – The team feed organizes all your team’s activities into one easy to digest page.  Track documents, post links, videos, pics, ask questions, assign tasks and provide insight all in one place.
  • Rich Profiles – Quickly explore what your team mates are up to with one click.  Profiles allow you to keep tabs on your team, explore common topics, locate expertise, and communicate all in one simple page.
  • Tagging – Tagging makes the chore of organizing data a breeze!  You can tag your posts as you create them or allow your team to assign tags later.  Your activity stream can be filtered by tag to make finding that proposal much easier or help subject matter experts discover your questions.  With infinite tag context gain insight by discovering content that would ordinarily go unnoticed. Tagging is the fun way to stay organized!
  • Bookmarks – Bookmarks make it easy to keep track of the information that’s important to you.  You can store any number of bookmarks and locate items, docs, links, or any other activity by tag, keeping the information you need at your fingertips.
  • Task Integration – The industry’s first social workflow engine makes social accountable and productive with inline task integration.  Assign tasks to get questions answered, get projects moving, review documents, or anything else you can think of!

SharePoint 2010 Application Templates for Health Organizations

Microsoft has come out with application templates for those who work in academic medical centers or health organizations. See the list of the various templates below:

SharePoint 2010 XML noredirect required

In upgrading from SharePoint 2007 to SharePoint 2010, one of my InfoPath forms would not return the XML data for a form field. The error I was getting was:

XML data that is required for this form to function correctly cannot be found

If I previewed the form in InfoPath 2010, I had no issues. It was only on the site that this error would occur. 

Here is my original data connect XML link:

http://sharepoint/_vti_bin/owssvr.dll?Cmd=Display&List={4B14953C-5E0D-45A9-B99A-6967F8FB8A73}&XMLDATA=TRUE

This worked fine in SharePoint 2007, no issues. In SharePoint 2010 apparently, it needs to look like this:

http://sharepoint/_vti_bin/owssvr.dll?Cmd=Display&List={4B14953C-5E0D-45A9-B99A-6967F8FB8A73}&XMLDATA=TRUE&noredirect=true

After that, it works fine. 

reference: http://msdn.microsoft.com/en-us/library/ms478653.aspx

Migrating from SharePoint 2007 to 2010

Last night I attended a meeting of the Triangle SharePoint Users Group (aka TriSPUG) here in Raleigh where they had a presentation by Jason Medero of B&R Solutions on “Migrating from SharePoint 2007 to SharePoint 2010 – Tools and Options.” In the presentation, Jason presented four ways to migrate and upgrade your current SharePoint 2007 farm to SharePoint 2010. Those four approaches are:

  1. In-Place Upgrade – the easiest approach but has the least amount of flexibility in configuration and has the most downtime. Also, depending on your hardware, it updates all the databases simultaneously which slows down the process and can take days or even weeks if this is attempted on a site with large content databases. And there is no ability to pause or rollback the upgrade.
  2. Database Attach – this is where you detach your content databases, create a new installation of SharePoint 2010, recreate your configuration, and finally reattach the content databases. This method has your site down while you upgrade.
  3. Hybrid Read-Only Database Attach – This method has you put your current site in read-only mode as you use backups to do the database attach on the new farm. This allows for users to continue using the site as you set up the new one. Once complete, you do a DNS change and point everyone to the new farm.
  4. Hybrid Detach Database Upgrade – Here you detach your content databases first, do the in-place upgrade, then reattach those content databases. The advantage with this is that the configuration is upgraded without having to reconfigure.

Take a look at the video below to hear Jason discuss all of these options as well as the tools to use before you start any of these methods. WARNING: the audio in the video is very loud so adjust your speakers prior to hitting play.

http://livestre.am/K98m

‘There is no web named’ in logs

Recently I noticed quite a few “There is no web named [link to specific aspx file like AllItems.aspx]” in my SharePoint 2007 logs. Most online boards say to ignore the error, it’s just “noise in the logs.” Well, it can be a lot of noise.

If you remove the item from the Quick Launch (List Settings > Title, description and navigation > Display this list on the Quick Launch?), the errors go away. If you add it back, so do those errors. Solution?

Nope, no solution, but you can at least workaround it. If you set “Display this list on the Quick Launch?” to “No” and then go into your site navigation and add a link back to that list, no more errors. It’s not a pleasant solution but the look is the same to the user and no more errors clogging up my logs.

STS#0 and the “failed to read package” SharePoint errors

Just some reminders to myself, the STS#0 template is the blank template. So if you get the “you cannot import because of STS#0 and STS#1 templates do not match”, you have to delete/create your Site Collection again but this time choose the blank template instead of the team site (which I assume is STS#1).

 

Also when doing an import, if you run into the “failed to read package” error that's likely because you don't have enough disk space on drive C even if you're importing cabs located on a different drive.

Non-supported field type HTML

Windows SharePoint Services 3.0 was unable to backup because of a field type 'HTML' error. To resolve this, you have to remove the “rogue” references to the content type. It's not a pretty process, but it did work. You may have to write up some code to identify which lists are referencing the bad content type if you have a huge site. Just make sure you back everything up before mucking around in the SharePoint database.

This was the original error I had:

Field type HTML is not installed properly. Go to the list settings page to delete this field.    at Microsoft.SharePoint.SPFieldCollection.CreateSPField(Int32 index)
at Microsoft.SharePoint.SPFieldCollection.EnsureSPField(Int32 index)
at Microsoft.SharePoint.SPFieldCollection.get_Item(Int32 iIndex)
at Microsoft.SharePoint.SPFieldCollection.ItemAtIndex(Int32 iIndex)
at Microsoft.SharePoint.SPBaseCollection.SPEnumerator.System.Collections.IEnumerator.get_Current()
at Microsoft.SharePoint.ApplicationPages.FieldListRenderer.OnPreRender(EventArgs e)
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

 

 

SharePoint 2007 Web Services

Each Web application Web service is installed in the _vti_bin directory, which maps to the following file system location:

%COMMONPROGRAMFILES%Microsoft Sharedweb server extensions12ISAPI

The following Web services are provided in Office SharePoint Server 2007 Web applications.

Friendly Name Location Description

Alerts

/_vti_bin/alerts.asmx

Provides methods for working with alerts for list items in a SharePoint site.

Area Web service

/_vti_bin/areaservice.asmx

Deprecated Web service. Provides an area interface for remote clients.

Authentication Web service

/_vti_bin/Authentication.asmx

Provides ability for Web services to operate in conjunction with forms authentication.

BDC Fields Resolver Web service

/_vti_bin/bdcfieldsresolver.asmx

BDC Fields Resolver Web service for client applications. Reserved for internal use only.

BDC Web service

/_vti_bin/businessdatacatalog.asmx

Business Data Catalog metadata Web service. Reserved for internal use only.

CMS Content Area Toolbox Info Web service

/_vti_bin/contentAreaToolboxService.asmx

Designed for use by the Microsoft Office SharePoint Designer client to use.

Copy Web service

/_vti_bin/Copy.asmx

Provides methods for copying items between locations in the SharePoint environment.

List Data Retrieval Web service

/_vti_bin/DspSts.asmx

Provides a method for performing queries against lists in Windows SharePoint Services.

Document Workspace Web service

/_vti_bin/DWS.asmx

Provides methods for managing Document Workspace sites and the data they contain.

Excel Services Web service

/_vti_bin/ExcelService.asmx

Provides methods to call Excel Services remotely or to work as a callback for Web Parts.

Forms Web service

/_vti_bin/Forms.asmx

Provides methods for returning forms used in the user interface when working with the contents of a list.

Forms Services proxy Web service

/_vti_bin/FormsServiceProxy.asmx

Provides methods for Forms Services to proxy requests to remote data sources from Web-based forms.

Forms Services Web service

/_vti_bin/FormsServices.asmx

Provides methods to call Forms Services remotely or to work as a callback for Web-based forms.

Imaging Web service

/_vti_bin/Imaging.asmx

Provides methods that enable you to create and manage picture libraries.

Lists Web service

/_vti_bin/Lists.asmx

Provides methods for working with lists and list data.

Meetings Web service

/_vti_bin/Meetings.asmx

Provides methods that enable you to create and manage Meeting Workspace sites.

Official File Web service

/_vti_bin/officialfile.asmx

Provides methods for sending files to a records repository.

People Web service

/_vti_bin/People.asmx

Provides methods for working with security groups.

Permissions Web service

/_vti_bin/Permissions.asmx

Provides methods for working with the permissions for a site or list.

Published Links Web service

/_vti_bin/publishedlinksservice.asmx

Office system client applications and other applications can obtain the list of published links on the server that are targeted to the current user.

Publishing Service Web service

/_vti_bin/PublishingService.asmx

Provides methods to remotely work with the publishing service.

Search Web service

/_vti_bin/search.asmx

Allows access to Enterprise Search results from client applications and Web applications outside of the context of a SharePoint site.

SharePoint Directory Management Web service

/_vti_bin/sharepointemailws.asmx

Provides methods for remotely managing distribution groups.

Sites Web service

/_vti_bin/sites.asmx

Provides methods for returning information about the site templates for a site collection.

Slide Library Web service

/_vti_bin/SlideLibrary.asmx

Provides methods for slide library callbacks or remote publishing of slides.

Search Crawl Web service

/_vti_bin/spscrawl.asmx

Provides methods for remote Office SharePoint Server 2007 server farms to crawl a local farm.

Search Web service

/_vti_bin/spsearch.asmx

Provides methods for remotely performing searches within a Windows SharePoint Services deployment.

Users and Groups Web service

/_vti_bin/UserGroup.asmx

Provides methods for working with users, site groups, and cross-site groups.

User Profile Change Web service

/_vti_bin/userprofilechangeservice.asmx

Provides methods to query the user profiles change log remotely.

User Profile Web service

/_vti_bin/userprofileservice.asmx

Provides a user profile interface for remote clients.

Versions Web service

/_vti_bin/versions.asmx

Provides methods for working with file versions.

Views Web service

/_vti_bin/Views.asmx

Provides methods for working with views of lists.

Web Part Pages Web service

/_vti_bin/webpartpages.asmx

Provides the methods to send information to and retrieve information from Web services.

Webs Web service

/_vti_bin/Webs.asmx

Provides methods for working with sites and subsites.

Workflow Web service

/_vti_bin/workflow.asmx

Provides methods to work with workflows.

The SharePoint Central Administration Web application provides Web services in the _vti_adm directory that map to the following file system location:

%COMMONPROGRAMFILES%Microsoft Sharedweb server extensions12ADMISAPI

The following Web services are exposed within the Central Administration Web application. For reasons of helping to ensure security, these Web services are not available to call remotely from custom code in a hosted environment.

Friendly Name Location Description

Admin

/_vti_adm/admin.asmx

Provides methods for managing a deployment of Windows SharePoint Services, such as for creating or deleting sites.

Content Deployment Remote Import

/_vti_adm/ContentDeploymentRemoteImport.asmx

Provides methods for a remote server farm to use content deployment to get content into a local farm.

Depending on configuration, the Office Server Web Services Web application exposes the following internal Web services, which are not available for calls from custom code.

Friendly Name Location Description

Search Web service

SearchAdmin.asmx

Office SharePoint Server 2007 Search Administration Web service.

Search Application Web service

/SSP/Search/SearchAdmin.asmx

Office SharePoint Server 2007 Search Application Administration Web service.

Excel Service SOAP

/SSP/ExcelCalculationServer/ExcelService.asmx

Office SharePoint Server 2007 Excel Services Application Web service.