Paul Liebrand’s Weblog

Welcome to my blog mainly about SharePoint

SharePoint URL Shortener Codeplex site has been published and is live!

The SharePoint URL Shortener Codeplex site has been published and is now publically available (as promised from yesterdays post).

LiebrandUrlShortener

As a reminder, the URL is http://spurlshortener.codeplex.com.

If you have any problems, please post something on the Codeplex site and/or hit me up on Twitter (@PaulLiebrand).

Thank you and please be gentle!

Advertisements

August 29, 2009 Posted by | SharePoint | , , | 3 Comments

SharePoint Url Shortener – it’s finally here!

After many iterations and delays I am pleased to announce that my SharePoint Url Shortener (initial version) is finally here! There is still some work to be done on this but I have decided to release it in its current state to start getting some feedback from the community.

Here is a demonstration of the process – from feature activation to Url generation:

I’ll be publishing the Codeplex project sometime this weekend (probably Saturday) so be on the look out.

The Codeplex Url is http://spurlshortener.codeplex.com – I’ll update my blog and send out a notification on Twitter (@PaulLiebrand) when I actually pull the trigger.

Thank you for being patient and I hope you find this useful.

August 28, 2009 Posted by | SharePoint | , , | 2 Comments

Publishing Links to Office 2007 without enabling My Sites in SharePoint

Some organizations want to leverage the publish links to Office 2007 client feature that SharePoint 2007 offers without enabling My Sites. The publish links to Office 2007 relies on the same update mechanism that the My SharePoint Sites feature uses.

If you have read any of my posts in the past on this topic you know that these features were designed around the fact that users would have My Sites. In fact, the very action of setting your default My Site is what triggers these features to become active.

Is is very possible to use these features without enabling My Sites but it will require you to update some registry settings on your client PC’s. Most organizations will deploy these types of settings using a GPO.

The registry setting you want to add can be found under:

HK_CurrentUser\Software\Microsoft\Office\12.0\Common\Portal

Add a string value called PersonalSiteURL and point it to any root SharePoint site in your farm that all your users have access too. Normally the users My Site URL would be listed here.

Once you have populated this registry setting, you should start seeing your published links appear once the user attempts to access My SharePoint Sites the first time via an Office 2007 application.

I also developed a utility that you can run, specify your SharePoint URL, and it will return all the URL’s it believes your client PC should get published. For example:

MySharePointSiteChecker

You can download this utility from here:

GetUserPublishedLinks (via Skydrive)

August 25, 2009 Posted by | SharePoint | , , , | 3 Comments

Baffled! “Your changes could not be saved because this SharePoint Web site has exceeded the storage quota limit.”

I have hit a strange problem today and I am trying to wrap my head around why this is happening.  Perhaps the SharePoint community has run into this before and has some insight as to what is causing it.

I have some custom code that enumerates each list then items in the list to do some security report processing. However, every now and then we will run across a user who has exceed their site quota and when our custom code runs we receive the following SPException:

Microsoft.SharePoint.SPException occurred
  Message="Your changes could not be saved because this SharePoint Web site has exceeded the storage quota limit. You must save your work to another location.  Contact your administrator to change the quota limits for the Web site."
  Source="Microsoft.SharePoint"
  ErrorCode=-2130575282
  StackTrace:
       at Microsoft.SharePoint.Library.SPRequest.GetListItemDataWithCallback(String bstrUrl, String bstrListName, String bstrViewName, String bstrViewXml, SAFEARRAYFLAGS fSafeArrayFlags, ISP2DSafeArrayWriter pSACallback, ISPDataCallback pPagingCallback, ISPDataCallback pSchemaCallback)
       at Microsoft.SharePoint.SPListItemCollection.EnsureListItemsData()
       at Microsoft.SharePoint.SPListItemCollection.Undirty()
       at Microsoft.SharePoint.SPBaseCollection.System.Collections.IEnumerable.GetEnumerator()

My code does not attempt to update any information within the SharePoint site, so why would simply accessing the items in a list cause this error message?

To prove to myself that I am not writing any information to the list I decided to navigate to this list using the SharePoint Manager 2007 tool. As you can see from the screenshot below, I received the same error message just by clicking on the library:

YourChangesCouldNotbeSaved

Has anyone else seen this before? Any guidance would be appreciated.

I’ll continue my quest to discover the reason – I am hoping it is something obvious that I am overlooking.

August 14, 2009 Posted by | SharePoint | , | 2 Comments

Access Denied When Adding New Item in SharePoint

This may seem obvious now but I through me for a loop for a few minutes yesterday when a co-worker asked me why he was getting redirected to the SharePoint access denied page when he attempted to add a new item to a list.

I checked the permissions on the list and he had contribute rights; hence the reason why he could see the New drop down button on the list. However, after he filled out the form and click Ok he was immediately re-directed.

After a few minutes I realized that he had the Edit access option of the Item-level Permissions on the list set to None.

Doh! – of course he is getting Access Denied

When adding a new item to a list, the SharePoint object model will,

  • Call the SPList.Add() method,
  • Update the properties of the SPListItem, then
  • Call the SPListItem.Update() method  <—Access is denied

Understand how SharePoint updates the item, you can understand why setting the Edit access option to None would cause an issue.

From an end-users perspective, seeing the New option but getting denied could lead to major confusion. Knowing this as a possible scenario, you can at least be better equipped to help troubleshoot and solve the issue.

August 14, 2009 Posted by | SharePoint | , | Leave a comment