Accessing a SharePoint server from outside a network with a Forefront TMG.

The following 2 scenarios can give you an Internal Server Error

  • View properties on document
  • Editing a list view

Full error text:

Error Code: 500 Internal Server Error. The request was rejected by the HTTP filter. Contact the server administrator. (12217)

 

?Solution

The reason why this happens is that the HTTP filter in Forefront has a URL protection mechanism wich will block URLs containing escaped characters after normalization.

To fix this:

  1. Open the properties of the firewall policy.
  2. Under the Traffic tab. Click Filtering
  3. Uncheck Verify normalization in the URL Protection section

 

Verify normalization will block URLs containing escaped characters after normalization.

 

Tags: , , | Categories: SharePoint related | SharePoint Configuration

In SharePoint you can only view alerts per site. That means you cannot see all your alerts at once.

View my alerts on a site

At the top of the site, click User name , and then click My Settings, click My Alerts.

View alerts for other people on a site

As a Site Administrator you can view alerts of other users on your site through Site Actions -> Site Settings -> Under Site Administration -> User Alerts select the person whose alerts you want to view and select Update.

View all my alerts

There are several solutions for this, CodePlex and other SharePoint companies have some.
Outlook to the rescue! If you are using Exchange your Exchange mailbox will keep track of all your alerts and where these are subscribed from.
Choose Rules and Alerts.. select the Manage Alerts tab.

blog-manage-all-alerts - small

Tags: , , , | Categories: SharePoint Configuration | Tips and tricks

Problems when trying to open a SharePoint Document Library in explorer view from Windows?

With errors like:

“Your client does not support opening this list with Windows Explorer.”

or in danish

”Klienten understøtter ikke åbning af denne liste med Windows Stifinder.”

Explorer view uses the WebDav protocol to connect to SharePoint from the client.

In Windows 7 or Windows Vista
Ensure the WebClient service is not disabled. The WebClient service is critical to the Open in Windows Explorer feature.

If already running and still not working try to restart the service.


In Windows Server 2008
The Windows Server is not designed to be a client and the WebDav client is not installed or enabled by default.
In order to enable the WebDav client on a server simply enable the Desktop Experience feature.

Tags: , | Categories: SharePoint Configuration | Tips and tricks

It all began while restarting the Office SharePoint Server Search service. I got the error

"The handle is invalid"

I tried modifying the Log On Identity of the service.  Changing this to "Local System", the service started without any errors. But being in a server farm this provided me with:

“The search request was unable to connect to the Search Service”

or actually it was in danish

”Søgeanmodningen kunne ikke oprette forbindelse til søgetjenesten.”

Solutions
1. Maybee the Accounts used to search dont have the right access needed or the Search services is not running. Check the services; Office SharePoint Server Search and Windows SharePoint Services Search
2. Search server settings
Go to Central Admin > Operations > Services on Server > Office SharePoint Server Search Service Setting -> "User this server for serving search queries”

Thank you:

http://fnoja.blogspot.com/2008/02/search-request-was-unable-to-connect-to.html

http://consultingblogs.emc.com/johnrayner/archive/2007/02/16/MOSS_3A00_-Error-_2200_The-handle-is-invalid_2200_-when-starting-Windows-SharePoint-Services-_2800_WSS_2900_-Search-service.aspx

 

 

Tags: , | Categories: SharePoint Configuration

If you get the following error when trying to run a search on a WSS site:

Your search cannot be completed because this site is not assigned to an indexer.
Contact your administrator for more information.

or in danish

Din søgning kan ikke fuldføres, da dette websted ikke er tildelt et indekseringsprogram.
Kontakt administratoren for at få flere oplysninger.

You'll need to set the indexer on the content database of the site collection. This is done by going to the Central Adminstration > Application Management > Content Databases. Then choose the database of your site and set the index server.

This is the same thing with the Search Server 2008 Express added.

 

Thank you Paul Wu

http://biztalkdev.com/blogs/paulwu/archive/2007/03/22/SharePoint-Error-Your-search-cannot-be-completed-because-this-site-is-not-assigned-to-an-indexer.aspx


 

Tags: , , , | Categories: SharePoint Configuration

Ever run in to problems with SharePoint and to long url or problems with uploading documents deep down the file map path?

I have and I found some pretty stange limits.

The Office programs Excel and Word have different limitations when it comes to storing documents in SharePoint.
In a SharePoint document library with a long URL path there is a difference in the length of file names that can be saved.

  • Word can´t handle more than 262 characters in the URL. Incl. path and file name
  • Excel can´t handle more than 218 characters in the URL. Incl. path and file name
 
The reason that there even can exist as long paths to an Excel sheet is that the above limit only applies when you save the document from Excel / Word and not when you upload it with the send button or using the the Explorer view.
There is even an different transfer limit on the 2 ways to transfer documents, but thats another day.
 
General restrictions:
URL path for all files and folders to be less than 260 characters and must not exceed 128 characters in each file or folder name in the URL path.
But this is not when you save the document from Excel!
 
 
Tags: , , , , | Categories: SharePoint Configuration | SharePoint Development | Tips and tricks